katello-nightly-rpm-pipeline 385 failed

Katello nightly pipeline failed:

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

foreman-katello-upgrade-nightly-test (failed)
foreman-katello-nightly-test (passed)

TASK [foreman_proxy_content : Detect certs generate] ***************************
fatal: [pipeline-upgrade-katello-proxy-nightly-centos7 -> 192.168.121.83]: FAILED! => changed=true 
  cmd:
  - which
  - foreman-proxy-certs-generate
  delta: '0:00:00.005387'
  end: '2020-02-04 22:45:43.932201'
  msg: non-zero return code
  rc: 1
  start: '2020-02-04 22:45:43.926814'
  stderr: 'which: no foreman-proxy-certs-generate in (/sbin:/bin:/usr/sbin:/usr/bin)'
  stderr_lines: <omitted>
  stdout: ''
  stdout_lines: <omitted>
...ignoring
Tuesday 04 February 2020  22:45:44 +0000 (0:00:00.807)       0:09:12.996 ****** 
Tuesday 04 February 2020  22:45:44 +0000 (0:00:00.807)       0:09:12.996 ****** 
Tuesday 04 February 2020  22:45:44 +0000 (0:00:00.171)       0:09:13.168 ****** 
Tuesday 04 February 2020  22:45:44 +0000 (0:00:00.171)       0:09:13.168 ****** 

TASK [foreman_proxy_content : Generate Certs] **********************************
fatal: [pipeline-upgrade-katello-proxy-nightly-centos7 -> 192.168.121.83]: FAILED! => changed=false 
  cmd: capsule-certs-generate --capsule-fqdn pipeline-upgrade-katello-proxy-nightly-centos7.n1.example.com --certs-tar /root/pipeline-upgrade-katello-proxy-nightly-centos7.n1.example.com.tar.gz
  msg: '[Errno 2] No such file or directory'
  rc: 2

So the chain of events causing this is:

  1. the package ‘katello’ isn’t being installed
  2. katello requires foreman-installer-katello, so since katello isn’t
    installed, that isn’t either
  3. foreman-installer-katello provides the foreman-proxy-certs-generate
    command, but since that isn’t present, it tries to use the (older)
    command capsule-certs-generate, which isn’t there either

Now why is the ‘katello’ package not being installed? I was not able to
figure it out, it worked for both eric and I when we tried it. Will dig
some more…

huh, this is very odd… looks like 386 passed, so maybe it was in fact due to the issue in epel that somehow broke some dependency resolution or something?

very strange, i guess that could have been it?

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