| *** bauzas_ is now known as bauzas | 05:15 | |
| *** bauzas_ is now known as bauzas | 05:37 | |
| *** bauzas_ is now known as bauzas | 07:33 | |
| *** bauzas- is now known as bauzas | 09:30 | |
| *** bauzas_ is now known as bauzas | 09:41 | |
| sean-k-mooney | fungi: clarkb: remember we chatted about the zuul quick fail issue when jobs were retryed and a post playbook and an error due to a previous error in the pre playbook | 10:45 |
|---|---|---|
| sean-k-mooney | i rememebr there was a patch propsoed for that but i was just wonderign if that got merged and if we have that avaiable in our current deployment | 10:45 |
| sean-k-mooney | i have not specificly seen that issue again recently but i also was not looking so just tought i woudl check in and see if that is still an issue before we get to the feature feeze crunch period | 10:46 |
| sean-k-mooney | on an unrealted note i happen to watch the recording of the tc meeting yesterday while cleaning my kitchen and there was a disucsion about ci health and testing with noble https://review.opendev.org/c/openstack/nova/+/922492 | 10:50 |
| sean-k-mooney | i have had a patch up to make nova-next run with noble since i fixed the devstack instlal issue so im hoping we will proceed with that soon. | 10:50 |
| sean-k-mooney | we already swapped the whitebox-tempest-plugin to use noble too. | 10:51 |
| sean-k-mooney | so while usage of noble will be relitivly light for 2024.2 we will have some test coverage of it before we move almost all the jobs to noble next cycle | 10:52 |
| sean-k-mooney | on a more personal note i would also be infaovr of removing our usage of centos stream form ci and replacing it with a pinned rocky version that we bump once a cycle or so. i.e. rocky 9.4 keeping stream for experimental or future testing might be fine but i think its more hassel then its actully worth. i would almost prefer ot track the fedora eln branch instead as that | 10:55 |
| sean-k-mooney | ultimatly is the upstream of all rhel/centos/rocky/alma distributoins | 10:55 |
| sean-k-mooney | *that being centos9 stream | 10:56 |
| sean-k-mooney | some of these topics are proably more suited to the openstack-qa channel but just wanted to mention it while it was fresh in my mind. | 10:56 |
| frickler | sean-k-mooney: how exactly would you pin "rocky 9.4"? currently iiuc we always build "rocky 9" in its latest incarnation. or was I misunderstanding your comment? | 11:31 |
| sean-k-mooney | so rocky has versioned cloud images http://dl.rockylinux.org/pub/rocky/9/images/x86_64/Rocky-9-GenericCloud-Base-9.4-20240509.0.x86_64.qcow2 | 11:36 |
| sean-k-mooney | but perhasp they dont keep the old ones after a new release | 11:36 |
| sean-k-mooney | but even if we tracked latest it would be more stable then stream | 11:36 |
| sean-k-mooney | no they do keep them https://dl.rockylinux.org/vault/rocky/9.2/images/x86_64/Rocky-9-GenericCloud-Base-9.2-20230513.0.x86_64.qcow2 | 11:37 |
| sean-k-mooney | frickler: ill admit i dont know if they have seperate repo verions for each point release like rhel does | 11:38 |
| sean-k-mooney | the even number rhel release i belive are the EUS (extended update supprot release) that are security patched and maintened for 4 years | 11:38 |
| sean-k-mooney | so if the repos can be pinned to the relevent even version and we can use the equivlent base iamge that might make things a lot more stable | 11:39 |
| sean-k-mooney | it looks like rocky only activly update the last 2 version i.e latest release and previous poitn relese looking at http://dl.rockylinux.org/pub/rocky/ | 11:40 |
| sean-k-mooney | but we could basicly bump this version each slurp | 11:41 |
| frickler | I think if someone can submit patches to amend our image builds accordingly, that would be fine, but I don't think some infra-root will do that | 11:45 |
| sean-k-mooney | ya this is a converstaion to have on #openstack-qa in the contenxt of the testing runtimes for 2025.1 | 11:46 |
| frickler | well qa can only use the images that are available in opendev, so there is some overlap (as is in the participants), so I don't think this discussion is misplaced here | 11:47 |
| sean-k-mooney | i would personally like to replace or usage of centos 9 stream with rocky 9.4 for 2025.1 and move to rocky 9.6 for 2026.1 assuming the release cadances line up | 11:47 |
| sean-k-mooney | so we buidl the rocky limages form containers https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/rocky-container/containerfiles/9#L1 | 11:50 |
| sean-k-mooney | so really all we woudl need to do is convert the image tag to a build arg | 11:50 |
| sean-k-mooney | and then modify the nodepool config to set it | 11:50 |
| sean-k-mooney | in theory that is ment ot be set via the DIB_RELEASE env var today https://github.com/openstack/diskimage-builder/blob/master/diskimage_builder/elements/rocky-container/environment.d/10-01-rocky-distro-name.bash#L2C8-L2C19 | 11:51 |
| sean-k-mooney | but that does not appare to be hooked up | 11:52 |
| sean-k-mooney | oh ok it kind of is | 11:53 |
| sean-k-mooney | https://github.com/openstack/diskimage-builder/tree/master/diskimage_builder/elements/containerfile#containerfile | 11:53 |
| sean-k-mooney | the way the generic container file element work is it expect a contianer file per release and does not ues build args | 11:53 |
| sean-k-mooney | so we woudl just need to copy past it with the full vertsion and set the tag properly and that about it on the dib side | 11:53 |
| sean-k-mooney | on the node pool side its just updating https://github.com/openstack/project-config/blob/master/nodepool/nodepool.yaml#L189-L200 or adding new build targets | 11:55 |
| sean-k-mooney | so its all pretty simple to do if we actully decied we want to do that | 11:56 |
| sean-k-mooney | there may be some considertion about mirroring that need dicssion too | 11:56 |
| *** bauzas- is now known as bauzas | 12:56 | |
| opendevreview | Takashi Kajinami proposed openstack/project-config master: Migrate release-openstack-puppet to jammy https://review.opendev.org/c/openstack/project-config/+/925986 | 14:34 |
| *** bauzas_ is now known as bauzas | 16:39 | |
| *** ministry is now known as __ministry | 18:27 | |
| *** bauzas_ is now known as bauzas | 19:32 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!