OCPBUGS-16164: retire LatencySensitive featureset

[deads2k]

For multiple years this has been the equivalent of "". Make these consistent because in 4.13 the featureset handling added to the CVO didn't account for this and its unnecessary. It's more practical to migrate a few existing clusters than modify all producers.

[openshift-ci-robot]

@deads2k: This pull request references Jira Issue OCPBUGS-16164, which is invalid:

• expected Jira Issue OCPBUGS-16164 to depend on a bug targeting a version in 4.14.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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.

In response to this:

For multiple years this has been the equivalent of "". Make these consistent because in 4.13 the featureset handling added to the CVO didn't account for this and its unnecessary. It's more practical to migrate a few existing clusters than modify all producers.

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.

[deads2k]

/jira refresh

[openshift-ci-robot]

@deads2k: This pull request references Jira Issue OCPBUGS-16164, which is invalid:

• expected dependent Jira Issue OCPBUGS-15877 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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 kubernetes/test-infra repository.

[deads2k]

/jira refresh

[openshift-ci-robot]

@deads2k: This pull request references Jira Issue OCPBUGS-16164, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.13.z) matches configured target version for branch (4.13.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-15877 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-15877 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0
• bug has dependents

Requesting review from QA contact:
/cc @gangwgr

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

[deads2k]

/cherrypick release-4.12

[openshift-cherrypick-robot]

@deads2k: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.12

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.

[JoelSpeed]

Units appear to have failed on related tests but don't have logs captured, so not sure what the actual issue is

[openshift-ci]

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

[mfojtik]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, mfojtik

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [deads2k,mfojtik]

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

[openshift-ci-robot]

@deads2k: Jira Issue OCPBUGS-16164: All pull requests linked via external trackers have merged:

• openshift/cluster-config-operator#329
• openshift/cluster-config-operator#325
• openshift/origin#28050

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

In response to this:

For multiple years this has been the equivalent of "". Make these consistent because in 4.13 the featureset handling added to the CVO didn't account for this and its unnecessary. It's more practical to migrate a few existing clusters than modify all producers.

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.

[openshift-cherrypick-robot]

@deads2k: new pull request created: #336

In response to this:

/cherrypick release-4.12

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.