WIP [release-4.14] OCPBUGS-59474: UPSTREAM: <carry>:

[vrutkovs]

Signed-off-by: cpanato [email protected]

[openshift-ci-robot]

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

The following commits are valid:

• dbcbd3d|UPSTREAM: 129011: skip TestCreateBlobDisk test: the upstream PR kubernetes/kubernetes#129011 has merged

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

• 27d9897|UPSTREAM: : disable some legacy cloud provider tests: does not specify an upstream backport in the commit message
• baedcce|UPSTREAM: : remove github.com/openshift-priv/golang-net replacement: 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]

@vrutkovs: This pull request references Jira Issue OCPBUGS-59474, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.14.z) matches configured target version for branch (4.14.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-59147 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-59147 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
• bug has dependents

Requesting review from QA contact:
/cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Signed-off-by: cpanato [email protected]

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: vrutkovs
Once this PR has been reviewed and has the lgtm label, please assign deads2k 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:

• DOWNSTREAM_OWNERS

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

[wangke19]

/retest-required

[wangke19]

/retest-required

[vrutkovs]

/retest-required

[openshift-ci]

@vrutkovs: 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-openstack-csi-manila	baedcce	link	false	/test e2e-openstack-csi-manila
ci/prow/e2e-openstack-csi-cinder	baedcce	link	false	/test e2e-openstack-csi-cinder
ci/prow/e2e-aws-ovn	baedcce	link	false	/test e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack	baedcce	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-csi	baedcce	link	false	/test e2e-aws-csi
ci/prow/e2e-agnostic-ovn-cmd	baedcce	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-metal-ipi	baedcce	link	false	/test e2e-metal-ipi
ci/prow/e2e-aws-disruptive	baedcce	link	false	/test e2e-aws-disruptive
ci/prow/e2e-aws-multitenant	baedcce	link	false	/test e2e-aws-multitenant
ci/prow/e2e-metal-ipi-ovn-ipv6	baedcce	link	false	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws	baedcce	link	false	/test e2e-aws
ci/prow/e2e-vsphere	baedcce	link	false	/test e2e-vsphere
ci/prow/k8s-e2e-aws	baedcce	link	false	/test k8s-e2e-aws
ci/prow/verify	baedcce	link	true	/test verify
ci/prow/unit	baedcce	link	true	/test unit
ci/prow/e2e-aws-ovn-serial	baedcce	link	true	/test e2e-aws-ovn-serial
ci/prow/integration	baedcce	link	true	/test integration

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.