Hi folks,
The latest ceph-ansible version requires ansible-2.4.1.0 now, due to some regressions in ansible-2.4.0.0.
It looks like the "ansible" package in CBS has been built in several different build targets recently.
Is there a standard place where we can build the "ansible" package going forward, and then cross-tag that build into all the places that need it?
- Ken
Hi,
On 11/13/17 20:03, Ken Dreyer wrote:
Hi folks,
The latest ceph-ansible version requires ansible-2.4.1.0 now, due to some regressions in ansible-2.4.0.0.
Quick note. It looks like Red Hat is pushing 2.4.1.0, today :
https://access.redhat.com/errata/RHBA-2017:3196
So it will be available in `extras` soon.
On 11/14/2017 06:32 AM, Thomas Oulevey wrote:
Hi,
On 11/13/17 20:03, Ken Dreyer wrote:
Hi folks,
The latest ceph-ansible version requires ansible-2.4.1.0 now, due to some regressions in ansible-2.4.0.0.
Quick note. It looks like Red Hat is pushing 2.4.1.0, today :
https://access.redhat.com/errata/RHBA-2017:3196
So it will be available in `extras` soon.
There was just a release today for ansible-2.4.1.0-1.el7 for extras.
I am building it now.
When complete it will be in centos/7/extras/x86_64/ .. I'm sure that it will also be built for aarch64 and ppc64le. (Actually, the packages are noarch, so those guys can just grab my output and roll into their arches).
On 11/14/2017 07:20 AM, Johnny Hughes wrote:
On 11/14/2017 06:32 AM, Thomas Oulevey wrote:
Hi,
On 11/13/17 20:03, Ken Dreyer wrote:
Hi folks,
The latest ceph-ansible version requires ansible-2.4.1.0 now, due to some regressions in ansible-2.4.0.0.
Quick note. It looks like Red Hat is pushing 2.4.1.0, today :
https://access.redhat.com/errata/RHBA-2017:3196
So it will be available in `extras` soon.
There was just a release today for ansible-2.4.1.0-1.el7 for extras.
I am building it now.
When complete it will be in centos/7/extras/x86_64/ .. I'm sure that it will also be built for aarch64 and ppc64le. (Actually, the packages are noarch, so those guys can just grab my output and roll into their arches).
I just pushed this to the master centos mirror .. should be on all of mirror.centos.org in 30 or so mins.
No idea how often CBS or the internal mirrors it uses are updated once I push an extras release.
Thanks, Johnny Hughes
On Tue, Nov 14, 2017 at 6:48 AM, Johnny Hughes johnny@centos.org wrote:
No idea how often CBS or the internal mirrors it uses are updated once I push an extras release.
I tried another build today (https://cbs.centos.org/koji/taskinfo?taskID=241860) and it failed to find ansible-2.4.1.0. I opened https://bugs.centos.org/view.php?id=14131 . Is "Extras" set up as an external repo in CBS for the ceph build targets?
- Ken
On 15/11/17 23:42, Ken Dreyer wrote:
On Tue, Nov 14, 2017 at 6:48 AM, Johnny Hughes johnny@centos.org wrote:
No idea how often CBS or the internal mirrors it uses are updated once I push an extras release.
I tried another build today (https://cbs.centos.org/koji/taskinfo?taskID=241860) and it failed to find ansible-2.4.1.0. I opened https://bugs.centos.org/view.php?id=14131 . Is "Extras" set up as an external repo in CBS for the ceph build targets?
- Ken
That happens when CBS/Koji doesn't know (yet) that new package[s] is/are available in those external repos : don't forget that the builders don't use the repomd metadata from those os/updates/extras repositories from source, but rather from what CBS/koji exposes.
The task to run "koji regen-repo" runs actually on demand and was triggered in the mean time, so it should be now available for all buildroots that have Extras enabled.
We can (and already discussed that with Thomas, but never finalized that action through CBS meeting) probably just have it triggered as soon as upstream repomd.xml file changed, but that would mean (actually) +/- 200 koji tasks , also reason why we initially preferred to launch it once/day during "idle" time
On Thu, Nov 16, 2017 at 2:42 AM, Fabian Arrotin arrfab@centos.org wrote:
On 15/11/17 23:42, Ken Dreyer wrote:
On Tue, Nov 14, 2017 at 6:48 AM, Johnny Hughes johnny@centos.org wrote:
No idea how often CBS or the internal mirrors it uses are updated once I push an extras release.
I tried another build today (https://cbs.centos.org/koji/taskinfo?taskID=241860) and it failed to find ansible-2.4.1.0. I opened https://bugs.centos.org/view.php?id=14131 . Is "Extras" set up as an external repo in CBS for the ceph build targets?
- Ken
That happens when CBS/Koji doesn't know (yet) that new package[s] is/are available in those external repos : don't forget that the builders don't use the repomd metadata from those os/updates/extras repositories from source, but rather from what CBS/koji exposes.
The task to run "koji regen-repo" runs actually on demand and was triggered in the mean time, so it should be now available for all buildroots that have Extras enabled.
Hi Fabian,
Thanks for the explanation!
https://cbs.centos.org/koji/buildinfo?buildID=20774 failed on Nov 20th with the same error.
I'm looking at our ceph-jewel build tag:
$ cbs taginfo storage7-ceph-jewel-el7-build Tag: storage7-ceph-jewel-el7-build [740] Arches: x86_64 aarch64 ppc64le Groups: build, srpm-build Tag options: This tag is a buildroot for one or more targets Current repo: repo#51946: 2017-11-18 08:10:13.074984 Targets that build from this tag: storage7-ceph-jewel-el7 External repos: 2 centos7-cr (http://mirror.centos.org/centos/7/cr/$arch/) 3 centos7-extras (http://mirror.centos.org/centos/7/extras/$arch/) 5 centos7-updates (http://mirror.centos.org/centos/7/updates/$arch/) 10 centos7-os (http://mirror.centos.org/centos/7/os/$arch/) Inheritance: 5 .... buildsys7 [6] 10 .... storage7-ceph-jewel-candidate [737] 15 .... storage7-ceph-common-candidate [653] 20 .... storage7-common-candidate [119]
It looks like "extras" is enabled there, right? And it was regenerated Nov 18th, two days after your email.
What am I missing?
- Ken
On 21/11/17 00:01, Ken Dreyer wrote:
On Thu, Nov 16, 2017 at 2:42 AM, Fabian Arrotin arrfab@centos.org wrote:
On 15/11/17 23:42, Ken Dreyer wrote:
On Tue, Nov 14, 2017 at 6:48 AM, Johnny Hughes johnny@centos.org wrote:
No idea how often CBS or the internal mirrors it uses are updated once I push an extras release.
I tried another build today (https://cbs.centos.org/koji/taskinfo?taskID=241860) and it failed to find ansible-2.4.1.0. I opened https://bugs.centos.org/view.php?id=14131 . Is "Extras" set up as an external repo in CBS for the ceph build targets?
- Ken
That happens when CBS/Koji doesn't know (yet) that new package[s] is/are available in those external repos : don't forget that the builders don't use the repomd metadata from those os/updates/extras repositories from source, but rather from what CBS/koji exposes.
The task to run "koji regen-repo" runs actually on demand and was triggered in the mean time, so it should be now available for all buildroots that have Extras enabled.
Hi Fabian,
Thanks for the explanation!
https://cbs.centos.org/koji/buildinfo?buildID=20774 failed on Nov 20th with the same error.
I'm looking at our ceph-jewel build tag:
$ cbs taginfo storage7-ceph-jewel-el7-build Tag: storage7-ceph-jewel-el7-build [740] Arches: x86_64 aarch64 ppc64le Groups: build, srpm-build Tag options: This tag is a buildroot for one or more targets Current repo: repo#51946: 2017-11-18 08:10:13.074984 Targets that build from this tag: storage7-ceph-jewel-el7 External repos: 2 centos7-cr (http://mirror.centos.org/centos/7/cr/$arch/) 3 centos7-extras (http://mirror.centos.org/centos/7/extras/$arch/) 5 centos7-updates (http://mirror.centos.org/centos/7/updates/$arch/) 10 centos7-os (http://mirror.centos.org/centos/7/os/$arch/) Inheritance: 5 .... buildsys7 [6] 10 .... storage7-ceph-jewel-candidate [737] 15 .... storage7-ceph-common-candidate [653] 20 .... storage7-common-candidate [119]
It looks like "extras" is enabled there, right? And it was regenerated Nov 18th, two days after your email.
What am I missing?
- Ken
Hi Ken,
Yes, I saw that failed build, and I even tried to ping you in #centos-devel to discuss this with you, but let's do it here Centos 7 extras is indeed enabled , *but* you have ansible specifically tagged in your repo , something you can see with (and also who added it) :
cbs list-pkgs --tag=storage7-ceph-jewel-el7-build|grep ansible
So it will pick the one that was "added" for that repo, and not the one from the "external" (from Koji PoV) repo, in this case centos 7 extras.
That's also what you can see from mock for that build:
cbs mock-config --task 244229 , that reveals the pkgs list : https://cbs.centos.org/kojifiles/repos/storage7-ceph-jewel-el7-build/51946/x... and so it shows ansible 2.3.1.0
At this point, you should probably sync with other SIG members and confirm that you can "remove" ansible from your SIG repo (if nobody else has a specific need for older ansible version) and so it will now use the one from Extras
See " cbs remove-pkg" to remove ansible from your tag[s] and then it should regenerate the internal repo metadata and combine that with the ones from external repos, and so start fetching pkgs from extras if same pkg (with different NVR) isn't declared in the internal tag/repo anymore
Hope this helps clarifying the situation
PS : if you confirm that it works, we'll also enhance the wiki / SIGGuide so that it will be documented for everybody in a central place
Hi Fabian,
Thank you very much for the details here. "cbs remove-pkg" worked great. We now pull ansible from the Extras external repository.
- Ken
On Mon, Nov 20, 2017 at 11:27 PM, Fabian Arrotin arrfab@centos.org wrote:
On 21/11/17 00:01, Ken Dreyer wrote:
On Thu, Nov 16, 2017 at 2:42 AM, Fabian Arrotin arrfab@centos.org wrote:
On 15/11/17 23:42, Ken Dreyer wrote:
On Tue, Nov 14, 2017 at 6:48 AM, Johnny Hughes johnny@centos.org wrote:
No idea how often CBS or the internal mirrors it uses are updated once I push an extras release.
I tried another build today (https://cbs.centos.org/koji/taskinfo?taskID=241860) and it failed to find ansible-2.4.1.0. I opened https://bugs.centos.org/view.php?id=14131 . Is "Extras" set up as an external repo in CBS for the ceph build targets?
- Ken
That happens when CBS/Koji doesn't know (yet) that new package[s] is/are available in those external repos : don't forget that the builders don't use the repomd metadata from those os/updates/extras repositories from source, but rather from what CBS/koji exposes.
The task to run "koji regen-repo" runs actually on demand and was triggered in the mean time, so it should be now available for all buildroots that have Extras enabled.
Hi Fabian,
Thanks for the explanation!
https://cbs.centos.org/koji/buildinfo?buildID=20774 failed on Nov 20th with the same error.
I'm looking at our ceph-jewel build tag:
$ cbs taginfo storage7-ceph-jewel-el7-build Tag: storage7-ceph-jewel-el7-build [740] Arches: x86_64 aarch64 ppc64le Groups: build, srpm-build Tag options: This tag is a buildroot for one or more targets Current repo: repo#51946: 2017-11-18 08:10:13.074984 Targets that build from this tag: storage7-ceph-jewel-el7 External repos: 2 centos7-cr (http://mirror.centos.org/centos/7/cr/$arch/) 3 centos7-extras (http://mirror.centos.org/centos/7/extras/$arch/) 5 centos7-updates (http://mirror.centos.org/centos/7/updates/$arch/) 10 centos7-os (http://mirror.centos.org/centos/7/os/$arch/) Inheritance: 5 .... buildsys7 [6] 10 .... storage7-ceph-jewel-candidate [737] 15 .... storage7-ceph-common-candidate [653] 20 .... storage7-common-candidate [119]
It looks like "extras" is enabled there, right? And it was regenerated Nov 18th, two days after your email.
What am I missing?
- Ken
Hi Ken,
Yes, I saw that failed build, and I even tried to ping you in #centos-devel to discuss this with you, but let's do it here Centos 7 extras is indeed enabled , *but* you have ansible specifically tagged in your repo , something you can see with (and also who added it) :
cbs list-pkgs --tag=storage7-ceph-jewel-el7-build|grep ansible
So it will pick the one that was "added" for that repo, and not the one from the "external" (from Koji PoV) repo, in this case centos 7 extras.
That's also what you can see from mock for that build:
cbs mock-config --task 244229 , that reveals the pkgs list : https://cbs.centos.org/kojifiles/repos/storage7-ceph-jewel-el7-build/51946/x... and so it shows ansible 2.3.1.0
At this point, you should probably sync with other SIG members and confirm that you can "remove" ansible from your SIG repo (if nobody else has a specific need for older ansible version) and so it will now use the one from Extras
See " cbs remove-pkg" to remove ansible from your tag[s] and then it should regenerate the internal repo metadata and combine that with the ones from external repos, and so start fetching pkgs from extras if same pkg (with different NVR) isn't declared in the internal tag/repo anymore
Hope this helps clarifying the situation
PS : if you confirm that it works, we'll also enhance the wiki / SIGGuide so that it will be documented for everybody in a central place
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 30/11/17 18:24, Ken Dreyer wrote:
Hi Fabian,
Thank you very much for the details here. "cbs remove-pkg" worked great. We now pull ansible from the Extras external repository.
- Ken
Well, just to let you know (and all people following this thread) that it seems Ansible disappeared from RHEL Extras, so it will be unmaintained at the CentOS Extras level too (and wondering even if pkg shouldn't disappear from that repo too)
So it appeared (again) in Epel : https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-74e062ae45
That also means that then CBS users will have to add it again (tag it) in their own targets, and Sandra already rebuilt 2.4.2 : https://cbs.centos.org/koji/buildinfo?buildID=20893
Really wondering why it appeared in RHEL extras and was removed ~1month later ...
-
Fabian Arrotin -
Johnny Hughes -
Ken Dreyer -
Thomas Oulevey