-
Notifications
You must be signed in to change notification settings - Fork 53
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
strict elemental setup #2201
strict elemental setup #2201
Conversation
frelon
commented
Oct 2, 2024
- Use --strict flag in elemental-setup services
- Set SilenceUsage for run-stage command
196c69c
to
e10fd8a
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.
Would be nice having some integration tests for that. What about setting some cloud-config in installation tests we know it will fail, so that we can check it still boots but on a degraded state, as some elemental-setup-*
service failed. Even more, ideally we should be capable to see the failure in journalctl.
Alternatively, we also use such a process for the fallback test. Imagine we set a health check test that reports error if systemd is on degraded state.
Essentially, we should define the behavior we expect on a cloud-config failure and then add an integration tests to exercise it.
@davidcassany This is true, I will look into some tests in this PR before merging! |
e10fd8a
to
d09e23f
Compare
Pull request was converted to draft
35eebe5
to
e50fa11
Compare
I am trying to implement a test for that, I think it should be relatively straight forward and I think this would cover the most important from integration test perspective. |
The default behavior has been to hide any errors and only log warnings. Using the --strict flag will ensure any yip errors are actually reported. Signed-off-by: Fredrik Lönnegren <[email protected]>
This ensures we do not show the usage text for errors caught during yip execution. Signed-off-by: Fredrik Lönnegren <[email protected]>
Signed-off-by: David Cassany <[email protected]>
…s a degraded systemd status Signed-off-by: David Cassany <[email protected]>
e50fa11
to
8d609b2
Compare
Checked manually that failures show up in journal, I don't think we need explicit test for that. |
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.
LGTM