Skip to content
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.

Sign up for GitHub

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

Jump to bottom

systemd presets for units from ignition don't get evaluated #243

Closed
yuqi-zhang opened this issue Aug 27, 2018 · 9 comments
Closed

systemd presets for units from ignition don't get evaluated #243

yuqi-zhang opened this issue Aug 27, 2018 · 9 comments
Assignees
@cgwalters

Comments

@yuqi-zhang
Copy link
Contributor

Doing -b rhcos with ami ami-0fc9356f07902b569 shows the following failure:

 --- FAIL: coreos.ignition.v2.once (123.83s)
        cluster.go:117: "test ! -e /etc/ignition-ran" failed: output , status Process exited with status 1

The original test does: sudo rm /etc/ignition-ran and reboots the machine. It seems that the reboot has re-created the file.

Raising issue here as suggested by @arithx. Original mantle issue: coreos/mantle#905
@dustymabe
Copy link
Member

what does sudo journalctl -b 0 -u ignition-files.service show ?

@yuqi-zhang
Copy link
Contributor Author

After reboot: https://paste.fedoraproject.org/paste/gl47Xr76MgTmFSQJAtadrw

@dustymabe
Copy link
Member

yeah it looks like ignition is running on every boot because the /boot/coreos-firstboot is not getting deleted. It looks like coreos-firstboot-complete.service from https://github.com/dustymabe/ignition-dracut/pull/12 is not getting run.

@dustymabe
Copy link
Member

looks like an issue with systemd presets not getting evaluated as mentioned here coreos/ignition#624 (comment) - maybe we need a new issue to track that.

@yuqi-zhang
Copy link
Contributor Author

@dustymabe Where would be a good place to track this issue?

@dustymabe
Copy link
Member

we could probably just rename this issue to "systemd presets for units from ignition don't get evaluated" and track it here.

@yuqi-zhang yuqi-zhang changed the title Kola AWS test failure: shows Ignition running multiple times systemd presets for units from ignition don't get evaluated Aug 28, 2018
@rphillips
Copy link

I booted the latest Fedora Atomic Host which contains systemd version 238. The rhcos image has systemd 219 (from ~2015).

@dustymabe
Copy link
Member

I booted the latest Fedora Atomic Host which contains systemd version 238. The rhcos image has systemd 219 (from ~2015).

I don't think that's relevant. We are and have been using an EL7 base. This was working and broke recently.

@cgwalters cgwalters self-assigned this Aug 28, 2018
@cgwalters cgwalters mentioned this issue Aug 28, 2018
Merged
cgwalters added a commit to cgwalters/os that referenced this issue Aug 28, 2018
@cgwalters
manifest: Explicitly set machineid-compat: false at toplevel
2bc22b2 
It looks like the include logic in rpm-ostree isn't handling
this correctly.

Closes: openshift#243
@cgwalters
Copy link
Member

PR in #247

cgwalters added a commit to cgwalters/os that referenced this issue Aug 28, 2018
@cgwalters
manifest: Explicitly set machineid-compat: false at toplevel
a29b16b 
It looks like the include logic in rpm-ostree isn't handling
this correctly.

Closes: openshift#243
@dustymabe dustymabe mentioned this issue Sep 7, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cgwalters cgwalters

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rphillips @cgwalters @dustymabe @yuqi-zhang