origin

origin copied to clipboard

To fix OCPBUGS-16342. Generated using hack/update-kube-vendor.sh c596e68c5c148565063c60a9e2731f7b7ab8a9ca.

release-4.7 was not updated from openshift/kubernetss for a long time, the diff is huge.

And I don't understand how k8s.io/kubernetes => github.com/openshift/kubernetes v1.21.0-alpha.0.0.20230719075753-c596e68c5c14 got there, it should be v1.20.15, not 1.21.alpha. Still, c596e68c5c14 is HEAD of o/k release-4.7.

@jsafrane: This pull request references Jira Issue OCPBUGS-16342, which is invalid:

• expected dependent Jira Issue OCPBUGS-10330 to target a version in 4.8.0, 4.8.z, but it targets "4.9.z" 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:

To fix OCPBUGS-16342. Generated using hack/update-kube-vendor.sh c596e68c5c148565063c60a9e2731f7b7ab8a9ca.

release-4.7 was not updated from openshift/kubernetss for a long time, the diff is huge.

And I don't understand how k8s.io/kubernetes => github.com/openshift/kubernetes v1.21.0-alpha.0.0.20230719075753-c596e68c5c14 got there, it should be v1.20.15, not 1.21.alpha. Still, c596e68c5c14 is HEAD of o/k release-4.7.

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.

/jira refresh

@jsafrane: This pull request references Jira Issue OCPBUGS-16342, which is invalid:

• expected dependent Jira Issue OCPBUGS-15995 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:

/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.

/retest

AWS volume resize tests succeeded \o/.

/retest-required

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, 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:

• ~~OWNERS~~ [soltysh]

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

/label cherry-pick-approved

/jira refresh

@sdodson: This pull request references Jira Issue OCPBUGS-16342, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

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

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

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.

/retest-required

Remaining retests: 0 against base HEAD 7706ed41ca790a298404e144e11ab7fcccc55c5b and 2 for PR HEAD adca10feb273c1e3c73ad7a82119a2d6c99a0010 in total

@jsafrane: 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-agnostic-cmd	adca10feb273c1e3c73ad7a82119a2d6c99a0010	link	true	/test e2e-agnostic-cmd
ci/prow/e2e-gcp-builds	adca10feb273c1e3c73ad7a82119a2d6c99a0010	link	true	/test e2e-gcp-builds

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.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

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

In response to this:

To fix OCPBUGS-16342. Generated using hack/update-kube-vendor.sh c596e68c5c148565063c60a9e2731f7b7ab8a9ca.

release-4.7 was not updated from openshift/kubernetss for a long time, the diff is huge.

And I don't understand how k8s.io/kubernetes => github.com/openshift/kubernetes v1.21.0-alpha.0.0.20230719075753-c596e68c5c14 got there, it should be v1.20.15, not 1.21.alpha. Still, c596e68c5c14 is HEAD of o/k release-4.7.

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.