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 2039373: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf #1107
Bug 2039373: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf #1107
Conversation
@mandre: This pull request references Bugzilla bug 2039373, 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. |
@mandre: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
/retest |
1 similar comment
/retest |
secret, err = os.secretLister.Secrets(os.secretNamespace).Get(os.secretName) | ||
if err != nil { | ||
klog.Infof("failed to get cloud.conf from secret (try %d), retrying after %d seconds. Error was: %v", i, i, err) | ||
time.Sleep(time.Duration(i) * time.Second) |
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.
Same comment as #1099 (comment) applies
The OpenStack secret is not guaranteed to be present at the time kube-controller-manager is initialised. Co-authored-by: Martin André <m.andre@redhat.com> Co-authored-by: Pierre Prinetti <pierreprinetti@redhat.com>
705f4d4
to
8ecc876
Compare
@mandre: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
/retest |
/bugzilla refresh |
@mandre: This pull request references Bugzilla bug 2039373, 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. 6 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. |
This is a cherry-pick of #1099 |
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
/approve
/label backport-risk-assesed
/remove-label backports/unvalidated-commits
/label backport/validated-commits
@soltysh: The label(s) 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mandre, soltysh 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 |
/label backport-risk-assessed |
Hey @xingxingxia @duanwei33, as we are not QE approvers in this repo, would someone from your team be able to add the cherry-pick-approved label in this PR? We already verified it successfully in 4.10. |
/label cherry-pick-approved |
thanks @gangwgr |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
@mandre: 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. |
@mandre: All pull requests linked via external trackers have merged: Bugzilla bug 2039373 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. |
The OpenStack secret is not guaranteed to be present at the time
kube-controller-manager is initialised.