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

Bug 2039373: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf #1107

Conversation

mandre
Copy link
Member

@mandre mandre commented Jan 11, 2022

The OpenStack secret is not guaranteed to be present at the time
kube-controller-manager is initialised.

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 11, 2022
@openshift-ci openshift-ci bot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Jan 11, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jan 11, 2022

@mandre: This pull request references Bugzilla bug 2039373, which is invalid:

  • expected dependent Bugzilla bug 2004542 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 2039373: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf

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.

@openshift-ci openshift-ci bot added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jan 11, 2022
@openshift-ci-robot
Copy link

@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 /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot requested review from soltysh and sttts January 11, 2022 16:00
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Jan 11, 2022
@mandre
Copy link
Member Author

mandre commented Jan 12, 2022

/retest

1 similar comment
@mandre
Copy link
Member Author

mandre commented Jan 13, 2022

/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)
Copy link
Member

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>
@openshift-ci-robot
Copy link

@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 /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@mandre
Copy link
Member Author

mandre commented Jan 24, 2022

/retest

@mandre
Copy link
Member Author

mandre commented Jan 27, 2022

/bugzilla refresh
/retest

@openshift-ci openshift-ci bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jan 27, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jan 27, 2022

@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
  • bug is open, matching expected state (open)
  • bug target release (4.9.z) matches configured target release for branch (4.9.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2004542 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2004542 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
  • bug has dependents

Requesting review from QA contact:
/cc @eurijon

In response to this:

/bugzilla refresh
/retest

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.

@openshift-ci openshift-ci bot requested a review from eurijon January 27, 2022 16:17
@pierreprinetti
Copy link
Member

This is a cherry-pick of #1099

Copy link
Member

@soltysh soltysh left a 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

@openshift-ci
Copy link

openshift-ci bot commented Jan 28, 2022

@soltysh: The label(s) /label backport-risk-assesed , /label backport/validated-commits cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, backport-risk-assessed, backports/unvalidated-commits, backports/validated-commits, bugzilla/invalid-bug, bugzilla/valid-bug, cherry-pick-approved

In response to this:

/lgtm
/approve
/label backport-risk-assesed
/remove-label backports/unvalidated-commits
/label backport/validated-commits

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.

@openshift-ci openshift-ci bot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 28, 2022
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 28, 2022
@openshift-ci
Copy link

openshift-ci bot commented Jan 28, 2022

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 28, 2022
@soltysh
Copy link
Member

soltysh commented Feb 1, 2022

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 1, 2022
@eurijon
Copy link

eurijon commented Feb 1, 2022

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.
Thanks
/cc @xingxingxia
/cc @duanwei33

@gangwgr
Copy link

gangwgr commented Feb 2, 2022

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 2, 2022
@eurijon
Copy link

eurijon commented Feb 2, 2022

/label cherry-pick-approved

thanks @gangwgr

@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link

openshift-ci bot commented Feb 2, 2022

@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.

@openshift-merge-robot openshift-merge-robot merged commit fc61f05 into openshift:release-4.9 Feb 2, 2022
@openshift-ci
Copy link

openshift-ci bot commented Feb 2, 2022

@mandre: All pull requests linked via external trackers have merged:

Bugzilla bug 2039373 has been moved to the MODIFIED state.

In response to this:

Bug 2039373: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf

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 mandre deleted the openstack-secret-race-49 branch February 3, 2022 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants