OCPBUGS-39315: remove ingress operator exclusion

[kannon92]

trafficstars

cc @candita

[openshift-ci-robot]

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

In response to this:

cc @candita

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.

[candita]

@kannon92 I investigated the logs here and I don't see any issues for cluster-ingress. Do you?

[kannon92]

/payload 4.18 informing

[openshift-ci[bot]]

@kannon92: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[kannon92]

@kannon92 I investigated the logs here and I don't see any issues for cluster-ingress. Do you?

@kannon92 I investigated the logs here and I don't see any issues for cluster-ingress. Do you?

yea, i think we gotta search for a job that actually triggers this. Not sure if it is covered in the default presubmits.

[kannon92]

/payload 4.18 nightly informing

[openshift-ci[bot]]

@kannon92: trigger 72 job(s) of type informing for the nightly release of OCP 4.18

• periodic-ci-openshift-release-master-nightly-4.18-e2e-agent-compact-ipv4-conformance
• periodic-ci-openshift-release-master-nightly-4.18-e2e-agent-ha-dualstack-conformance
• periodic-ci-openshift-release-master-nightly-4.18-e2e-agent-single-node-ipv6
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-upgrade-ovn-single-node
• periodic-ci-openshift-release-master-nightly-4.18-console-aws
• periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.18-periodics-e2e-aws
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-csi
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-cgroupsv2
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-fips
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-csi
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-serial
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-techpreview
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-upgrade-ovn-single-node
• periodic-ci-openshift-release-master-nightly-4.18-upgrade-from-stable-4.17-e2e-aws-upgrade-ovn-single-node
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade-out-of-change
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-upi
• periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.18-periodics-e2e-azure
• periodic-ci-openshift-release-master-nightly-4.18-e2e-azure-csi
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade-out-of-change
• periodic-ci-openshift-release-master-cnv-nightly-4.18-e2e-azure-deploy-cnv
• periodic-ci-openshift-release-master-cnv-nightly-4.18-e2e-azure-upgrade-cnv
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-driver-toolkit
• periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.18-periodics-e2e-gcp
• periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn
• periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-csi
• periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-rt
• periodic-ci-openshift-release-master-nightly-4.18-e2e-gcp-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-dualstack
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-dualstack-techpreview
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6-techpreview
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-serial-ipv4
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-serial-virtualmedia
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-techpreview
• periodic-ci-openshift-release-master-nightly-4.18-upgrade-from-stable-4.17-e2e-metal-ipi-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-serial-ovn-ipv6
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-serial-ovn-dualstack
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-upgrade-ovn-ipv6
• periodic-ci-openshift-release-master-nightly-4.18-upgrade-from-stable-4.17-e2e-metal-ipi-upgrade-ovn-ipv6
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ovn-assisted
• periodic-ci-openshift-release-master-nightly-4.18-metal-ovn-single-node-recert-cluster-rename
• periodic-ci-openshift-osde2e-main-nightly-4.18-osd-aws
• periodic-ci-openshift-osde2e-main-nightly-4.18-conformance-osd-aws
• periodic-ci-openshift-osde2e-main-nightly-4.18-osd-gcp
• periodic-ci-openshift-osde2e-main-nightly-4.18-conformance-osd-gcp
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-proxy
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ovn-single-node-live-iso
• periodic-ci-openshift-osde2e-main-nightly-4.18-rosa-classic-sts
• periodic-ci-openshift-release-master-nightly-4.18-e2e-telco5g
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-csi
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-serial
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-techpreview
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-vsphere-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-upi
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-ovn-upi-serial
• periodic-ci-openshift-release-master-nightly-4.18-e2e-vsphere-static-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/708127f0-7111-11ef-8a2a-3bc56ba8cbf2-0

[kannon92]

/payload 4.18 nightly blocking

[openshift-ci[bot]]

@kannon92: trigger 9 job(s) of type blocking for the nightly release of OCP 4.18

• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-fips-payload-scan
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm
• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/538d1480-7128-11ef-8c0b-e7390bea2fd0-0

[kannon92]

If we can't find any failures, I'm happy to merge this PR. And we can monitor the CI to see if this failure occurs again.

[candita]

@kannon92 let me know if there's anything else I can do. It's not clear to me how to find issues in the payload tests you ran.

[Miciah]

@kannon92, I don't see any restarts for cluster-ingress-operator in CI. @openshift/openshift-team-network-edge is fine with the change. Do you want to remove the "wip" from the commit message and link this to OCPBUGS-39315?

[openshift-ci-robot]

@kannon92: This pull request references Jira Issue OCPBUGS-39315, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

cc @candita

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.

[kannon92]

/jira refresh

[openshift-ci-robot]

@kannon92: This pull request references Jira Issue OCPBUGS-39315, which is invalid:

• expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[kannon92]

/jira refresh

[openshift-ci-robot]

@kannon92: This pull request references Jira Issue OCPBUGS-39315, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact: /cc @anuragthehatter

In response to this:

/jira refresh

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.

[kannon92]

@kannon92, I don't see any restarts for cluster-ingress-operator in CI. @openshift/openshift-team-network-edge is fine with the change. Do you want to remove the "wip" from the commit message and link this to OCPBUGS-39315?

done!

[kannon92]

/hold

A related PR was reverted so going to hold on this one for now.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: f409bd2da5fd8b7b8242968a46a1102bc05ea86b

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade	High [sig-api-machinery] disruption/kube-api connection/reused should be available throughout the test This test has passed 99.94% of 6408 runs on release 4.18 [Overall] in the last week. --- [sig-api-machinery] disruption/kube-api connection/new should be available throughout the test This test has passed 99.75% of 6408 runs on release 4.18 [Overall] in the last week.

[Miciah]

/hold

A related PR was reverted so going to hold on this one for now.

Gentle nudge! @kannon92, is there any update on the related PR? Are we going to proceed with this PR?

[kannon92]

PR was rebased and updated.

[openshift-trt[bot]]

Job Failure Risk Analysis for sha: 705916d020f2c636b2c9097409b69567f064c787

Job Name

Failure Risk

pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade

Medium [sig-architecture] platform pods in ns/openshift-e2e-loki should not exit an excessive amount of times This test has passed 93.38% of 151 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. Open Bugs Loki on SNO throws excessive restarts while waiting for DNS deployment

[kannon92]

/hold cancel

[kannon92]

/retest

[openshift-trt[bot]]

Job Failure Risk Analysis for sha: 37598aeaad3c9fe2595c7fd6f7354ecd24b4a596

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (103) are below the historical average (2586): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[kannon92]

@dgoodwin @deads2k could you help with this PR?

[dgoodwin]

/lgtm

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD b331d386c1ced3c02b4825522444a2b577ca6e7b and 2 for PR HEAD 37598aeaad3c9fe2595c7fd6f7354ecd24b4a596 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 0c564f067157f734d95737f27b5e8173d801134c and 1 for PR HEAD 37598aeaad3c9fe2595c7fd6f7354ecd24b4a596 in total