Thanks for reporting your issue!
In order for the CoreOS team to be able to triage your issue, please copy the applicable parts of the following template into a comment and fill them out as completely as possible.
Be ready for follow-up questions and please respond in a timely manner.
If we can't reproduce a bug, we might close your issue.
OCP Version at Install Time:
RHCOS Version at Install Time:
OCP Version after Upgrade (if applicable):
RHCOS Version after Upgrade (if applicable):
Platform (AWS, Azure, bare metal, GCP, vSphere, etc.):
Architecture (x86_64, ppc64le, s390x, etc.):
If you're having problems booting/installing RHCOS, please provide:
- Reproduction steps that work with a single RHCOS node
- The full contents of the serial console showing disk initialization, network configuration, and Ignition stages. See this article for information about configuring your serial console. Screenshots or a video recording of the console is usually not sufficient.
- Ignition JSON
- Output of journalctl -b
If you're having problems post-upgrade, please provide:
- A complete must-gather (oc adm must-gather)
If you're having SELinux related issues, please provide:
- The full /var/log/audit/audit.log file
- Were any SELinux modules or booleans changed from the default configuration?
- The output of ostree admin config-diff | grep selinux/targeted on impacted nodes
Please add anything else that might be useful, for example:
- Kernel command line (cat /proc/cmdline)
- Contents of /etc/NetworkManager/system-connections/
- Contents of /etc/sysconfig/network-scripts/
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Important: OpenShift Container Platform 4.11.27 security update), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:0651