Master tripleo component is red
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
It seems a change related to HAProxy is causing issues in the tripleo component:
http://
WARNING | ERROR: Can't run container container-
stderr: time="2023-
time="2023-
time="2023-
time="2023-
time="2023-
time="2023-
time="2023-
time="2023-
+ /usr/bin/puppet apply --summarize --detailed-
+ logger -s -t puppet-user
<13>Jan 24 20:03:00 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:04 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:04 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:04 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:04 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:04 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:04 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:04 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:06 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:06 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:06 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:06 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:06 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:06 puppet-user: Warning: Facter: Could not delete cache: Read-only file system @ apply2files - /opt/puppetlabs
<13>Jan 24 20:03:07 puppet-user: Warning: Found multiple default providers for service: pacemaker_xml, swiftinit, base; using pacemaker_xml
<13>Jan 24 20:03:09 puppet-user: Warning: /etc/puppet/
<13>Jan 24 20:03:09 puppet-user: (file: /etc/puppet/
<13>Jan 24 20:03:09 puppet-user: Warning: Undefined variable '::deploy_
<13>Jan 24 20:03:09 puppet-user: (file & line not available)
<13>Jan 24 20:03:10 puppet-user: Warning: Scope(Haproxy:
<13>Jan 24 20:03:10 puppet-user: Warning: Scope(Haproxy:
<13>Jan 24 20:03:10 puppet-user: Warning: Scope(Haproxy:
<13>Jan 24 20:03:10 puppet-user: Warning: Scope(Haproxy:
<13>Jan 24 20:03:10 puppet-user: Warning: Scope(Haproxy:
<13>Jan 24 20:03:10 puppet-user: Warning: Unknown variable: '::pacemaker:
<13>Jan 24 20:03:10 puppet-user: Warning: Scope(Haproxy:
<13>Jan 24 20:03:10 puppet-user: Warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored (file: /etc/puppet/
<13>Jan 24 20:03:10 puppet-user: Warning: Scope(Haproxy:
<13>Jan 24 20:03:10 puppet-user: Error: Evaluation Error: Error while evaluating a Resource Statement, Haproxy:
+ rc=1
+ '[' false = false ']'
+ set +x
2023-01-24 15:03:48.839506 | fa163e7c-
2023-01-24 15:03:48.839994 | fa163e7c-
this seems to be related to https:/ /github. com/puppetlabs/ puppetlabs- haproxy/ commit/ 95ca912f77966ed 0da7a5bec9265cd acbf09da4c
puppet- haproxy- 6.4.1-0. 20230124153846. 95ca912. el9.noarch picked up this change.
I am testing this workaround:
"dnf downgrade -y puppet-haproxy"
that rolls back to:
6.4.1-0. 20230118145422. 9fbf4e6. el9
We should probably pin this for the time being.