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

[release-4.6] Bug 2059677: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf #1198

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1178

/assign mandre

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

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

openshift-ci bot commented Mar 1, 2022

@openshift-cherrypick-robot: Bugzilla bug 2054669 has been cloned as Bugzilla bug 2059677. Retitling PR to link against new bug.
/retitle [release-4.6] [release-4.7] Bug 2059677: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf

In response to this:

[release-4.6] [release-4.7] Bug 2054669: 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 changed the title [release-4.6] [release-4.7] Bug 2054669: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf [release-4.6] [release-4.7] Bug 2059677: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf Mar 1, 2022
@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 1, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 1, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2059677, which is invalid:

  • expected dependent Bugzilla bug 2054669 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED 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:

[release-4.6] [release-4.7] Bug 2059677: 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 requested review from deads2k and marun March 1, 2022 17:32
@openshift-ci openshift-ci bot added the vendor-update Touching vendor dir or related files label Mar 1, 2022
@mandre
Copy link
Member

mandre commented Mar 2, 2022

/retest

@mandre
Copy link
Member

mandre commented Mar 2, 2022

/retitle [release-4.6] Bug 2059677: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf

@openshift-ci openshift-ci bot changed the title [release-4.6] [release-4.7] Bug 2059677: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf [release-4.6] Bug 2059677: UPSTREAM: 89885: SQUASH: Retry fetching clouds.conf Mar 2, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 2, 2022

@openshift-cherrypick-robot: 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
Copy link
Member

mandre commented Mar 8, 2022

/bugzilla refresh

@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 Mar 8, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 8, 2022

@mandre: This pull request references Bugzilla bug 2059677, 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.6.z) matches configured target release for branch (4.6.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2054669 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2054669 targets the "4.7.z" release, which is one of the valid target releases: 4.7.0, 4.7.z
  • bug has dependents

Requesting review from QA contact:
/cc @eurijon

In response to this:

/bugzilla refresh

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 March 8, 2022 15:41
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-assessed
/remove-label backports/unvalidated-commits
/label backports/validated-commits

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. backports/validated-commits Indicates that all commits come to merged upstream PRs. and removed backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. labels Mar 8, 2022
@eurijon
Copy link

eurijon commented Mar 8, 2022

Hi @gangwgr, this is the last backport of the serie, would you mind adding the cherry-pick-approved in this one as well?
It's been successfully verified in 4.7.

Thanks a lot

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 8, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 8, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, 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 Mar 8, 2022
@gangwgr
Copy link

gangwgr commented Mar 9, 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 Mar 9, 2022
@openshift-merge-robot openshift-merge-robot merged commit d5ccddc into openshift:release-4.6 Mar 9, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 9, 2022

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Bugzilla bug 2059677 has been moved to the MODIFIED state.

In response to this:

[release-4.6] Bug 2059677: 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.

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. backports/validated-commits Indicates that all commits come to merged upstream PRs. 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