[release-4.9] Bug 2021995: Read k8s version from hyperkube Dockerfile #1044

openshift-cherrypick-robot · 2021-11-10T14:21:26Z

This is an automated cherry-pick of #1038

/assign vrutkovs

openshift-ci-robot · 2021-11-10T14:21:34Z

@openshift-cherrypick-robot: 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:

f6434e9|UPSTREAM: : squash with the rest of tooling: does not specify an upstream backport in the commit message

openshift-ci · 2021-11-10T14:22:38Z

@openshift-cherrypick-robot: Bugzilla bug 2021936 has been cloned as Bugzilla bug 2021995. Retitling PR to link against new bug.
/retitle [release-4.9] Bug 2021995: Read k8s version from hyperkube Dockerfile

In response to this:

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 · 2021-11-10T14:23:44Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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.

vrutkovs · 2021-11-10T16:55:25Z

/retest

openshift-ci · 2021-11-10T19:08:22Z

@openshift-cherrypick-robot: 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	`f6434e9`	link	false	`/test e2e-openstack-csi-manila`
ci/prow/e2e-openstack-csi-cinder	`f6434e9`	link	false	`/test e2e-openstack-csi-cinder`

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.

soltysh

/lgtm
/approve
/label backports/validated-commits
/label backport-risk-assessed

soltysh · 2021-11-10T21:00:52Z

/remove-label /backports/unvalidated-commits

openshift-ci · 2021-11-10T21:00:53Z

@soltysh: The label(s) /remove-label /backports/unvalidated-commits cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, backport-risk-assessed, backports/unvalidated-commits, backports/validated-commits, bugzilla/invalid-bug, bugzilla/valid-bug, cherry-pick-approved

In response to this:

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 · 2021-11-10T21:01:11Z

/remove-label backports/unvalidated-commits

openshift-ci · 2021-11-10T21:04:59Z

[APPROVALNOTIFIER] This PR is APPROVED

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

openshift-bot · 2021-11-10T21:06:01Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-11-10T22:24:05Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-11-10T23:29:06Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-11-10T23:42:04Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2021-11-13T01:00:32Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-13T01:00:36Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-14T01:01:27Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-14T01:01:31Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-15T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-15T01:00:27Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-16T01:00:24Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-16T01:00:28Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-17T01:01:21Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-17T01:01:26Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-18T01:00:52Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-18T01:00:57Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-19T01:00:46Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-19T01:00:51Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-20T01:00:32Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-20T01:00:37Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-21T01:00:51Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-21T01:00:56Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-22T01:00:55Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-22T01:01:00Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2021997 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is NEW instead
expected dependent Bugzilla bug 2021997 to target a release in 4.10.0, but it targets "4.8.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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-bot · 2021-11-23T01:00:49Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2021-11-23T01:00:53Z

@openshift-bot: This pull request references Bugzilla bug 2021995, which is invalid:

expected dependent Bugzilla bug 2021936 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

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.

josefkarasek · 2021-11-23T08:09:50Z

/bugzilla refresh

openshift-ci · 2021-11-23T08:11:57Z

@josefkarasek: This pull request references Bugzilla bug 2021995, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.9.z) matches configured target release for branch (4.9.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2021936 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2021936 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
bug has dependents

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

In response to this:

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.

xingxingxia · 2021-11-23T08:28:44Z

/label cherry-pick-approved

openshift-ci · 2021-11-23T11:03:48Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

openshift/kubernetes#1044

Bugzilla bug 2021995 has been moved to the MODIFIED state.

In response to this:

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.

UPSTREAM: <carry>: squash with the rest of tooling

f6434e9

openshift-ci bot assigned vrutkovs Nov 10, 2021

openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Nov 10, 2021

openshift-cherrypick-robot mentioned this pull request Nov 10, 2021

Bug 2021936: Read k8s version from hyperkube Dockerfile #1038

Merged

openshift-ci bot changed the title ~~[release-4.9] Bug 2021936: Read k8s version from hyperkube Dockerfile~~ [release-4.9] Bug 2021995: Read k8s version from hyperkube Dockerfile Nov 10, 2021

openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Nov 10, 2021

openshift-ci bot requested review from deads2k and sttts November 10, 2021 14:25

vrutkovs mentioned this pull request Nov 10, 2021

[release-4.9] Update fedora-coreos-config to latest stable Nov 9 openshift/okd-machine-os#243

Merged

soltysh approved these changes Nov 10, 2021

View reviewed changes

openshift-ci bot assigned soltysh Nov 10, 2021

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 10, 2021

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 10, 2021

openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Nov 23, 2021

openshift-ci bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Nov 23, 2021

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Nov 23, 2021

openshift-merge-robot merged commit 4dd1b5a into openshift:release-4.9 Nov 23, 2021

[release-4.9] Bug 2021995: Read k8s version from hyperkube Dockerfile #1044

[release-4.9] Bug 2021995: Read k8s version from hyperkube Dockerfile #1044

Conversation

openshift-cherrypick-robot commented Nov 10, 2021

openshift-ci-robot commented Nov 10, 2021

openshift-ci bot commented Nov 10, 2021

openshift-ci bot commented Nov 10, 2021

vrutkovs commented Nov 10, 2021

openshift-ci bot commented Nov 10, 2021 • edited Loading

soltysh left a comment

Choose a reason for hiding this comment

soltysh commented Nov 10, 2021

openshift-ci bot commented Nov 10, 2021

soltysh commented Nov 10, 2021

openshift-ci bot commented Nov 10, 2021

openshift-bot commented Nov 10, 2021

openshift-bot commented Nov 10, 2021

openshift-bot commented Nov 10, 2021

openshift-bot commented Nov 10, 2021

openshift-bot commented Nov 13, 2021

openshift-ci bot commented Nov 13, 2021

openshift-bot commented Nov 14, 2021

openshift-ci bot commented Nov 14, 2021

openshift-bot commented Nov 15, 2021

openshift-ci bot commented Nov 15, 2021

openshift-bot commented Nov 16, 2021

openshift-ci bot commented Nov 16, 2021

openshift-bot commented Nov 17, 2021

openshift-ci bot commented Nov 17, 2021

openshift-bot commented Nov 18, 2021

openshift-ci bot commented Nov 18, 2021

openshift-bot commented Nov 19, 2021

openshift-ci bot commented Nov 19, 2021

openshift-bot commented Nov 20, 2021

openshift-ci bot commented Nov 20, 2021

openshift-bot commented Nov 21, 2021

openshift-ci bot commented Nov 21, 2021

openshift-bot commented Nov 22, 2021

openshift-ci bot commented Nov 22, 2021

openshift-bot commented Nov 23, 2021

openshift-ci bot commented Nov 23, 2021

josefkarasek commented Nov 23, 2021

openshift-ci bot commented Nov 23, 2021

xingxingxia commented Nov 23, 2021

openshift-ci bot commented Nov 23, 2021

openshift-ci bot commented Nov 10, 2021 •

edited

Loading