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

Simplify system compatibility check logic and improve error reporting. #8727

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

opencmit2
Copy link

@opencmit2 opencmit2 commented Apr 18, 2024

Description

Simplify system compatibility check logic and improve error reporting.

In the CI validation step, confirm whether spaces and tabs #8654

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

TBD

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

Signed-off-by: JinXinWang <opencmit2@126.com>
@opencmit2 opencmit2 requested a review from a team as a code owner April 18, 2024 02:07
@marvin-tigera marvin-tigera added this to the Calico v3.29.0 milestone Apr 18, 2024
@marvin-tigera marvin-tigera added release-note-required Change has user-facing impact (no matter how small) docs-pr-required Change is not yet documented labels Apr 18, 2024
@caseydavenport
Copy link
Member

@opencmit2 thanks for the PR - If I understand correctly, this changes behavior where the command will now no longer print out all detected problems, and instead will only print out the first problem. Is this desirable?

Could you provide a bit more context for why this is an important change?

@opencmit2
Copy link
Author

@caseydavenport
I think this is reasonable. If the kernel version is not suitable, there is no need to check the following kernel modules. If the kernel version is suitable, the following kernel modules will also be checked in sequence.

1714093993176

@caseydavenport
Copy link
Member

I generally don't want to make changes in behavior unless we can point to a specific problem it is solving. In this case, I am not sure there is one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-pr-required Change is not yet documented release-note-required Change has user-facing impact (no matter how small)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants