Cloud SIG would like to requests tags for OpenStack Wallaby (next release) for CentOS 8 Stream. Those tags already exist for CentOS 8 [1], but Wallaby will only be built and supported on C8S. I'll create a separate issue to ask the same for previous Openstack releases (Victoria and Ussuri), once this one is closed.
Below the informations:
Build target: cloud8s-openstack-wallaby-el8s Buildroot: cloud8s-openstack-wallaby-el8s-build Buildroot inheritance: cloud8s-openstack-wallaby-el8s-build ├─buildsys8s-release └─cloud8s-openstack-wallaby-candidate └─cloud8s-openstack-wallaby-testing
Destination tag: cloud8s-openstack-wallaby-candidate
Publishing tags: cloud8s-openstack-wallaby-testing cloud8s-openstack-wallaby-release
External repos: centos8s-cr centos8s-extras centos8s-powertools centos8s-appstream centos8s-baseos centos8s-ha
[1] https://pagure.io/centos-infra/issue/107
Metadata Update from @arrfab: - Issue tagged with: cbs, medium-gain, medium-trouble
@alphacc worth discussing about the disttag policy or not ? we can probably easily create this one even if the repo consumption is still an open question
We'd like to maintain the same .el8 disttag for c8s buildroots if possible. Note that C8S itself has .el8 disttag so i guess there is no reason to enforce a different one for SIGs.
The disttag is a SIG decision, I don't think we need to enforce it. it is needed if you want a completely separated namspace for your Steam contributions (no conflicting NVR).
Tags are created, as we have few Stream tags we may still encounter issue, so don't hesitate to ping me on IRC or here.
Comparing cloud8-openstack-wallabi-el8-build and its centos8s equivalent, new one is missing inheritance on -testing tag.
Tested in https://cbs.centos.org/koji/taskinfo?taskID=1875095
@amoralej , just quickly looking and I see it : https://cbs.centos.org/koji/taginfo?tagID=cloud8s-openstack-wallaby-el8-build
So maybe added by @alphacc afterwards ? btw (just me though), I don't know why something el8-build tag would rely on -testing .. -candidate should be more than enough as you have to build in -candidate first anyway .. but shouldn't change anything though ..
Can we close this request for now ?
Yes, it can be closed, Thanks!
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @arrfab: - Issue assigned to alphacc
"cbs list-history --tag cloud8s-openstack-wallaby-el8-build" says changes were made by "koji". If we use our user accounts instead, it will be easier to communicate who is making what change.
Login to comment on this ticket.