-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove NVME-related UUID from images /usr/etc/nvme/hostid
/usr/etc/nvme/hostnqn
#1519
Comments
/usr/etc/nvme/hostid
/usr/etc/nvme/hostnqn
/usr/etc/nvme/hostid
/usr/etc/nvme/hostnqn
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
OpenShift image has the NVMe `hostid` and `hostnqn` hardcoded, so it ends up being the same in all the control plane nodes, which is problematic. This `MachineConfig` fixes this issue by recreating both files when the `hostid` doesn't match the system-uuid of the machine it is running on. Bugs: - https://issues.redhat.com/browse/OCPBUGS-34629 - openshift/os#1519 - openshift/os#1520
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
/remove-lifecycle rotten |
In Fedora and EL10 the %post that generates this was removed:
I'm not sure if there are supporting changes made in I do know if I implement this change to |
I guess either way we don't want the same ID baked in so what we have right now is clearly wrong. We can start with deleting them and then if we need to generate them on first boot for EL9 we can create a service to do that. |
See: #1445 (comment)
There are apparently hardcoded NMVE ids in the images right now and we should remove those to make sure those are unique and generated per-node.
The text was updated successfully, but these errors were encountered: