Please fill out the template entirely: Thanks for reporting your issue! In order for the CoreOS team to be able to quickly and successfully triage your issue, please fill out the following template 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 What are you trying to do? What is your use case? What happened? What went wrong or what did you expect? What are the steps to reproduce your issue? Please try to reduce these steps to something that can be reproduced with a single RHCOS node. If you're having problems booting/installing RHCOS, please provide: - the full contents of the serial console showing disk initialization, network configuration, and Ignition stage (see https://access.redhat.com/articles/7212 for information about configuring your serial console) - 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/`
Hmm, indeed this error is similar to https://bugzilla.redhat.com/show_bug.cgi?id=2006690. But if I understand https://bugzilla.redhat.com/show_bug.cgi?id=2006690#c5 correctly, this was fixed when we removed fallback.efi, which we did backport to 4.8 in https://github.com/coreos/coreos-assembler/pull/2437. Can you confirm that the latest 4.8 ISO is being used? Also as a test, does booting the 4.10 live ISO work? I'm confused though that you also have a screenshot of Ignition output. How did you get there if the live ISO boot failed? Can you clarify the exact order of events?
Can they reproduce this issue with the 4.6 installation ISO that was used to install the cluster? They don't need to and should not use a newer installations media to install new nodes in a cluster as they get updated on first boot.