Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #5248

/assign patrickdillon

Adds CA for self-signed certs to the cloud provider
config on Azure Stack Hub platform.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2021

@openshift-cherrypick-robot: Detected clone of Bugzilla bug 2010921 with correct target release. Retitling PR to link to clone:
/retitle [release-4.9] Bug 2012173: Azure Stack: add trust bundle to cloud config

Details

In response to this:

[release-4.9] Bug 2010921: Azure Stack: add trust bundle to cloud config

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.9] Bug 2010921: Azure Stack: add trust bundle to cloud config [release-4.9] Bug 2012173: Azure Stack: add trust bundle to cloud config Oct 20, 2021
@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 Oct 20, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2021

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

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

Details

In response to this:

[release-4.9] Bug 2012173: Azure Stack: add trust bundle to cloud config

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 Oct 20, 2021
@openshift-ci openshift-ci bot requested a review from jhixson74 October 20, 2021 14:50
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign patrickdillon after the PR has been reviewed.
You can assign the PR to them by writing /assign @patrickdillon in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details 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 requested a review from patrickdillon October 20, 2021 14:50
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 20, 2021

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-openstack-kuryr b1a06ec link false /test e2e-openstack-kuryr
ci/prow/e2e-aws b1a06ec link true /test e2e-aws
ci/prow/e2e-libvirt b1a06ec link false /test e2e-libvirt
ci/prow/e2e-crc b1a06ec link false /test e2e-crc
ci/prow/e2e-aws-workers-rhel7 b1a06ec link false /test e2e-aws-workers-rhel7
ci/prow/e2e-aws-upgrade b1a06ec link true /test e2e-aws-upgrade
ci/prow/e2e-metal-ipi-ovn-ipv6-required b1a06ec link true /test e2e-metal-ipi-ovn-ipv6-required

Full PR test history. Your PR dashboard.

Details

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.

@staebler
Copy link
Contributor

/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 Oct 22, 2021
@openshift-bot
Copy link
Contributor

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

@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 1, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 1, 2022

@openshift-bot: This pull request references Bugzilla bug 2012173, 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 2010921 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2010921 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (gpei@redhat.com), skipping review request.

Details

In response to this:

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

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.

@gpei
Copy link
Contributor

gpei commented Jan 3, 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 Jan 3, 2022
@patrickdillon
Copy link
Contributor

/hold
We are looking at a more unified solution and operators should use proxy workaround until then

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 4, 2022
@patrickdillon
Copy link
Contributor

/close
Proxy workaround until we design a more unified solution.

@openshift-ci openshift-ci bot closed this Jan 14, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 14, 2022

@patrickdillon: Closed this PR.

Details

In response to this:

/close
Proxy workaround until we design a more unified solution.

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
Copy link
Contributor

openshift-ci bot commented Jan 14, 2022

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2012173. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

[release-4.9] Bug 2012173: Azure Stack: add trust bundle to cloud config

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

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants