This is related to https://pagure.io/nfv-sig/issue/2 We'd like a tag to build the SiG packages against s390x or an already tag that could be use to do so.
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, high-gain, medium-trouble
Tags are now created :
* Checking distribution el9s configuration... -> Checking nfv config... Using default options for nfv/openvswitch Creating tag : nfv9s-openvswitch-s390xbootstrap-candidate Creating tag : nfv9s-openvswitch-s390xbootstrap-testing Creating tag : nfv9s-openvswitch-s390xbootstrap-release -> creating nfv9s-openvswitch-s390xbootstrap-el9s Added external repo centos9s-baseos to tag nfv9s-openvswitch-s390xbootstrap-el9s-build (priority 5) Added external repo centos9s-appstream to tag nfv9s-openvswitch-s390xbootstrap-el9s-build (priority 10) Added external repo centos9s-crb to tag nfv9s-openvswitch-s390xbootstrap-el9s-build (priority 15) Added external repo centos9s-buildroot to tag nfv9s-openvswitch-s390xbootstrap-el9s-build (priority 20) cbs taginfo nfv9s-openvswitch-s390xbootstrap-el9s-build Tag: nfv9s-openvswitch-s390xbootstrap-el9s-build [3000] Arches: s390x Groups: build, srpm-build Tag options: mock.new_chroot : 0 mock.package_manager : 'dnf' mock.yum.module_hotfixes : 1 rpm.macro.vendor : 'CentOS Nfv SIG' This tag is a buildroot for one or more targets Current repo: no active repo Targets that build from this tag: nfv9s-openvswitch-s390xbootstrap-el9s External repos: 5 centos9s-baseos (http://mirror.stream.centos.org/9-stream/BaseOS/$arch/os/, merge mode: bare), arches: inherited from tag 10 centos9s-appstream (http://mirror.stream.centos.org/9-stream/AppStream/$arch/os/, merge mode: bare), arches: inherited from tag 15 centos9s-crb (http://mirror.stream.centos.org/9-stream/CRB/$arch/os/, merge mode: bare), arches: inherited from tag 20 centos9s-buildroot (https://kojihub.stream.centos.org/kojifiles/repos/c9s-build/latest/$arch/, merge mode: bare), arches: inherited from tag Inheritance: 5 .... buildsys9s-release [2363] 10 .... nfv9s-openvswitch-s390xbootstrap-candidate [2997]
So you can now submit exiting src.rpms with --scratch --arch-override s390x nfv9s-openvswitch-s390xbootstrap-el9s for your build order. Worth knowing that after successful scratch build, you have to give me (either through ticket or irc is fine) the task/buildID so that I can then merge with existing build Also worth knowing that if you need to find yourself in these bootstrap tags the newly merged (merged so wait for it to be done) builds, don't forget to "cbs tag-build nfv9s-openvswitch-s390xbootstrap-candidate <build-nvr>" Happy to give more details if needed
--scratch --arch-override s390x nfv9s-openvswitch-s390xbootstrap-el9s
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Needs Review)
hello @arrfab
Below the task ID of the scratch build that need to be merged with existing builds:
taskID NVR 4241911 openvswitch2.15-2.15.0-120.el9s 4241901 openvswitch2.16-2.16.0-117.el9s 4241870 openvswitch2.17-2.17.0-169.el9s 4241871 openvswitch3.1-3.1.0-132.el9s 4241872 openvswitch3.2-3.2.0-102.el9s 4241873 openvswitch3.3-3.3.0-53.el9s 4241902 ovn-2021-21.12.0-82.el9s 4241905 ovn22.03-22.03.0-22.el9s 4241912 ovn22.06-22.06.0-16.el9s 4241913 ovn22.09-22.09.0-31.el9s 4241914 ovn22.12-22.12.0-34.el9s 4241919 ovn23.03-23.03.0-69.el9s 4241920 ovn23.06-23.06.1-11.el9s 4241921 ovn23.09-23.09.4-28.el9s 4241922 ovn24.03-24.03.2-32.el9s
All processed and merged with previous builds so s390x artifacts are available for all these proper builds now.
do you want me to close this ticket or do you want to use it to request s390x to be added for the existing nfv9s-openswitch tags (and which ones ?) ?
up2you if you don't want to proceed immediately with that, so we'd then close this request and you'll just have to create another one later for the other tags
Thank you for the operation and let's request the addition of s390x in this ticket for : nfv9s-openvswitch-2-el9s-build nfv9s-openvswitch-2-candidate nfv9s-openvswitch-2-testing nfv9s-openvswitch-2-release
Done and I just enqueued the nfv9s-openvswitch-2-testing and nfv9s-openvswitch-2-release tags into signing queue to see the s390x being processed and pushed out .
There are quite other signing jobs in the queue but they'll be processed. Closing now this ticket as work was done
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.