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

Ignition should fail validation if files/links/dirs conflict with systemd units or drop ins #881

Closed
ajeddeloh opened this issue Oct 24, 2019 · 0 comments · Fixed by #1456
Assignees
Labels

Comments

@ajeddeloh
Copy link
Contributor

ajeddeloh commented Oct 24, 2019

Bug

Operating System Version

Any

Ignition Version

All

Environment

All

Expected Behavior

Ignition should disallow internally inconsistent configs

Actual Behavior

Users can specify a file at /etc/systemd/system/unitname.service and a systemd unit that would also write a file to that location. Unit drop-ins have the same problem.

@sohankunkerkar sohankunkerkar self-assigned this Aug 26, 2020
sohankunkerkar added a commit to sohankunkerkar/ignition that referenced this issue Aug 28, 2020
Fixes coreos#881
Ignition should panic when users try to overwrite the existing files
sohankunkerkar added a commit to sohankunkerkar/ignition that referenced this issue Aug 28, 2020
Fixes coreos#881
Ignition should panic when users try to overwrite the existing files
sohankunkerkar added a commit to sohankunkerkar/ignition that referenced this issue Aug 28, 2020
Fixes coreos#881
Ignition should panic when users try to overwrite the existing files
@sohankunkerkar sohankunkerkar removed their assignment Sep 7, 2021
@marmijo marmijo added jira for syncing to jira and removed jira for syncing to jira labels May 26, 2022
@marmijo marmijo self-assigned this May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment