-
Notifications
You must be signed in to change notification settings - Fork 109
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
Stop enabling afterburn-hostname.service
on GCP
#1432
Comments
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 |
/remove-lifecycle stale |
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 |
/remove-lifecycle stale |
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 |
/remove-lifecycle stale |
Right now, RHCOS is carrying a patch for Afterburn to have it write to
/etc/hostname
(basically coreos/afterburn#512).There's a lot of backstory on this also in coreos/afterburn#509. But IIUC, now that NM correctly shortens DHCP hostnames that are too long, we can rely on hostname setting via DHCP again and stop carrying that patch.
A big change here of course is that we'd no longer physically write
/etc/hostname
from the initramfs. Need to verify this doesn't break things. (Though presumably this works in OKD + FCOS today, where we don't have that patch.)The text was updated successfully, but these errors were encountered: