-
Notifications
You must be signed in to change notification settings - Fork 159
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
overlay.d: add service to check for unique-boot after ignition #1540
Conversation
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/coreos-ignition-unique-boot.service
Outdated
Show resolved
Hide resolved
16684d5
to
62c3369
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't do an in-depth analysis here, but this seems sane to me.
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/coreos-boot-edit.sh
Outdated
Show resolved
Hide resolved
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/coreos-ignition-unique-boot.service
Outdated
Show resolved
Hide resolved
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/coreos-ignition-unique-boot.service
Outdated
Show resolved
Hide resolved
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/coreos-ignition-unique-boot.service
Outdated
Show resolved
Hide resolved
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/module-setup.sh
Outdated
Show resolved
Hide resolved
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/coreos-ignition-unique-boot.service
Outdated
Show resolved
Hide resolved
62c3369
to
249d29a
Compare
249d29a
to
3451b1c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @nikita-dubrovskii and @sohankunkerkar!
which is interesting. This runs right after Hmm, but actually I think we could have |
3451b1c
to
c50de40
Compare
overlay.d/05core/usr/lib/dracut/modules.d/35coreos-ignition/coreos-ignition-unique-boot.service
Outdated
Show resolved
Hide resolved
f145d16
to
dae4c54
Compare
using this with coreos/coreos-installer#813 fixes CI (locally) |
This is pending a new coreos-installer release. |
After ignition's stages partition table could be modified, and therefore kernel may have an old picture of disks and partitions. During verification we force kernel to reread the partition table for each disk and call udevsettle, which in turn leads to modification of "/dev/disk/by-*/*" symlinks and systemd may send SIGTERM to services with "Require=dev-disk-by\x2dlabel-boot.device". To avoid that this checks for the unique fs labeled 'boot' after ignition's disks stage was finished but before mounting stage. Issue: coreos/fedora-coreos-tracker#1105 Signed-off-by: Nikita Dubrovskii <[email protected]>
dae4c54
to
710ba7d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have new enough coreos-installer now, so this is unblocked.
LGTM!
I restarted CI here to make sure it tests on top of the latest. Let's rerun it multiple times before merging this to try to make sure we're not introducing flakiness again. Edit: I've now enabled auto-merge after restarting the test three times. Ideally, we should add tests for both |
After ignition's stages partition table could be modified, and therefore
kernel may have an old picture of disks and partitions. During verification
we force kernel to reread the partition table for each disk and call udevsettle,
which in turn leads to modification of "/dev/disk/by-/" symlinks and systemd
may send SIGTERM to services with "Require=dev-disk-by\x2dlabel-boot.device".
To avoid that this checks for the unique fs labeled 'boot' after ignition's
disks stage was finished but before mounting stage.
Issue: coreos/fedora-coreos-tracker#1105