OCPBUGS-15866: remove readiness check for cache exclusion

[JoelSpeed]

This readiness check is causing issues when adding and removing nodes from the cluster. See kubernetes-sigs/cloud-provider-azure#4230 for details.

Upstream have set a milestone to fix this for 1.28, but we need it in 1.27 and 1.26 so will merge here and create a backport for the in-tree provider for 1.26.

This will go directly to the 4.13 branch to solve the release-1.26 issue.
For 4.14 the Azure CCM will be the default choice and this in-tree code will not be executed, therefore no change required in master for this repo.

[openshift-ci-robot]

@JoelSpeed: This pull request references Jira Issue OCPBUGS-15866, which is invalid:

• expected dependent Jira Issue OCPBUGS-14762 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST 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 readiness check is causing issues when adding and removing nodes from the cluster. See kubernetes-sigs/cloud-provider-azure#4230 for details.

Upstream have set a milestone to fix this for 1.28, but we need it in 1.27 and 1.26 so will merge here and create a backport for the in-tree provider for 1.26.

This will go directly to the 4.13 branch to solve the release-1.26 issue.
For 4.14 the Azure CCM will be the default choice and this in-tree code will not be executed, therefore no change required in master for this repo.

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

@JoelSpeed: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73febd4|UPSTREAM: : remove readiness check for cache exclusion: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[JoelSpeed]

/payload-aggregate periodic-ci-openshift-release-master-ci-4.13-e2e-azure-ovn-upgrade 10

Running payload aggregation job to ensure disruption metrics look good for this change

[openshift-ci]

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

• periodic-ci-openshift-release-master-ci-4.13-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e66dfd20-1be6-11ee-817a-b995f8cf4a76-0

[bertinatto]

/test e2e-aws-csi

[JoelSpeed]

/retest

[JoelSpeed]

Verify failed, seemingly because of go modules, is this normal? My PR shouldn't have affected the go modules

[openshift-ci-robot]

@JoelSpeed: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73febd4|UPSTREAM: : remove readiness check for cache exclusion: does not specify an upstream backport in the commit message
• e30dd44|Update vendor: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@JoelSpeed: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 73febd4|UPSTREAM: : remove readiness check for cache exclusion: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[soltysh]

master PR is in openshift/cloud-provider-azure#77 so this is good as is for 4.13, overriding the valid-bug

[soltysh]

/lgtm
/approve
/label backport-risk-assessed

[soltysh]

/retest-required

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, soltysh

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:

• DOWNSTREAM_OWNERS [soltysh]

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

[JoelSpeed]

/retest

[soltysh]

typecheck failure is a known problem tracked in https://issues.redhat.com/browse/OCPBUGS-16176
/override ci/prow/verify

[openshift-ci]

@soltysh: Overrode contexts on behalf of soltysh: ci/prow/verify

In response to this:

typecheck failure is a known problem tracked in https://issues.redhat.com/browse/OCPBUGS-16176
/override ci/prow/verify

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.

[soltysh]

/test integration

[JoelSpeed]

/retest-required

[ShudiLi]

/label cherry-pick-approved
thanks

[openshift-ci]

@ShudiLi: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved
thanks

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.

[ShudiLi]

cancel /label cherry-pick-approved

[gangwgr]

/label cherry-pick-approved

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f245ced and 2 for PR HEAD 73febd4 in total

[openshift-ci]

@JoelSpeed: The following test 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/verify	73febd4	link	true	/test verify

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.

[openshift-ci-robot]

@JoelSpeed: Jira Issue OCPBUGS-15866: Some pull requests linked via external trackers have merged:

• openshift/kubernetes#1625

The following pull requests linked via external trackers have not merged:

• openshift/installer#7302 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

This readiness check is causing issues when adding and removing nodes from the cluster. See kubernetes-sigs/cloud-provider-azure#4230 for details.

Upstream have set a milestone to fix this for 1.28, but we need it in 1.27 and 1.26 so will merge here and create a backport for the in-tree provider for 1.26.

This will go directly to the 4.13 branch to solve the release-1.26 issue.
For 4.14 the Azure CCM will be the default choice and this in-tree code will not be executed, therefore no change required in master for this repo.

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.