katello-nightly-rpm-pipeline 1166 failed

[jenkins]

Katello nightly pipeline failed:

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

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

[evgeni]

Now this is interesting.

EL7 failed with:

[2021-12-15T01:09:44.132Z] e[0;32m    not ok 7 sync just one content view to the proxye[0m
[2021-12-15T01:09:44.136Z] e[0;32m    # (in test file fb-katello-proxy.bats, line 60)e[0m
[2021-12-15T01:09:44.136Z] e[0;32m    #   `hammer capsule content synchronize --id=$PROXY_ID --content-view="${CONTENT_VIEW}" --organization="${ORGANIZATION}"' failed with status 64e[0m
[2021-12-15T01:09:44.136Z] e[0;32m    # Could not synchronize capsule content:e[0m
[2021-12-15T01:09:44.136Z] e[0;32m    #   Error: Unrecognised option '--content-view'.e[0m
[2021-12-15T01:09:44.136Z] e[0;32m    #e[0m
[2021-12-15T01:09:44.136Z] e[0;32m    #   See: 'hammer capsule content synchronize --help'.e[0m

Which is a new test @iballou added in https://github.com/theforeman/forklift/pull/1450, BUT it works fine in the non-upgrade case.

Makes me wonder if there is an issue with hammer not detecting a new apidoc?

And EL8 is still failing the upgrade on Foreman 3.1/Katello 4.3: pulpcore has newer version of createrepo_c-libs on CentOS 8 stream, which I am working on.

[evgeni]

The EL7 failure is now Bug #34161: Katello 4.2 to 4.2 upgrade doesn't trigger apipie:cache:index, breaking some new hammer commands - Installer - Foreman

[evgeni]

And EL7 is now fixed, thanks @ekohl!

EL8 needs some further discussion, see https://github.com/theforeman/pulpcore-packaging/pull/353 for details