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

strict elemental setup #2201

Merged
merged 4 commits into from
Nov 6, 2024
Merged

strict elemental setup #2201

merged 4 commits into from
Nov 6, 2024

Conversation

frelon
Copy link
Contributor

@frelon frelon commented Oct 2, 2024

  • Use --strict flag in elemental-setup services
  • Set SilenceUsage for run-stage command

@frelon frelon requested a review from a team as a code owner October 2, 2024 11:40
@frelon frelon enabled auto-merge (rebase) October 2, 2024 12:03
Copy link
Contributor

@davidcassany davidcassany left a 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.

@frelon
Copy link
Contributor Author

frelon commented Oct 11, 2024

@davidcassany This is true, I will look into some tests in this PR before merging!

@frelon frelon linked an issue Oct 25, 2024 that may be closed by this pull request
5 tasks
@frelon frelon marked this pull request as draft October 25, 2024 08:15
auto-merge was automatically disabled October 25, 2024 08:15

Pull request was converted to draft

@frelon frelon force-pushed the strict-elemental-setup branch 2 times, most recently from 35eebe5 to e50fa11 Compare October 28, 2024 09:33
@davidcassany
Copy link
Contributor

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.

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.

frelon and others added 4 commits November 6, 2024 13:06
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]>
@davidcassany
Copy link
Contributor

Checked manually that failures show up in journal, I don't think we need explicit test for that.

@davidcassany davidcassany marked this pull request as ready for review November 6, 2024 13:41
Copy link
Contributor

@davidcassany davidcassany left a comment

Choose a reason for hiding this comment

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

LGTM

@frelon frelon enabled auto-merge (rebase) November 6, 2024 13:43
@frelon frelon merged commit 59c79a3 into rancher:main Nov 6, 2024
28 checks passed
@frelon frelon deleted the strict-elemental-setup branch November 6, 2024 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Enable strict elemental-setup
2 participants