katello-4.3-rpm-pipeline 13 failed

Katello 4.3 pipeline failed:


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

[2022-01-11T19:25:12.070Z] # (in test file fb-katello-proxy.bats, line 60)
[2022-01-11T19:25:12.070Z] #   `hammer capsule content synchronize --id=$PROXY_ID --content-view="${CONTENT_VIEW}" --organization="${ORGANIZATION}"' failed with status 64
[2022-01-11T19:25:12.070Z] # Could not synchronize capsule content:
[2022-01-11T19:25:12.070Z] #   Error: Unrecognised option '--content-view'.
[2022-01-11T19:25:12.070Z] #   
[2022-01-11T19:25:12.070Z] #   See: 'hammer capsule content synchronize --help'.

Looks like this was added in:

@iballou you added this. It looks like install passes so is this by any chance a problem with an outdated Hammer cache? (We saw that earlier today: force hammer cache reload when enabling puppet · theforeman/forklift@3415064 · GitHub)

I’m going to guess it’s a hammer cache issue too. I can bring up the upgrade pipeline and see what happens.


Can you try to rekick the pipeline again to see if the error happens again? I talked with @iballou this morning and he is still looking into the issue but wants to see if it fails on the same step again.

Looks like it does:

I reproduced the issue locally, but it’s not a hammer cache problem. Even apipie was out of date. I had to run foreman-rake apipie:cache:index to get the --content-view[-id] option to pop up.

Perhaps we need to include this in Foreman 3.1 and do a new release.

I’d really love that, because if you fresh install and then enable puppet, you hit the same issue.
So I’d love if we could get it into 3.1 release.


Since it looks like an installer change, do you need me to do anything to push this along?

I’ve aligned Bug #34161: Katello 4.2 to 4.3 upgrade doesn't trigger apipie:cache:index, breaking some new hammer commands - Installer - Foreman to Foreman 3.1.1. During the next release meeting we should discuss a Foreman 3.1.1 release. I’ve opened an agenda:

So right now I don’t think there’s anything else to do.

1 Like

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