katello-nightly-rpm-pipeline 1369 failed

Infra & CI
1

Katello nightly pipeline failed:

https://ci.theforeman.org/job/katello-nightly-rpm-pipeline/1369/

foreman-pipeline-katello-nightly-centos8-stream-upgrade (failed) (remote job)
foreman-pipeline-katello-nightly-almalinux8-install (failed) (remote job)
foreman-pipeline-katello-nightly-centos8-stream-install (failed) (remote job)
foreman-pipeline-katello-nightly-almalinux8-upgrade (failed) (remote job)

2

I see failures which mention Simple Content access. Could anyone from @katello take a look? I’m not sure if this is a recent change in Katello, subscription-manager or something else.

3

The “SCA orgs can’t attach subs” check has been there for a while: https://github.com/Katello/katello/pull/8746
Wonder why it started happening now.

4

Aha!

There is a new candlepin in nightly (candlepin-4.2.3-1.el8 | Build Info | koji) which has the following in the changelog:

4.2.1-1
…
- ENT-3756: Implementation of SCA-by-default for newly created Owners

I guess that’s it?

5

Yes, that’s it. The new Candlepin build is going to require some dev effort to unbreak things around SCA because its behavior has changed in significant ways:

  • content access mode is now attached to the org, not the consumer (manifest)
  • Toggling SCA should not reach out to upstream Candlepin anymore
  • new orgs will now default to SCA, so we need to make Katello respect that even when a manifest is not imported

etc.

We need to make all the changes above. @cintrix84 & Candlepin folks can help if you need more details…

6

Are there issues tracking this? Can we unbreak the pipeline in the short term?

7

Should we just untag that candlepin build for the moment? Until Katello can handle it?

2 Likes
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.