-
Notifications
You must be signed in to change notification settings - Fork 105
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
systemd units created by Ignition don't have their symlinks created #105
Comments
It might be simplest to change Ignition to run Alternatively, we could try to change things so that we don't do any presets when building images and do it on first boot. I'm...uncertain about the complexity of that. |
Related: coreos/bugs#2244 |
coreos/ignition-dracut#11 also seems to be related? Update: yup, can close this issue once the PR gets merged i think. |
This was fixed. |
Yup, can confirm it, I see the following behaivor on the newly built ami image. The ami id is ami-0918132e44967d193, built on July 27th
|
Ignition expects that
systemd-preset
will run and take care of creating relevant symlinks.As a result currently any systemd unit created by Ignition will not run despite being enabled.
Per @cgwalters
systemd-preset
won't run on RHCOS:that's another consequence of the
ConditionFirstBoot=
not being set - it only works for systems with empty/etc
(neither classic fedora/rhel nor ostree-based systems)The text was updated successfully, but these errors were encountered: