| *** ykarel__ is now known as ykarel | 06:23 | |
| rosmaita | I'm getting a 404 for https://docs.openstack.org/releasenotes/os-brick/2026.2.html even though they exist when I build locally ... i guess the publish releasenotes job failed at some point? | 15:08 |
|---|---|---|
| rosmaita | same for python-cinderclient | 15:08 |
| clarkb | you should be able to trace that from the zuul job | 15:35 |
| clarkb | of course the first step is figuring out what is responsible for building those artifacts | 15:36 |
| clarkb | looks like it is the promote-openstack-releasenotes job that promotes the artifact from gate | 15:40 |
| clarkb | this runs in the promote pipeline | 15:40 |
| clarkb | https://zuul.opendev.org/t/openstack/buildset/052c4cb281464d78abbfd5da65db5b97 master ran here a few seconds before stable/2026.2 https://zuul.opendev.org/t/openstack/buildset/574e03c461694d94a5f853a76489c965 | 15:43 |
| clarkb | rosmaita: my hunch but I don't have concrete evidence yet is that the ordering there overwrote the content you're looking for | 15:44 |
| rosmaita | clarkb: thanks for looking, your hypothesis sounds very plausible | 15:46 |
| clarkb | publish-openstack-releasenotes-python3 has a semaphore but that job only runs on tags. The promote-openstack-releasenotes job which runs on every merge in the promote pipeline does not have a semaphore | 15:46 |
| rosmaita | clarkb: sounds like the workaround would be to merge any patch with a release note to master, and then that should promote the latest set of releasenotes | 15:49 |
| clarkb | rosmaita: https://151cae9b08d5ca436478-aa35b71b6be789592a986446cd8c5cd9.ssl.cf5.rackcdn.com/openstack/65d274a4addf48d9bff6394b8b1d1975/docs/ this is the 2026.2 preview site (and lacks the 2026.2 content) https://07020983da81469adf4b-b9f7b4910ad16729218670d60db15b93.ssl.cf5.rackcdn.com/openstack/c21cef08e8564769911f477dedd0f6d6/docs/ is the master preview site and has the | 15:50 |
| clarkb | content. So I think 2026.2 overwrote the master content which ironically removed the 2026.2 release notes | 15:50 |
| clarkb | it does make me wonder if you're always going to overwrite broken content when you merge things to 2026.2 though | 15:50 |
| clarkb | maybe those jobs should only run from the master branch? But yes I think if you land something on master it should fix things. Possibly only until you land the next change on 2026.2 though | 15:51 |
| rosmaita | ok, i will try to keep an eye on what happens, we will be doing both this week for RC-2 | 15:52 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!