Skip to content

Comments

ARO-15695: test/e2e: run EnsureImageRegistryCapabilityDisabled on 4.18#5984

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
sjenning:ir-disable-e2e-418
Apr 7, 2025
Merged

ARO-15695: test/e2e: run EnsureImageRegistryCapabilityDisabled on 4.18#5984
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
sjenning:ir-disable-e2e-418

Conversation

@sjenning
Copy link
Contributor

@sjenning sjenning commented Apr 4, 2025

Hold for #5964 to merge.

Diff is large because I wrapped EnsureImageRegistryCapabilityDisabled in a t.Run()

cc @flavianmissi

Run /test e2e-aws-4-18 after dep merge and before moving out of draft.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 4, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 4, 2025

@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.

Details

In response to this:

Hold for #5964 to merge.

Diff is large because I wrapped EnsureImageRegistryCapabilityDisabled in a t.Run()

cc @flavianmissi

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.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2025

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

@openshift-ci openshift-ci bot added do-not-merge/needs-area area/testing Indicates the PR includes changes for e2e testing labels Apr 4, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 4, 2025

@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.

Details

In response to this:

Hold for #5964 to merge.

Diff is large because I wrapped EnsureImageRegistryCapabilityDisabled in a t.Run()

cc @flavianmissi

Run /test e2e-aws-4-18 after dep merge and before moving out of draft.

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 4, 2025

[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

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 4, 2025
@sjenning
Copy link
Contributor Author

sjenning commented Apr 4, 2025

/test e2e-aws-4-18

@sjenning
Copy link
Contributor Author

sjenning commented Apr 4, 2025

/test verify

@flavianmissi
Copy link
Member

looks like it didn't work? 🤔

Failed  === RUN   TestCreateClusterCustomConfig/Main
    util.go:218: Successfully waited for kubeconfig to be published for HostedCluster e2e-clusters-ctp8b/custom-config-v9txn in 0s
    util.go:235: Successfully waited for kubeconfig secret to have data in 0s
    util.go:281: Successfully waited for a successful connection to the guest API server in 0s
    util.go:2348: 
        Expected an error to have occurred.  Got:
            <nil>: nil
    --- FAIL: TestCreateClusterCustomConfig/Main (5.48s)

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

@sjenning sjenning marked this pull request as ready for review April 7, 2025 13:12
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 7, 2025
@openshift-ci openshift-ci bot requested review from hasueki and rtheis April 7, 2025 13:13
@sjenning
Copy link
Contributor Author

sjenning commented Apr 7, 2025

unrelated flakes

/override ci/prow/e2e-aks
/override ci/prow/e2e-aks-4-18

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 7, 2025

@sjenning: Overrode contexts on behalf of sjenning: ci/prow/e2e-aks, ci/prow/e2e-aks-4-18

Details

In response to this:

unrelated flakes

/override ci/prow/e2e-aks
/override ci/prow/e2e-aks-4-18

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.

@jparrill
Copy link
Contributor

jparrill commented Apr 7, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 7, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 7, 2025

@sjenning: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.

@sjenning
Copy link
Contributor Author

sjenning commented Apr 7, 2025

/override "Red Hat Konflux / hypershift-operator-main-on-pull-request"
/override "Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main"

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 7, 2025

@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

Details

In response to this:

/override "Red Hat Konflux / hypershift-operator-main-on-pull-request"
/override "Red Hat Konflux / hypershift-operator-main-enterprise-contract / hypershift-operator-main"

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 00016a3 into openshift:main Apr 7, 2025
14 of 16 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: hypershift
This PR has been included in build ose-hypershift-container-v4.20.0-202504080239.p0.g00016a3.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/testing Indicates the PR includes changes for e2e testing jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants