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.

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-sysusers: change execution order #3720

Merged
merged 1 commit into from
Jan 22, 2024

Conversation

arnaldo2792
Copy link
Contributor

Description of changes:

systemd-sysusers might run while the /etc tmpfs filesystem is still being set up, which results on failures on the service when it tries to read SELinux configuration files. With this change, systemd-sysusers is forced to run after the required SELinux configuration files are in place.

Testing done:

  • I confirmed systemd-sysusers runs after selinux-policy-files.
  • There weren't any new warnings when I ran journalctl -p4.
  • systemctl status shows the system is running

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

Copy link
Contributor

@yeazelm yeazelm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

systemd-sysusers might run while the /etc tmpfs filesystem is still
being set up, which results on failures on the service when it tries to
read SELinux configuration files. With this change, systemd-sysusers is
forced to run after the required SELinux configuration files are in
place.

Signed-off-by: Arnaldo Garcia Rincon <[email protected]>
@arnaldo2792
Copy link
Contributor Author

(Forced push removes the unnecessary section)

@arnaldo2792 arnaldo2792 merged commit 5653daa into bottlerocket-os:develop Jan 22, 2024
52 checks passed
@ginglis13 ginglis13 mentioned this pull request Jan 24, 2024
9 tasks
@arnaldo2792 arnaldo2792 deleted the systemd-sysusers branch January 29, 2024 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants