Closed bryan-cox closed 3 weeks ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
@bryan-cox: This pull request references HOSTEDCP-1994 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target only the "4.18.0" version, but multiple target versions were set.
@bryan-cox: This pull request references HOSTEDCP-2019 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target only the "4.18.0" version, but multiple target versions were set.
/retest
/test e2e-azure-operator
Hi @bryan-cox, are you planning on addressing this comment? Relatedly, if your preference would be to change the entire auth path for Azure, will you be available in the future to aid investigation of potential bugs related to this change?
Additionally, what is the automated test plan for this change, if any?
worth mentioning that the e2e-*-operator
tests can be quite flaky and are also failing in a different way each run (sigh).
the e2e-hypershift
failures look unrelated to me.
/test e2e-aws-operator /test e2e-azure-operator
/test e2e-hypershift
@bryan-cox: This pull request references HOSTEDCP-2019 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target only the "4.18.0" version, but multiple target versions were set.
I tested this PR with the following PRs and was able to deploy an Azure Hosted Cluster from an AKS management cluster:
/retest
@bryan-cox: all tests passed!
Full PR test history. Your PR dashboard.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bryan-cox, flavianmissi
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/label docs-approved
/label px_approved
@sferich888: The label(s) /label px_approved
cannot be applied. These labels are supported: acknowledge-critical-fixes-only, 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, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved
. Is this label configured under labels -> additional_labels
or labels -> restricted_labels
in plugin.yaml
?
/label px-approved
/label qe-approved
@bryan-cox: This pull request references HOSTEDCP-2019 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target only the "4.18.0" version, but multiple target versions were set.
[ART PR BUILD NOTIFIER]
Distgit: ose-cluster-image-registry-operator This PR has been included in build ose-cluster-image-registry-operator-container-v4.18.0-202410251041.p0.g4c7e4ef.assembly.stream.el9. All builds following this will include this PR.
Use Client Certificate Authentication for ARO HCP deployments. HyperShift will pass the needed environment variables for this authentication method: ARO_HCP_MI_CLIENT_ID, ARO_HCP_TENANT_ID, and ARO_HCP_CLIENT_CERTIFICATE_PATH.