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
Bug 2062355: Collect NMState resources when operator is installed #292
Bug 2062355: Collect NMState resources when operator is installed #292
Conversation
Skipping CI for Draft Pull Request. |
/retitle Bug 2062355: Collect NMState resources when operator is installed |
@creydr: This pull request references Bugzilla bug 2062355, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test all |
/bugzilla refresh |
@creydr: This pull request references Bugzilla bug 2062355, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@creydr: This pull request references Bugzilla bug 2062355, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@cybertron @qinqon @rhrazdil: fyi |
@creydr: This pull request references Bugzilla bug 2062355, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@creydr we have a must-gather bits to retrieve knmstate stuff at openshift virtualization, maybe you can take inspiration from there. UPDATE: This is the place https://github.com/kubevirt/must-gather/blob/main/collection-scripts/gather#L16 |
110a945
to
5cf76c5
Compare
@creydr: This pull request references Bugzilla bug 2062355, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -0,0 +1,28 @@ | |||
#!/bin/bash |
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.
Do we fail must-gather if one of the script fails ? for that we need to do set -e
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.
That's probably something @RickJWagner or @sferich888 can answer better
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.
Given that must-gather might run in clusters that are having problems, we should probably tend to be more forgiving of errors. (And let things run as bullet-proof as possible, even if it means we give extra leniency to components that don't complete their jobs error-free.) We'd prefer to get as much information as possible, even if some pieces of information are unavailable.
Signed-off-by: Christoph Stäbler <cstabler@redhat.com>
5cf76c5
to
45e1589
Compare
/assign @RickJWagner |
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.
This looks good to me.
One point to consider: There's a lot of similarity between gather_nmstate and scripts like gather_metallb_logs. Maybe consider factoring out the common stuff into a script that could be sourced by other scripts. (DRY).
Tried it locally, looks like it captured everything we need. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: amalykhi, creydr, cybertron, RickJWagner The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all |
/retest-required |
1 similar comment
/retest-required |
/test e2e-aws |
2 similar comments
/test e2e-aws |
/test e2e-aws |
/retest-required |
/test e2e-aws |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@creydr: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@creydr: All pull requests linked via external trackers have merged: Bugzilla bug 2062355 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.10 |
@creydr: new pull request created: #294 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Currently we are missing the NMState resources in the must-gathers. This is especially a problem as the kubernetes-nmstate-operator became GA in 4.10.
This PR addresses it and adds the NMState resources (namespace resources & CRs) to the must-gathers when the operator is installed.
Hints for reviewers:
I was following a similar approach to how MetalLB is collecting its resources (./collection-scripts/gather_metallb_logs). If there is an easier way (e.g. by adding a certain annotation), please let me know.
How to verify:
oc -n openshift-nmstate get po -w
)omg get nnce
)