Conversation
|
Skipping CI for Draft Pull Request. |
6181b03 to
5552a3f
Compare
|
/test ? |
|
/test integration-e2e-parallel |
|
/test stage-e2e-parallel |
|
/test integration-e2e-parallel |
|
/test e2e-parallel |
|
Status update 17-07-2026:
Action Items:
|
|
mvacula02 Just as a heads up, 6082 replicates the check done in CS, but doesn't remove it from CS. So that will likely need to happen for this to pass. |
06c6c0a to
dd100ee
Compare
|
/hold until https://gitlab.cee.redhat.com/service/aro-hcp-clusters-service/-/merge_requests/401 is merged |
4f15578 to
1372819
Compare
1372819 to
bdf64ac
Compare
|
/test e2e-parallel |
There was a problem hiding this comment.
🟡 Changes recommended
The new E2E test currently risks nil-pointer panics when dereferencing identity profile entries and should add explicit assertions to fail cleanly.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
Suppressed comments (1)
internal/validation/validate_cluster_comprehensive_test.go:784
- This test case now expects no validation errors, but the case name still says "duplicate managed identity…" which reads like a failure scenario. Rename the case to reflect that identity reuse is allowed to keep the test intent clear.
}(),
expectErrors: []utils.ExpectedError{},
- Files reviewed: 23/23 changed files
- Comments generated: 2
- Review effort level: Lite
| By("reusing the same managed identity for all control plane operators") | ||
| cpOps := clusterParams.UserAssignedIdentitiesProfile.ControlPlaneOperators | ||
| sharedMI := cpOps["cluster-api-azure"] | ||
| for name := range cpOps { | ||
| if name == "cluster-api-azure" { | ||
| continue | ||
| } | ||
| originalMI := *cpOps[name] | ||
| cpOps[name] = sharedMI | ||
| if originalMI != *sharedMI { | ||
| delete(clusterParams.Identity.UserAssignedIdentities, originalMI) | ||
| } | ||
| } |
| }(), | ||
| expectErrors: []utils.ExpectedError{ | ||
| {Message: "must be unique within the cluster", FieldPath: "customerProperties.platform.operatorsAuthentication.userAssignedIdentities.dataPlaneOperators"}, | ||
| }, | ||
| expectErrors: []utils.ExpectedError{}, |
|
/test e2e-parallel |
2 similar comments
|
/test e2e-parallel |
|
/test e2e-parallel |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mvacula02 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
follow-up for Azure#6082, adding new negative E2E test case reusing MIs within a cluster.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
a86f006 to
3f731a7
Compare
|
/test e2e-parallel |
2 similar comments
|
/test e2e-parallel |
|
/test e2e-parallel |
|
mvacula02: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
PR needs rebase. DetailsInstructions 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-sigs/prow repository. |
ARO-28671
What
adding a new positive E2E test case that reuses managed identities within a cluster. The test assigns the same managed identity resource ID to two different control plane operators (ingress and cluster-api-azure) and verifies that cluster creation completes successfully.
removing validation that prevents MI reuse within cluster.
Depends on https://gitlab.cee.redhat.com/service/aro-hcp-clusters-service/-/merge_requests/401
Why
MI reuse within a cluster is a valid scenario. This test demonstrates that a cluster provisions successfully when two operators share the same managed identity, providing justification to remove the validateManagedIdentitiesUniqueWithinCluster validation added in
#6082#6121Testing
The PR adds an E2E test for existing feature.
PR Checklist
If E2E tests are included:
demonstrate that the test is able to detect a defect/error and fail with
proper error message and logs which communicates nature of the problem.