katello-nightly-rpm-pipeline 210 failed

Infra & CI
1

Katello nightly pipeline failed:

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

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

2

The current failure is:


TASK [foreman_proxy_content : Generate Certs] **********************************
fatal: [pipeline-katello-proxy-nightly-centos7 -> 192.168.121.161]: FAILED! => changed=true 
  cmd:
  - foreman-proxy-certs-generate
  - --foreman-proxy-fqdn
  - pipeline-katello-proxy-nightly-centos7.n58.example.com
  - --certs-tar
  - /root/pipeline-katello-proxy-nightly-centos7.n58.example.com.tar.gz
  delta: '0:00:12.457965'
  end: '2019-09-22 22:45:32.535891'
  msg: non-zero return code
  rc: 21
  start: '2019-09-22 22:45:20.077926'
  stderr: |-
    tput: unknown terminal "unknown"
    tput: unknown terminal "unknown"
    Parameter parent-fqdn invalid: nil is not a valid string
    Parameter foreman-proxy-cname invalid: Elements of the array are invalid: [] must match one of (?-mix:^(([a-zA-Z0-9]|[a-zA-Z0-9][a-zA-Z0-9\-]*[a-zA-Z0-9])\.)*([A-Za-z0-9]|[A-Za-z0-9][A-Za-z0-9\-]*[A-Za-z0-9])$)

@ekohl This looks related to https://github.com/theforeman/puppet-certs/pull/256

3

This uncovered a few issues. First of all, that PR was incomplete:

Then I found that we need to configure the class mapping to look for the right params class because that’s not automatic:

This uncovered a bug in kafo (which the above PR works around):

4

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