-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
fix(multus): loop_control template error when item is None #10347
fix(multus): loop_control template error when item is None #10347
Conversation
Hi @nicolas-goudry. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
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.
Thanks for your contribution :D!
/lgtm
Thanks @nicolas-goudry |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MrFreezeex, nicolas-goudry, yankay 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 |
…s-sigs#10347) (kubernetes-sigs#10726) Co-authored-by: Nicolas Goudry <nicolas-goudry@users.noreply.github.com> (cherry picked from commit 336b323)
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR avoids the loop_control templating to fail when item is None, which happens when the run of
upgrade-cluster.yml
is limited with--limit
(see the issue it fixes for further details).Which issue(s) this PR fixes:
Fixes #9703
Special notes for your reviewer:
Does this PR introduce a user-facing change?: