OCPBUGS-39120: Sync the non-OKD assets from master to release-4.17

[metlos]

This brings the 4.17 branch up-to-date with master prior to 4.17 release.

[openshift-ci-robot]

@metlos: This pull request references Jira Issue OCPBUGS-39120, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-39120 to depend on a bug targeting a version in 4.18.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

This brings the 4.17 branch up-to-date with master prior to 4.17 release.

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.

[metlos]

/jira refresh

[openshift-ci-robot]

@metlos: This pull request references Jira Issue OCPBUGS-39120, 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.17.0) matches configured target version for branch (4.17.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-42346 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-42346 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
• bug has dependents

Requesting review from QA contact:
/cc @jitendar-singh

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.

[metlos]

/test e2e-aws

[metlos]

As reasoned in #574 (comment) I am going to override the image ecosystem test because the failures it exhibits are fixed in the PR openshift/origin#29126 which itself requires changes introduced in this PR.

The gordian knot needs to be cut.

[metlos]

/override ci/prow/e2e-aws-ovn-image-ecosystem

[openshift-ci]

@metlos: Overrode contexts on behalf of metlos: ci/prow/e2e-aws-ovn-image-ecosystem

Details

In response to this:

/override ci/prow/e2e-aws-ovn-image-ecosystem

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]

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

[openshift-ci]

@metlos: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

• e2e-aws-ovn-image-ecosystem

Only the following failed contexts/checkruns were expected:

• ci/prow/e2e-aws
• ci/prow/e2e-aws-operator
• ci/prow/e2e-aws-ovn-image-ecosystem
• ci/prow/e2e-aws-ovn-proxy
• ci/prow/e2e-aws-ovn-upgrade
• ci/prow/images
• ci/prow/unit
• ci/prow/verify
• pull-ci-openshift-cluster-samples-operator-master-e2e-aws
• pull-ci-openshift-cluster-samples-operator-master-e2e-aws-operator
• pull-ci-openshift-cluster-samples-operator-master-e2e-aws-ovn-image-ecosystem
• pull-ci-openshift-cluster-samples-operator-master-e2e-aws-ovn-proxy
• pull-ci-openshift-cluster-samples-operator-master-e2e-aws-ovn-upgrade
• pull-ci-openshift-cluster-samples-operator-master-images
• pull-ci-openshift-cluster-samples-operator-master-unit
• pull-ci-openshift-cluster-samples-operator-master-verify
• tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override e2e-aws-ovn-image-ecosystem

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.

[metlos]

/cherry-pick-approved
/backport-risk-assessed

[fbm3307]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fbm3307, metlos

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:

• OWNERS [fbm3307,metlos]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[fbm3307]

/label cherry-pick-approved
/label backport-risk-assessed

[openshift-ci-robot]

@metlos: Jira Issue OCPBUGS-39120: All pull requests linked via external trackers have merged:

• openshift/cluster-samples-operator#577

Jira Issue OCPBUGS-39120 has been moved to the MODIFIED state.

Details

In response to this:

This brings the 4.17 branch up-to-date with master prior to 4.17 release.

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-samples-operator
This PR has been included in build ose-cluster-samples-operator-container-v4.17.0-202409260907.p0.g3a44b4d.assembly.stream.el9.
All builds following this will include this PR.