Foreman RPM nightly pipeline failed:
foreman-pipeline-foreman-nightly-centos8-install (failed)
foreman-pipeline-foreman-nightly-centos7-install (passed)
foreman-pipeline-foreman-nightly-centos8-upgrade (failed)
foreman-pipeline-foreman-nightly-centos7-upgrade (passed)
Looks like an issue with proxy on el8:
[ERROR ] [configure] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[pipeline-foreman-server-nightly-centos8.n2.example.com]: Could not evaluate: Proxy pipeline-foreman-server-nightly-centos8.n2.example.com cannot be retrieved: unknown error (response 503)and sos report doesn’t seem to include foreman sos data
But it does include SELinux denials, see my comment in https://github.com/theforeman/puppet-foreman/pull/883
should fix that
nope, the file still get’s created as var_run_t, not foreman_var_run_t and then things explode.
next try!
so foreman-selinux is now correct, but systemd requires a systemctl daemon-reexec to know about these new file contexts, as otherwise it will still create the file as var_run_t 
and this was now implemented:
pipeline was green again
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.