ARO-15695: test/e2e: run EnsureImageRegistryCapabilityDisabled on 4.18#5984
Conversation
|
@sjenning: This pull request references ARO-15695 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 task to target the "4.19.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. |
|
Skipping CI for Draft Pull Request. |
|
@sjenning: This pull request references ARO-15695 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 task to target the "4.19.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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sjenning 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 |
|
/test e2e-aws-4-18 |
|
/test verify |
|
looks like it didn't work? 🤔 The line in question (2348) attempts to get the image-registry cluster operator and expects an error, which didn't happen. The registry operator pod is also up and running: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_hypershift/5984/pull-ci-openshift-hypershift-main-e2e-aws-4-18/1908298529105776640/artifacts/e2e-aws-4-18/hypershift-aws-run-e2e-external/artifacts/TestCreateClusterCustomConfig/namespaces/e2e-clusters-ctp8b-custom-config-v9txn/core/pods/ (assuming I'm looking at the right place). Is it possible that even though all the relevant code was merged, the feature still does not work in 4.18? how? 🤔 I'll run a retest in case somehow the code was not in the payload. /retest |
|
unrelated flakes /override ci/prow/e2e-aks |
|
@sjenning: Overrode contexts on behalf of sjenning: ci/prow/e2e-aks, ci/prow/e2e-aks-4-18 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. |
|
/lgtm |
|
@sjenning: all tests passed! 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. |
|
/override "Red Hat Konflux / hypershift-operator-main-on-pull-request" |
|
@sjenning: Overrode contexts on behalf of sjenning: Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main, Red Hat Konflux / hypershift-operator-main-on-pull-request 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. |
00016a3
into
openshift:main
|
[ART PR BUILD NOTIFIER] Distgit: hypershift |
Hold for #5964 to merge.
Diff is large because I wrapped
EnsureImageRegistryCapabilityDisabledin at.Run()cc @flavianmissi
Run
/test e2e-aws-4-18after dep merge and before moving out of draft.