| opendevreview | Adam Harwell proposed openstack/devstack master: WIP: Add ASGI serving via oslo_service.asgi_factory https://review.opendev.org/c/openstack/devstack/+/996228 | 08:54 |
|---|---|---|
| opendevreview | Adam Harwell proposed openstack/devstack master: WIP: Add ASGI serving via oslo_service.asgi_factory https://review.opendev.org/c/openstack/devstack/+/996228 | 08:59 |
| opendevreview | Adam Harwell proposed openstack/devstack master: WIP: Add ASGI serving via oslo_service.asgi_factory https://review.opendev.org/c/openstack/devstack/+/996228 | 09:32 |
| opendevreview | Adam Harwell proposed openstack/devstack master: WIP: Add ASGI serving via oslo_service.asgi_factory https://review.opendev.org/c/openstack/devstack/+/996228 | 09:45 |
| eolivare | hi there, when you have some time, please review this devstack patch: https://review.opendev.org/c/openstack/devstack/+/994408 | 12:27 |
| eolivare | Tested with https://review.opendev.org/c/openstack/neutron/+/994257 | 12:27 |
| frickler | eolivare: it would be good to have some review from the neutron team, slaweq or ralonsoh maybe? | 12:44 |
| eolivare | frickler, it makes sense. I'll ask them. Thanks | 12:45 |
| *** ykarel_ is now known as ykarel | 13:01 | |
| *** mtreinish_ is now known as mtreinish | 16:36 | |
| *** opendevstatus_ is now known as opendevstatus__ | 16:38 | |
| *** opendevstatus__ is now known as opendevstatus | 16:38 | |
| *** opendevstatus is now known as Guest12850 | 16:38 | |
| sean-k-mooney | gmaan: does this tempet failure to install oslo.config on stable 2025.1 on jammy look familar https://github.com/openstack/governance/blob/master/reference/runtimes/2025.1.rst#additional-testing-for-a-smooth-upgrade | 18:19 |
| sean-k-mooney | wrong link | 18:19 |
| sean-k-mooney | https://review.opendev.org/c/openstack/watcher/+/996304/comments/b57d3d17_abc6f6c0 | 18:19 |
| sean-k-mooney | im proposing we just disable the jammy job and grenade job there | 18:20 |
| sean-k-mooney | but if there is a known fix we coudl do that as well | 18:20 |
| gmaan | sean-k-mooney: yes, jammy jobs needs to be pinned with old tempest and to use stable/2025.1 constraints. it is using master one and failing | 18:20 |
| gmaan | let me find the fix i did for other jammy job and same you can appky | 18:20 |
| sean-k-mooney | right i vagley recall that coming up on irc a weeek or two ago | 18:21 |
| sean-k-mooney | i tought that was being pinned in devstack however or a common job def? | 18:21 |
| gmaan | sean-k-mooney: this one, though i squashed it in other fix but this is how you can fix | 18:21 |
| gmaan | https://review.opendev.org/c/openstack/devstack/+/993973/1/.zuul.yaml | 18:21 |
| gmaan | no, because 2025.1 is still in supported phase so we cannot pin it globally. | 18:22 |
| sean-k-mooney | we cloud pin it in greneade however right | 18:22 |
| sean-k-mooney | well i guess not | 18:22 |
| sean-k-mooney | ok so copy paste that into the affecte jobs is the recommendation ? | 18:23 |
| sean-k-mooney | if so ill do that now | 18:23 |
| gmaan | no, same thing, upgrade from 2025.1 -> 2025.2 should be with master tempest | 18:23 |
| gmaan | yeah, copy paste should work | 18:23 |
| sean-k-mooney | no im talking about grenade on 2025.1 | 18:23 |
| sean-k-mooney | which is 2024.2->2025.1 | 18:23 |
| gmaan | sean-k-mooney: does that install watcher tempest plugin also? | 18:23 |
| sean-k-mooney | oh greneade probably | 18:23 |
| sean-k-mooney | we have our own watcher-grenade job | 18:24 |
| sean-k-mooney | so i expect we are | 18:24 |
| gmaan | sean-k-mooney: grenade on 2025.1 can be removed as those might be broken for other reason as 2024.2 is EOL | 18:24 |
| gmaan | sean-k-mooney: i mean if it install watcher tempest plugin then you need to pin the old wather-tempest-plugin also in jammt job | 18:24 |
| sean-k-mooney | well only if the job breaks | 18:25 |
| sean-k-mooney | i.e. if we are using a new method in a latere tempest | 18:25 |
| sean-k-mooney | or there is a python issue | 18:25 |
| gmaan | but this also failing watcher-tempest-api-jammy | 18:25 |
| sean-k-mooney | yes that the one i actully checked | 18:25 |
| sean-k-mooney | so that ill fix with the pin | 18:26 |
| sean-k-mooney | ill see if the pin is enouch for grenade and drop it if not | 18:26 |
| gmaan | sean-k-mooney: as this also has watcher-tempest-plugin, this is good example where you can pin the plugin also https://review.opendev.org/c/openstack/cinder/+/991434/2/.zuul.yaml#147 | 18:27 |
| gmaan | yeah, I will say drop as 2024.2 is EOL | 18:28 |
| sean-k-mooney | ya so i coudl do that but i if i dont need to pin it i was gong to let it continue using master | 18:28 |
| sean-k-mooney | but if it failes then yep ill lookup the relevent tag | 18:28 |
| sean-k-mooney | what tag did ye end up pining too for cinder was it for 2026.1 | 18:29 |
| sean-k-mooney | i.e the same release as the corresponding tempest pin? | 18:29 |
| gmaan | you can try if it pass with master but in future it might fail | 18:31 |
| gmaan | it was 2025.1 release one | 18:31 |
| gmaan | 3.3.0 or 3.4.0 should work for wacther-tempest-plugin https://releases.openstack.org/epoxy/index.html#epoxy-watcher-tempest-plugin | 18:32 |
| sean-k-mooney | ya i was looking at 3.7.0 https://releases.openstack.org/gazpacho/index.html#tempest-plugins | 18:32 |
| sean-k-mooney | we have quite a few new temepst test and backproted some fixes to 2025.1 that are covered by them | 18:33 |
| sean-k-mooney | so if i use 3.3.0 or 3.4.0 it will reduce the tgest coverage | 18:33 |
| sean-k-mooney | so if 3.7.0 works ill go with that for now and we can alwasy downgrade it if needed | 18:33 |
| sean-k-mooney | https://review.opendev.org/c/openstack/watcher/+/996338/1 should fix it but ill drop to 3.4.0 if it does not thanks | 18:38 |
| gmaan | yeah, i think 3.7.0 should work but let's see | 18:42 |
| sean-k-mooney | ok tempes tjust started running https://zuul.openstack.org/stream/9d651c774bbd4ab083567c1937d683aa?logfile=console.log ill wait for it to finish but while it does ill go make dinner | 19:26 |
| sean-k-mooney | 3.7.0 passes install but w weill see if it uses anything form a newer tempst that will fail | 19:27 |
| gmaan | all worked fine | 20:19 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!