CNTRLPLANE-1042: Run EnsureNetworkPolicies on Azure - #6328
Conversation
|
Skipping CI for Draft Pull Request. |
|
/test e2e-aks |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| t.Run("EnsureNetworkPolicies", func(t *testing.T) { | ||
| if hostedCluster.Spec.Platform.Type != hyperv1.AWSPlatform { | ||
| if hostedCluster.Spec.Platform.Type != hyperv1.AWSPlatform && hostedCluster.Spec.Platform.Type != hyperv1.AzurePlatform { | ||
| t.Skipf("test only supported on AWS platform, saw %s", hostedCluster.Spec.Platform.Type) |
Test Resultse2e-aks
Failed TestsTotal failed tests: 17
... and 12 more failed tests |
2a9beb5 to
a2e28a1
Compare
|
/test e2e-aks |
a2e28a1 to
88deed6
Compare
| "cloud-controller-manager", | ||
| "olm-collect-profiles", | ||
| "aws-ebs-csi-driver-operator", | ||
| "azure-disk-csi-driver-operator", |
There was a problem hiding this comment.
Confirmed with Jan Safranek this needed access to the management KAS here.
|
/test e2e-aks |
|
@enxebre: This pull request references CNTRLPLANE-1042 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 epic to target the "4.20.0" version, but no target version was set. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-aks |
|
/test verify |
|
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. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
|
@enxebre: 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. |
|
Stale PRs are closed after 21d of inactivity. If this PR is still relevant, comment to refresh it or remove the stale label. If this PR is safe to close now please do so with /lifecycle stale |
|
Stale PRs rot after 14d of inactivity. Mark the PR as fresh by commenting If this PR is safe to close now please do so with /lifecycle rotten |
|
Now I have all the information needed. Let me compile the final report. Test Failure Analysis CompleteJob Information
Test Failure AnalysisErrorSummaryAll 7 CI jobs failed identically during Prow's pre-test git merge phase — no builds, tests, or scans ever executed. When Prow attempted to merge the PR head commit ( Root CauseThe PR branch Because the merge conflict occurs during Prow's initial git clone/merge step — before The Tide error ("Not mergeable") is a downstream consequence of this same merge conflict — Tide correctly identifies that the PR cannot be automatically merged. This is not a product bug, test flake, or infrastructure issue. It is purely a stale branch that needs rebasing. Recommendations
Evidence
|
|
Rotten PRs close after 7d of inactivity. Reopen the PR by commenting /close |
|
@openshift-ci[bot]: Closed this PR. DetailsIn response to this:
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-sigs/prow repository. |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)format, where issue_number might be a GitHub issue, or a Jira story:Fixes #
Checklist