| stephenfin | sean-k-mooney: Could I ask for a review on https://review.opendev.org/c/openstack/python-watcherclient/+/931174 ? It's one of two things breaking a job in openstackclient | 12:08 |
|---|---|---|
| sean-k-mooney | i can review but i dont currently have merge rights | 12:10 |
| kopecmartin | hello, where are we at with this https://review.opendev.org/c/openstack/project-config/+/934357 and basically the whole rights talk we had last week? .. https://meetings.opendev.org/irclogs/%23openstack-watcher/%23openstack-watcher.2024-11-07.log.html | 15:36 |
| kopecmartin | do we wanna set any kind of a deadline/timeline until anyone can object and then proceed? | 15:36 |
| sean-k-mooney | so i ment to start reachign out to chenker this week but i was hoping to get some guidance form the tc on the launchpad project accces yesterday before i did. | 17:08 |
| sean-k-mooney | tldr is there are no active admisn of the launchpad team and the team is not owned by the openstack-admins team | 17:09 |
| sean-k-mooney | so right now we are blocked on the launchpad side until we resove that | 17:09 |
| sean-k-mooney | on the gerrit side | 17:09 |
| sean-k-mooney | i was going to reach out to chenker either this week or ealy next and ask if they were conformatble rebootstraping the core teams with myself and perhaps you (kopecmartin) and gman in the case of the tempest plugin | 17:11 |
| sean-k-mooney | kopecmartin: i was not really sure who had interest time and experiance to do wider review across all the deliverables | 17:12 |
| haleyb | so i realize stable/2023.1 is going unmaintained, but we (Canonical) see stable/2023.2 is also broken - https://review.opendev.org/c/openstack/watcher/+/934379 (canary patch). I didn't know the best workaround for those failures, but can spend some time fixing things with a little guidance | 17:54 |
| haleyb | disabling the jobs seems non-optimal | 17:54 |
| sean-k-mooney | haleyb: so right now one of hte problems we have is we are tryign to restabelis merge rights so we can get the master and stable brances healty again | 17:59 |
| sean-k-mooney | i do plan to tyr and fix the stable jobs | 18:00 |
| sean-k-mooney | we may also try and help get unmiantianed/2023.1 healty as a lower piriority but im all for fixing stable/2023.2 | 18:00 |
| sean-k-mooney | haleyb: hum focal is that 22.04 | 18:01 |
| sean-k-mooney | or 20.04 | 18:01 |
| haleyb | sean-k-mooney: thanks, i'm not trying to push was more curious. if there's something we can help with let me know i just didn't know where to start as the 2023.2 failures were regarding not supporting things on focal | 18:01 |
| haleyb | 20.04 | 18:01 |
| haleyb | maybe it's just a bad nodeset somewhere? | 18:02 |
| sean-k-mooney | i woudl guess since the porject has mostly been dorment they missed moving it forard with the rest | 18:02 |
| sean-k-mooney | that should be an easy fix | 18:02 |
| sean-k-mooney | let me check what the testing runtim was quickly but im pretty sure 2023.02 shoudl have been 22.04 | 18:03 |
| sean-k-mooney | yep https://github.com/openstack/governance/blob/master/reference/runtimes/2023.2.rst#tested-runtimes-for-20232 | 18:03 |
| haleyb | i can have bryan take a look if it's simple, might be a good exercise to learn about job definitions, etc | 18:03 |
| sean-k-mooney | oh so 20.04 was technially ment to be used for grenade | 18:04 |
| sean-k-mooney | what the actual error i wonder | 18:04 |
| sean-k-mooney | oh its just the devstack os comaptiblity list | 18:04 |
| sean-k-mooney | so ya we coudl add force but moving those to 22.04 is proably for the best | 18:05 |
| sean-k-mooney | haleyb: ah this is missing https://github.com/openstack/watcher/commit/922478fbda1a9b23b566969ce691b2d5182054d1 | 18:06 |
| haleyb | so the nodeset in stable/2023.2 has focal, that might be an easy change - i meet with him shortly will have him propose a change | 18:06 |
| haleyb | sean-k-mooney: oh, did that not merge? | 18:07 |
| opendevreview | sean mooney proposed openstack/watcher stable/2023.2: Unblock the CI gate https://review.opendev.org/c/openstack/watcher/+/934996 | 18:07 |
| sean-k-mooney | it did but on 2024.1 | 18:07 |
| sean-k-mooney | it was never cherrypicked but ^ shoudl fix the ci | 18:07 |
| sean-k-mooney | lets see if it works | 18:07 |
| haleyb | sean-k-mooney: hey thanks for finding that, will keep an eye | 18:08 |
| sean-k-mooney | haleyb: as an aside i know canoncal added maas supprot to watcher in caracal. are ye interested in helpign to revie/maintin watcher on the stable/master branches? | 18:09 |
| haleyb | sean-k-mooney: that's a good question, i mean, we do support it and find bugs, just don't know about master but can ask around | 18:10 |
| sean-k-mooney | the reason im askign is my managemnet (redhat) have at least for this cycle, (hopefully more to come) have ask myself and a few other to help revivie the project | 18:11 |
| * haleyb already has another full-time job :) | 18:11 | |
| sean-k-mooney | so i will be trying to help adress some issue liek thei and we are hoping ot extend and diversify the core team | 18:12 |
| sean-k-mooney | so even if its fixing bugs or saying this branch is broken that woudl be helpful | 18:12 |
| haleyb | this was the first time i've been involved with watcher in 2 years, but i know we can help fix branches when CI breaks, at least i encourage people to do that when we encounter doing cherry-picks | 18:14 |
| sean-k-mooney | oh the mass integration ws done by someoen form cloud stack https://github.com/openstack/watcher/commit/c95ce4ec17aa7844f64e97d67cf66c017d656c47 sorry i assuemd they were form canonical | 18:16 |
| sean-k-mooney | s/mass/maas/ | 18:16 |
| sean-k-mooney | sorry cloudbase now cloudstack | 18:18 |
| haleyb | right | 18:18 |
| sean-k-mooney | that was one of the integration i was most woried about keeping fucntionla as there was nnot upstream ci job for ti and its also using asyncio which is not generally safe to do whn also useing eventlet | 18:22 |
| sean-k-mooney | so im not entirly conviced the unit tests are really adiquete to prevent regressions | 18:23 |
| sean-k-mooney | haleyb: do you know if there is any supprot or testing of that either the charm or sunbeam installers or in ubuntu in general | 18:23 |
| sean-k-mooney | haleyb: my concern is really that it might work fine for a long time and it could silently break and no one will notice until someone files a bug | 18:25 |
| sean-k-mooney | thats proably a next cycle problem as i dont think we have integration testing of the ironic supprot either | 18:25 |
| haleyb | sean-k-mooney: i really have no idea | 18:25 |
| sean-k-mooney | ack no worries | 18:26 |
| sean-k-mooney | just said i would ask while you were about | 18:26 |
| sean-k-mooney | hum so no https://review.opendev.org/c/openstack/charm-watcher/+/901445 it never merged but it is in airship so maybe its being used in starlingx | 18:28 |
| sean-k-mooney | future problems | 18:28 |
| sean-k-mooney | haleyb: https://review.opendev.org/c/openstack/watcher/+/934996 looks like that fixed it | 19:31 |
| haleyb | sean-k-mooney: thanks, lgtm | 19:37 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!