where should we build nsible-2.4.1 in CBS?

Hi folks,

The latest ceph-ansible version requires ansible- now, due to
some regressions in ansible-

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


Re: where should we build nsible-2.4.1 in CBS?

By Thomas Oulevey at 11/14/2017 - 08:32


On 11/13/17 20:03, Ken Dreyer wrote:

Quick note. It looks like Red Hat is pushing, today :

<a href="" title=""></a>

So it will be available in `extras` soon.

Re: where should we build nsible-2.4.1 in CBS?

By Johnny Hughes at 11/14/2017 - 09:20

On 11/14/2017 06:32 AM, Thomas Oulevey wrote:
There was just a release today for ansible- 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).

Re: where should we build nsible-2.4.1 in CBS?

By Johnny Hughes at 11/14/2017 - 09:48

On 11/14/2017 07:20 AM, Johnny Hughes wrote:
I just pushed this to the master centos mirror .. should be on all of in 30 or so mins.

No idea how often CBS or the internal mirrors it uses are updated once I
push an extras release.

Johnny Hughes

Re: where should we build nsible-2.4.1 in CBS?

By Ken Dreyer at 11/15/2017 - 18:42

On Tue, Nov 14, 2017 at 6:48 AM, Johnny Hughes < ... at centos dot org> wrote:
I tried another build today
(<a href="" title=""></a>) and it failed to
find ansible- I opened
<a href="" title=""></a> . Is "Extras" set up as an
external repo in CBS for the ceph build targets?

- Ken

Re: where should we build nsible-2.4.1 in CBS?

By Fabian Arrotin at 11/16/2017 - 05:42

On 15/11/17 23:42, Ken Dreyer wrote:
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

Re: where should we build nsible-2.4.1 in CBS?

By Ken Dreyer at 11/20/2017 - 19:01

On Thu, Nov 16, 2017 at 2:42 AM, Fabian Arrotin < ... at centos dot org> wrote:
Hi Fabian,

Thanks for the explanation!

<a href="" title=""></a> 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:
External repos:
2 centos7-cr ($arch/)
3 centos7-extras ($arch/)
5 centos7-updates ($arch/)
10 centos7-os ($arch/)
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

Re: where should we build nsible-2.4.1 in CBS?

By Fabian Arrotin at 11/21/2017 - 02:27

On 21/11/17 00:01, Ken Dreyer wrote:
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 :
<a href="" title=""></a>
and so it shows ansible

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

Re: where should we build nsible-2.4.1 in CBS?

By Ken Dreyer at 11/30/2017 - 13:24

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 < ... at centos dot org> wrote:

Re: where should we build nsible-2.4.1 in CBS?

By Fabian Arrotin at 12/01/2017 - 04:31

On 30/11/17 18:24, Ken Dreyer wrote:
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 :
<a href="" title=""></a>

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 :
<a href="" title=""></a>

Really wondering why it appeared in RHEL extras and was removed ~1month
later ...