Skip to content

Conversation

@everettraven
Copy link
Contributor

as all the skipped tests expect some level of internet access or a specific disconnected environment configuration.

…connected testing

as all the skipped tests expect some level of internet access or a
specific disconnected environment configuration.

Signed-off-by: everettraven <[email protected]>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 20, 2024
@openshift-ci-robot
Copy link

@everettraven: This pull request explicitly references no jira issue.

Details

In response to this:

as all the skipped tests expect some level of internet access or a specific disconnected environment configuration.

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.

@joelanford
Copy link
Member

We do expect OLMv1 to work in disconnected clusters. However it seems something is not quite configured correctly in the disconnected CI cluster. Either (or both):

  • There isn't an registry mapping that works for OLMv1 (likely need an ImageTagMirrorSet for registry.redhat.io)
  • The catalog images were not mirrored.

@everettraven can you open an OCPBUGS issue for this?

/lgtm
/approve

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 20, 2024
@everettraven
Copy link
Contributor Author

We do expect OLMv1 to work in disconnected clusters. However it seems something is not quite configured correctly in the disconnected CI cluster. Either (or both):

  • There isn't an registry mapping that works for OLMv1 (likely need an ImageTagMirrorSet for registry.redhat.io)
  • The catalog images were not mirrored.

@everettraven can you open an OCPBUGS issue for this?

/lgtm /approve

Created https://issues.redhat.com/browse/OCPBUGS-44810

@LalatenduMohanty
Copy link
Member

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Nov 20, 2024
@tmshort
Copy link
Contributor

tmshort commented Nov 20, 2024

You need to do a make update

Signed-off-by: everettraven <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 20, 2024
@tmshort
Copy link
Contributor

tmshort commented Nov 20, 2024

/lgtm

@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 20, 2024
@grokspawn
Copy link
Contributor

grokspawn commented Nov 20, 2024

/retitle OPRUN-3605: sig-olmv1: update all but one of the olmv1 tests to be skipped in disconnected testing

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 20, 2024
@openshift-ci openshift-ci bot changed the title NO-ISSUE: sig-olmv1: update all but one of the olmv1 tests to be skipped in disconnected testing OPRUN-3605: sig-olmv1: update all but one of the olmv1 tests to be skipped in disconnected testing Nov 20, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 20, 2024

@everettraven: This pull request references OPRUN-3605 which is a valid jira issue.

Details

In response to this:

as all the skipped tests expect some level of internet access or a specific disconnected environment configuration.

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.

@xueqzhan
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: everettraven, joelanford, tmshort, xueqzhan

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 Nov 20, 2024
@tmshort
Copy link
Contributor

tmshort commented Nov 20, 2024

/retest

@grokspawn
Copy link
Contributor

Note: surviving test is simply a CRD existence check, so no networking is required.

@everettraven
Copy link
Contributor Author

/retest

1 similar comment
@tmshort
Copy link
Contributor

tmshort commented Nov 20, 2024

/retest

@everettraven
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 36b577a and 2 for PR HEAD 47e8351 in total

@everettraven
Copy link
Contributor Author

/retest

2 similar comments
@tmshort
Copy link
Contributor

tmshort commented Nov 21, 2024

/retest

@grokspawn
Copy link
Contributor

/retest

@stbenjam
Copy link
Member

/skip

@stbenjam
Copy link
Member

/skip

1 similar comment
@stbenjam
Copy link
Member

/skip

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2024

@everettraven: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn-single-node-upgrade 47e8351 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 47e8351 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-agnostic-ovn-cmd 47e8351 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-openstack-ovn 47e8351 link false /test e2e-openstack-ovn

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.

@openshift-trt
Copy link

openshift-trt bot commented Nov 21, 2024

Job Failure Risk Analysis for sha: 47e8351

Job Name Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade Low
[sig-node] static pods should start after being created
This test has passed 67.19% of 64 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.
---
[sig-node] static pods should start after being created
This test has passed 67.19% of 64 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

@openshift-merge-bot openshift-merge-bot bot merged commit 203d2b1 into openshift:master Nov 21, 2024
28 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202411212037.p0.g203d2b1.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

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.

9 participants