[release-4.17] OCPBUGS-49363: Auto-recover from MC with invalid extension

[openshift-cherrypick-robot]

This is an automated cherry-pick of #4805

/assign openshift-cherrypick-robot

/cherrypick release-4.16

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-48829 has been cloned as Jira Issue OCPBUGS-49363. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-49363: Auto-recover from MC with invalid extension

In response to this:

This is an automated cherry-pick of #4805

/assign openshift-cherrypick-robot

/cherrypick release-4.16

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

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-49363, which is invalid:

• expected dependent Jira Issue OCPBUGS-48829 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

In response to this:

This is an automated cherry-pick of #4805

/assign openshift-cherrypick-robot

/cherrypick release-4.16

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign cheesesashimi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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-cherrypick-robot: 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-hypershift	b25a0f1	link	true	/test e2e-hypershift
ci/prow/e2e-gcp-op	b25a0f1	link	true	/test e2e-gcp-op
ci/prow/e2e-vsphere-ovn-upi	b25a0f1	link	false	/test e2e-vsphere-ovn-upi
ci/prow/e2e-gcp-op-techpreview	b25a0f1	link	false	/test e2e-gcp-op-techpreview
ci/prow/verify	b25a0f1	link	true	/test verify
ci/prow/e2e-aws-ovn	b25a0f1	link	true	/test e2e-aws-ovn
ci/prow/e2e-vsphere-ovn-zones	b25a0f1	link	false	/test e2e-vsphere-ovn-zones
ci/prow/e2e-aws-ovn-upgrade	b25a0f1	link	true	/test e2e-aws-ovn-upgrade
ci/prow/bootstrap-unit	b25a0f1	link	false	/test bootstrap-unit
ci/prow/images	b25a0f1	link	true	/test images
ci/prow/e2e-vsphere-ovn-upi-zones	b25a0f1	link	false	/test e2e-vsphere-ovn-upi-zones
ci/prow/e2e-gcp-op-single-node	b25a0f1	link	true	/test e2e-gcp-op-single-node
ci/prow/unit	b25a0f1	link	true	/test unit
ci/prow/e2e-aws-ovn-upgrade-out-of-change	b25a0f1	link	false	/test e2e-aws-ovn-upgrade-out-of-change
ci/prow/e2e-azure-ovn-upgrade-out-of-change	b25a0f1	link	false	/test e2e-azure-ovn-upgrade-out-of-change

Full PR test history. Your PR dashboard.

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.

[isabella-janssen]

/jira refresh

[openshift-ci-robot]

@isabella-janssen: This pull request references Jira Issue OCPBUGS-49363, which is invalid:

• expected dependent Jira Issue OCPBUGS-48829 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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.

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.

[isabella-janssen]

/jira refresh

[openshift-ci-robot]

@isabella-janssen: This pull request references Jira Issue OCPBUGS-49363, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.z) matches configured target version for branch (4.17.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-48829 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-48829 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 @sergiordlr

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.

[djoshy]

I think there's a build issue, maybe 4.17 is missing the function used to validate the extensions?

[isabella-janssen]

I think there's a build issue, maybe 4.17 is missing the function used to validate the extensions?

Thanks for noticing @djoshy--I'll pull it down to see what's going on

[isabella-janssen]

/close

Closing in favor of #4824

[openshift-ci]

@isabella-janssen: Closed this PR.

In response to this:

/close

Closing in favor of #4824

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]

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

In response to this:

This is an automated cherry-pick of #4805

/assign openshift-cherrypick-robot

/cherrypick release-4.16

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.