[release-4.18] OCPBUGS-59680, OCPBUGS-48710, OCPBUGS-61748: DownStream Merge Sync from 4.19 [07-14-2025]

[jluhrsen]

git merge -X theirs from 4.19 to 4.18

[openshift-ci-robot]

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

Details

In response to this:

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

• My code requires changes to the documentation
• if so, I have updated the documentation as required
• My code requires tests
• if so, I have added and/or updated the tests as required
• All the tests have passed in the CI

How to verify it

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.

[jluhrsen]

/payload 4.18 ci blocking
/payload 4.18 nightly blocking

[openshift-ci]

@jluhrsen: trigger 4 job(s) of type blocking for the ci release of OCP 4.18

• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-upgrade
• periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b3ce2150-60f5-11f0-9f0b-220c9d622c64-0

trigger 11 job(s) of type blocking for the nightly release of OCP 4.18

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-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
• periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-fips-payload-scan
• 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-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/b3ce2150-60f5-11f0-9f0b-220c9d622c64-1

[jluhrsen]

/retest
payloads look great, except this one failed. try again:
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm

[openshift-ci]

@jluhrsen: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/73d8eb20-6127-11f0-9208-bb96565c4671-0

[jluhrsen]

/retitle [release-4.18] OCPBUGS-48710: DownStream Merge Sync from 4.19 [07-14-2025]

[openshift-ci-robot]

@jluhrsen: This pull request references Jira Issue OCPBUGS-48710, which is invalid:

• expected dependent Jira Issue OCPBUGS-59350 to target a version in 4.19.0, 4.19.z, but it targets "4.20.0" instead

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.

Details

In response to this:

📑 Description

Fixes #

Additional Information for reviewers

✅ Checks

• My code requires changes to the documentation
• if so, I have updated the documentation as required
• My code requires tests
• if so, I have added and/or updated the tests as required
• All the tests have passed in the CI

How to verify it

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.

[jluhrsen]

/retest payloads look great, except this one failed. try again: /payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm

re-run looks good.

[jluhrsen]

/retest

[jluhrsen]

/jira refresh

[openshift-ci-robot]

@jluhrsen: This pull request references Jira Issue OCPBUGS-48710, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-59350 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59350 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

Details

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.

[zshi-redhat]

The commit to repin libreswan to 4.6-3.el9_0.3 looks good to me.

[martinkennelly]

@jluhrsen youre missing some commits from latest 4.19 - any reason? I really need it in 4.18

https://issues.redhat.com/browse/OCPBUGS-59371

[jluhrsen]

/retest

[jluhrsen]

@jluhrsen youre missing some commits from latest 4.19 - any reason? I really need it in 4.18

https://issues.redhat.com/browse/OCPBUGS-59371

this only includes what was in 4.19 at the time this PR was created. the most recent 4.19 sync landed after this was created and I think that's what you want.

but, updating these sync PRs resets the timeframe for getting them merged. This one is essentially ready to land, just need two more required jobs to pass and the right labels. As soon as that happens we can get the next 4.18 sync up.

[jluhrsen]

/retest

[martinkennelly]

/retest

unrelated - bgp CI is permafailing @jcaamano

[jcaamano]

/retest

unrelated - bgp CI is permafailing @jcaamano

yeah, can be safely ignored in 4.18

[openshift-ci-robot]

@jluhrsen: This pull request references Jira Issue OCPBUGS-59680, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-59350 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59350 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

This pull request references Jira Issue OCPBUGS-59371, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

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.

This pull request references Jira Issue OCPBUGS-48710, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-59350 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59350 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

This pull request references Jira Issue OCPBUGS-61748, which is invalid:

• expected dependent Jira Issue OCPBUGS-38735 to target a version in 4.19.0, 4.19.z, but it targets "4.20.0" instead

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.

Details

In response to this:

git merge -X theirs from 4.19 to 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 openshift-eng/jira-lifecycle-plugin repository.

[arkadeepsen]

/jira refresh

[openshift-ci-robot]

@arkadeepsen: This pull request references Jira Issue OCPBUGS-59680, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-59350 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59350 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

This pull request references Jira Issue OCPBUGS-59371, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead

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.

This pull request references Jira Issue OCPBUGS-48710, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-59350 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59350 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-60979 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-60979 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @huiran0826

Details

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.

[arkadeepsen]

Removing OCPBUGS-59371 as it's already closed.

/retitle [release-4.18] OCPBUGS-59680, OCPBUGS-48710, OCPBUGS-61748: DownStream Merge Sync from 4.19 [07-14-2025]

[openshift-ci-robot]

@jluhrsen: This pull request references Jira Issue OCPBUGS-59680, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-59350 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59350 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

This pull request references Jira Issue OCPBUGS-48710, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-59350 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-59350 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

This pull request references Jira Issue OCPBUGS-61748, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-60979 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-60979 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @huiran0826

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

Details

In response to this:

git merge -X theirs from 4.19 to 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 openshift-eng/jira-lifecycle-plugin repository.

[jluhrsen]

/test all

payloads were ugly, but I think we were in the middle of an aws outage when I tried them. just re-running the failed payloads for now:

/payload-job periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
/payload-job periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-upgrade-ovn-single-node
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview-serial
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6

[openshift-ci]

@jluhrsen: trigger 8 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-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
• 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/719cf850-9963-11f0-8c62-a6a25978e36e-0

[jluhrsen]

ci has not been good recently. I think we may be better now. trying it all again:

/retest all
/payload 4.18 ci blocking
/payload 4.18 nightly blocking

[openshift-ci]

@jluhrsen: trigger 4 job(s) of type blocking for the ci release of OCP 4.18

• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-upgrade
• periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0ca0ab10-9a51-11f0-9320-1b7aa3eeb0ad-0

trigger 10 job(s) of type blocking for the nightly release of OCP 4.18

• periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
• periodic-ci-openshift-release-master-ci-4.18-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
• 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-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/0ca0ab10-9a51-11f0-9320-1b7aa3eeb0ad-1

[openshift-ci]

@jluhrsen: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test 4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade

/test 4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

/test 4.18-upgrade-from-stable-4.17-images

/test e2e-aws-ovn

/test e2e-aws-ovn-edge-zones

/test e2e-aws-ovn-hypershift

/test e2e-aws-ovn-local-gateway

/test e2e-aws-ovn-local-to-shared-gateway-mode-migration

/test e2e-aws-ovn-serial

/test e2e-aws-ovn-shared-to-local-gateway-mode-migration

/test e2e-aws-ovn-upgrade

/test e2e-aws-ovn-upgrade-local-gateway

/test e2e-aws-ovn-windows

/test e2e-azure-ovn-upgrade

/test e2e-gcp-ovn

/test e2e-gcp-ovn-techpreview

/test e2e-metal-ipi-ovn-dualstack

/test e2e-metal-ipi-ovn-ipv6

/test gofmt

/test images

/test lint

/test okd-scos-images

/test qe-perfscale-payload-control-plane-6nodes

/test unit

The following commands are available to trigger optional jobs:

/test e2e-agent-compact-ipv4

/test e2e-aws-ovn-clusternetwork-cidr-expansion

/test e2e-aws-ovn-fdp-qe

/test e2e-aws-ovn-hypershift-conformance-techpreview

/test e2e-aws-ovn-hypershift-kubevirt

/test e2e-aws-ovn-single-node-techpreview

/test e2e-aws-ovn-techpreview

/test e2e-aws-ovn-virt

/test e2e-azure-ovn

/test e2e-azure-ovn-techpreview

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview

/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview

/test e2e-metal-ipi-ovn-dualstack-local-gateway

/test e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview

/test e2e-metal-ipi-ovn-dualstack-techpreview

/test e2e-metal-ipi-ovn-ipv4

/test e2e-metal-ipi-ovn-ipv6-techpreview

/test e2e-metal-ipi-ovn-techpreview

/test e2e-openstack-ovn

/test e2e-ovn-hybrid-step-registry

/test e2e-vsphere-ovn

/test e2e-vsphere-ovn-techpreview

/test e2e-vsphere-windows

/test okd-scos-e2e-aws-ovn

/test openshift-e2e-gcp-ovn-techpreview-upgrade

/test ovncore-perfscale-aws-ovn-large-cluster-density-v2

/test ovncore-perfscale-aws-ovn-large-node-density-cni

/test ovncore-perfscale-aws-ovn-xlarge-cluster-density-v2

/test ovncore-perfscale-aws-ovn-xlarge-node-density-cni

/test perfscale-aws-ovn-medium-cluster-density-v2

/test perfscale-aws-ovn-medium-node-density-cni

/test perfscale-aws-ovn-small-cluster-density-v2

/test perfscale-aws-ovn-small-node-density-cni

/test qe-perfscale-aws-ovn-medium-cluster-density

/test qe-perfscale-aws-ovn-medium-node-density-cni

/test qe-perfscale-aws-ovn-small-cluster-density

/test qe-perfscale-aws-ovn-small-node-density-cni

/test qe-perfscale-aws-ovn-small-udn-density-l2

/test qe-perfscale-aws-ovn-small-udn-density-l3

/test security

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-ovn-kubernetes-release-4.18-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade

pull-ci-openshift-ovn-kubernetes-release-4.18-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

pull-ci-openshift-ovn-kubernetes-release-4.18-4.18-upgrade-from-stable-4.17-images

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-clusternetwork-cidr-expansion

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-edge-zones

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-hypershift

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-hypershift-conformance-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-hypershift-kubevirt

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-local-gateway

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-local-to-shared-gateway-mode-migration

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-serial

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-shared-to-local-gateway-mode-migration

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-single-node-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-upgrade

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-upgrade-local-gateway

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-aws-ovn-windows

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-azure-ovn

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-azure-ovn-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-azure-ovn-upgrade

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-gcp-ovn

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-gcp-ovn-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-dualstack

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-dualstack-bgp-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-dualstack-local-gateway

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-dualstack-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-ipv4

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-ipv6

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-ipv6-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-metal-ipi-ovn-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-openstack-ovn

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-ovn-hybrid-step-registry

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-vsphere-ovn

pull-ci-openshift-ovn-kubernetes-release-4.18-e2e-vsphere-ovn-techpreview

pull-ci-openshift-ovn-kubernetes-release-4.18-gofmt

pull-ci-openshift-ovn-kubernetes-release-4.18-images

pull-ci-openshift-ovn-kubernetes-release-4.18-lint

pull-ci-openshift-ovn-kubernetes-release-4.18-okd-scos-e2e-aws-ovn

pull-ci-openshift-ovn-kubernetes-release-4.18-okd-scos-images

pull-ci-openshift-ovn-kubernetes-release-4.18-openshift-e2e-gcp-ovn-techpreview-upgrade

pull-ci-openshift-ovn-kubernetes-release-4.18-security

pull-ci-openshift-ovn-kubernetes-release-4.18-unit

Details

In response to this:

ci has not been good recently. I think we may be better now. trying it all again:

/retest all
/payload 4.18 ci blocking
/payload 4.18 nightly blocking

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.

[tssurya]

@jluhrsen : Are the payloads green here? I am willing to sign off and take the risk but we need to coordinate the dates such that we do this at the early end of a z stream release. Please start a thread in slack with me in team channel and let's talk there

@tssurya , I will get back to looking at this again. For some reason, when I try to make the partial PR that includes up to the commit that fixes the GCP bug (not sure if you remember that... it's been so long now) the clusters don't install. But this PR was fine way back when I was babysiting it.

Per your slack, I'll try to find the right timing on this, but first I think we should run all of CI and the payloads again, just to be safe:

/retest all /payload 4.18 ci blocking /payload 4.18 nightly blocking

Also why are the BGP lanes red in 4.18?

+ for network in "${!vrf_neighbors[@]}"
+ label='network: extranet'
+ '[' default = extranet ']'
+ subnet_v4_var=EXTRANET_NETWORK_SUBNET_V4
+ subnet_v6_var=EXTRANET_NETWORK_SUBNET_V6
+ ip=192.168.221.3
+ ip6=fd2e:6f44:5dd8:ca56::3
+ name=receive-filtered-extranet
+ vrf='vrf: extranet'
++ cat
+ network_selector='    - networkSelectionType: ClusterUserDefinedNetworks
      clusterUserDefinedNetworkSelector:
        networkSelector:
          matchLabels:
            network: extranet'
+ oc apply -f -
frrconfiguration.frrk8s.metallb.io/receive-filtered-extranet created
+ oc apply -f -
The RouteAdvertisements "extranet" is invalid: spec: Invalid value: "object": If 'PodNetwork' is selected for advertisement, a 'nodeSelector' can't be specified as it needs to be advertised on all nodes
+ rm -rf /tmp/tmp.KP3FAjcchR

we are missing backports of CNO into 4.18 this is totally red because of the API changes, cc @jcaamano ? or something is missing in origin backport not sure which of these is true.

I'm not sure how to track down what may be missing in CNO and/or origin if that's the case, but I can try to look for candidates. But, you are correct to note that they are permafailing on this PR.

LMK if this is a blocker on this PR and I will prioritize figuring it out.

Yea IMHO we should backport those API changes in CNO to stay safe, otherwise its hard to tell if we introduce some actual regression if the job continues to stay red, which it will.

[jluhrsen]

/test e2e-aws-ovn

[jluhrsen]

I think CI issues are ok now. and the payloads were great yesterday. just two to re-check, although I think one of them
is the gcp-ovn-rt-upgrade permafail. will re-run it anyway.

/retest
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
/payload-job periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

[openshift-ci]

@jluhrsen: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c22f66b0-9b0a-11f0-8169-3e5f6a9d042e-0

[kyrtapz]

/retest
/payload-job periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
/payload-job periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

[openshift-ci]

@kyrtapz: trigger 2 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1f2e79b0-9d1c-11f0-9122-bb2a661bbeac-0

[openshift-ci]

@jluhrsen: 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-metal-ipi-ovn-ipv4	e6c43bb	link	false	/test e2e-metal-ipi-ovn-ipv4
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview	e6c43bb	link	false	/test e2e-metal-ipi-ovn-dualstack-local-gateway-techpreview
ci/prow/4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade	e6c43bb	link	true	/test 4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview	e6c43bb	link	false	/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview
ci/prow/e2e-aws-ovn-hypershift-kubevirt	e6c43bb	link	false	/test e2e-aws-ovn-hypershift-kubevirt
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway	e6c43bb	link	false	/test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-aws-ovn-single-node-techpreview	e6c43bb	link	false	/test e2e-aws-ovn-single-node-techpreview
ci/prow/e2e-metal-ipi-ovn-ipv6-techpreview	e6c43bb	link	false	/test e2e-metal-ipi-ovn-ipv6-techpreview
ci/prow/lint	e6c43bb	link	true	/test lint
ci/prow/e2e-metal-ipi-ovn-techpreview	e6c43bb	link	false	/test e2e-metal-ipi-ovn-techpreview
ci/prow/okd-scos-e2e-aws-ovn	e6c43bb	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview	e6c43bb	link	false	/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-metal-ipi-ovn-dualstack-techpreview	e6c43bb	link	false	/test e2e-metal-ipi-ovn-dualstack-techpreview
ci/prow/security	e6c43bb	link	false	/test security
ci/prow/e2e-metal-ipi-ovn-dualstack	e6c43bb	link	true	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-metal-ipi-ovn-ipv6	e6c43bb	link	true	/test e2e-metal-ipi-ovn-ipv6

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.

[jluhrsen]

/payload-job periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
/retest

[openshift-ci]

@jluhrsen: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/7bb2d6d0-9d5e-11f0-80d3-dd8e9c41e3d0-0

[jluhrsen]

/close

[openshift-ci]

@jluhrsen: Closed this PR.

Details

In response to this:

/close

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-ci-robot]

@jluhrsen: This pull request references Jira Issue OCPBUGS-59680. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-48710. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

git merge -X theirs from 4.19 to 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 openshift-eng/jira-lifecycle-plugin repository.