blocked versions due to OCPBUGS-30256

[pepedocs]

blocked versions due to OCPBUGS-30256

Issue link: https://issues.redhat.com/browse/OCPBUGS-30256

[pepedocs]

/test e2e-latest-cincinnati

[openshift-ci]

@pepedocs: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

[LalatenduMohanty]

/hold Till we link the impact assessment card in the risk. Refer https://github.com/openshift/enhancements/tree/master/enhancements/update/update-blocker-lifecycle for more information.

[LalatenduMohanty]

We do not need any conditional risk for a cluster which has already updated to 4.13 , as the risk does not change between 4.13 to 4.14 or 4.14 to 4.15 if the cluster already on that version which has the regression.
So please remove the risk from 4.14.z, 4.15.z versions

[LalatenduMohanty]

/hold cancel

[hlipsig]

We do not need any conditional risk for a cluster which has already updated to 4.13 , as the risk does not change between 4.13 to 4.14 or 4.14 to 4.15 if the cluster already on that version which has the regression. So please remove the risk from 4.14.z, 4.14.z versions

Disagree. The issue that necessitates the edge occurs when a node reboots, as it would during upgrade. We want to minimize instances of this as SRE has to manually remediate each node.

[LalatenduMohanty]

Update this link to https://issues.redhat.com/browse/OPNET-479 in all the files included in this PR

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pepedocs
Once this PR has been reviewed and has the lgtm label, please ask for approval from lalatendumohanty. For more information see the Kubernetes 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

[LalatenduMohanty]

Disagree. The issue that necessitates the edge occurs when a node reboots, as it would during upgrade. We want to minimize instances of this as SRE has to manually remediate each node.

As per the remediation steps we need to delete .link files to fix the issue. So if a cluster has update to 4.13 and the files are deleted, will these files again get created when they update to 4.14.z?

[cblecker]

/close
in favour of #4903

[openshift-ci]

@cblecker: Closed this PR.

In response to this:

/close
in favour of #4903

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/test-infra repository.