Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting #1407

Conversation

aravindhp
Copy link
Contributor

The openshift/kubernetes repo does not propagate all tags from upstream. Only the X.Y.0 tag is propagated. This causes the Windows kubelet and kube-proxy Z version to lag behind its Linux counterparts. The Linux build of kubelet and kube-proxy figures out the Z version at build time. To do something similar for Windows, we can leverage the hack/update_submodules.sh script which is always used to update the kubelet and kube-proxy submodules. To achieve this, the following changes are made:

  • Add kubelet and kube-proxy version variables to the Makefile along with make endpoints
  • Call these make endpoints in the Dockerfile
  • Update hack/update_submodules.sh to pull upstream tags and generate a commit that updates the Makefile version variables

Now the built binaries will have the correct version encoded in them.

(manually cherry picked from #1401)

The openshift/kubernetes repo does not propagate all tags from upstream.
Only the X.Y.0 tag is propagated. This causes the Windows kubelet and
kube-proxy Z version to lag behind its Linux counterparts. The Linux
build [0] of kubelet and kube-proxy figures out the Z version at build
time. To do something similar for Windows, we can leverage the
hack/update_submodules.sh script which is always used to update the
kubelet and kube-proxy submodules. To achieve this, the following
changes are made:
- Add kubelet and kube-proxy version variables to the Makefile along
  with make endpoints
- Call these make endpoints in the Dockerfile
- Update hack/update_submodules.sh to pull upstream tags and generate
  a commit that updates the Makefile version variables

Now the built binaries will have the correct version encoded in them.

[0] https://github.com/openshift/doozer/blob/a34e303682ca180e4f071f85cc4c34e6d333787e/doozerlib/metadata.py#L788

(manually cherry picked from commit 60c4b4b)
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2023

@aravindhp: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[build] Fix k8s version reporting

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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2023
@aravindhp
Copy link
Contributor Author

/approve cancel

@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2023
@aravindhp
Copy link
Contributor Author

/jira cherrypick OCPBUGS-6635

@openshift-ci-robot
Copy link

@aravindhp: Jira Issue OCPBUGS-6635 has been cloned as Jira Issue OCPBUGS-7336. Retitling PR to link against new bug.
/retitle OCPBUGS-7336: [build] Fix k8s version reporting

In response to this:

/jira cherrypick OCPBUGS-6635

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 openshift-ci bot changed the title [build] Fix k8s version reporting OCPBUGS-7336: [build] Fix k8s version reporting Feb 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2023

@aravindhp: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-7336: [build] Fix k8s version reporting

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 openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 10, 2023
@openshift-ci-robot
Copy link

@aravindhp: This pull request references Jira Issue OCPBUGS-7336, which is invalid:

  • expected dependent Jira Issue OCPBUGS-6635 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is MODIFIED 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:

The openshift/kubernetes repo does not propagate all tags from upstream. Only the X.Y.0 tag is propagated. This causes the Windows kubelet and kube-proxy Z version to lag behind its Linux counterparts. The Linux build of kubelet and kube-proxy figures out the Z version at build time. To do something similar for Windows, we can leverage the hack/update_submodules.sh script which is always used to update the kubelet and kube-proxy submodules. To achieve this, the following changes are made:

  • Add kubelet and kube-proxy version variables to the Makefile along with make endpoints
  • Call these make endpoints in the Dockerfile
  • Update hack/update_submodules.sh to pull upstream tags and generate a commit that updates the Makefile version variables

Now the built binaries will have the correct version encoded in them.

(manually cherry picked from #1401)

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.

@aravindhp
Copy link
Contributor Author

/retitle [release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting

@openshift-ci openshift-ci bot changed the title OCPBUGS-7336: [build] Fix k8s version reporting [release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting Feb 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2023

@aravindhp: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting

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.

@aravindhp
Copy link
Contributor Author

/retitle OCPBUGS-7336: [release-4.12][build] Fix k8s version reporting

@openshift-ci openshift-ci bot changed the title [release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting OCPBUGS-7336: [release-4.12][build] Fix k8s version reporting Feb 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2023

@aravindhp: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-7336: [release-4.12][build] Fix k8s version reporting

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.

@aravindhp
Copy link
Contributor Author

/retitle [release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting

@openshift-ci openshift-ci bot changed the title OCPBUGS-7336: [release-4.12][build] Fix k8s version reporting [release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting Feb 10, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2023

@aravindhp: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.12] OCPBUGS-7336: [build] Fix k8s version reporting

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.

@aravindhp
Copy link
Contributor Author

/test images
/test build
/test vsphere-e2e-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 10, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sebsoto

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 10, 2023
@mansikulkarni96
Copy link
Member

/lgtm

@aravindhp
Copy link
Contributor Author

/hold

In case want to order backport PRs for the release-4.12 branch.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 10, 2023
@mtnbikenc
Copy link
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 14, 2023
@openshift-ci-robot
Copy link

@mtnbikenc: This pull request references Jira Issue OCPBUGS-7336, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.12.z) matches configured target version for branch (4.12.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-6635 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
  • dependent Jira Issue OCPBUGS-6635 targets the "4.13.0" version, which is one of the valid target versions: 4.13.0
  • bug has dependents

Requesting review from QA contact:
/cc @rrasouli

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.

@openshift-ci openshift-ci bot requested a review from rrasouli February 14, 2023 15:40
@aravindhp aravindhp marked this pull request as ready for review February 16, 2023 18:41
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 16, 2023
Copy link
Contributor Author

@aravindhp aravindhp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 16, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD eb7fa56 and 2 for PR HEAD ce0404b in total

@aravindhp
Copy link
Contributor Author

/test platform-none-vsphere-e2e-operator

Failed in gather-extra. Hopefully it is a flake 🤞🏽

 INFO: gathering quay tcpdump packet headers if present
error: the server could not find the requested resource
  404 page not found
error: the server could not find the requested resource
  404 page not found
error: the server could not find the requested resource
  404 page not found
{"component":"entrypoint","error":"wrapped process failed: exit status 1","file":"k8s.io/test-infra/prow/entrypoint/run.go:79","func":"k8s.io/test-infra/prow/entrypoint.Options.Run","level":"error","msg":"Error executing test process","severity":"error","time":"2023-02-17T00:13:52Z"}
error: failed to execute wrapped command: exit status 1 
INFO[2023-02-17T00:14:00Z] Step platform-none-vsphere-e2e-operator-gather-extra failed after 40s. 

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c79081b and 1 for PR HEAD ce0404b in total

@mtnbikenc
Copy link
Member

gather-extra failures related to https://issues.redhat.com/browse/TRT-861

@mtnbikenc
Copy link
Member

/retest-required

@aravindhp
Copy link
Contributor Author

/retest-required
Seeing an infrequent failure:

INFO[2023-02-17T17:11:11Z] Running step aws-e2e-ccm-install-gather-core-dump. 
INFO[2023-02-17T17:45:51Z] pod pending timeout: container "place-entrypoint" has not started in 30m0s: 
* Container sidecar is not ready with reason PodInitializing
* Container test is not ready with reason PodInitializing
Found 13 events for Pod aws-e2e-ccm-install-gather-core-dump:
* 0x : Successfully assigned ci-op-mzkwrzkm/aws-e2e-ccm-install-gather-core-dump to ip-10-0-135-185.ec2.internal
* 1x multus: Add eth0 [10.128.237.67/23] from openshift-sdn
* 1x kubelet: Pulling image "registry.access.redhat.com/ubi8"
* 1x kubelet: Successfully pulled image "registry.access.redhat.com/ubi8" in 202.867596ms
* 1x kubelet: Created container ci-scheduling-dns-wait
* 1x kubelet: Started container ci-scheduling-dns-wait
* 10x kubelet: Container image "gcr.io/k8s-prow/entrypoint:v20230215-1f9eebbd96" already present on machine
* 8x kubelet: Error: context deadline exceeded
* 3x kubelet: Failed to inspect image "gcr.io/k8s-prow/entrypoint:v20230215-1f9eebbd96": rpc error: code = DeadlineExceeded desc = context deadline exceeded
* 3x kubelet: Error: ImageInspectError
* 1x kubelet: Error: kubelet may be retrying requests that are timing out in CRI-O due to system load. Currently at stage container storage creation: context deadline exceeded: error reserving ctr name k8s_place-entrypoint_aws-e2e-ccm-install-gather-core-dump_ci-op-mzkwrzkm_4459f50f-6320-41e2-a53b-8331badd9289_2 for id f3b89f430ce2196735ee0fddd282ee06b7efb38e40fbedf2b861b288522524c0: name is reserved 

@mtnbikenc
Copy link
Member

Tests passed on this commit before and failures are after tests.
/override aws-e2e-ccm-install

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 17, 2023

@mtnbikenc: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • aws-e2e-ccm-install

Only the following failed contexts/checkruns were expected:

  • ci/prow/aws-e2e-ccm-install
  • ci/prow/aws-e2e-operator
  • ci/prow/aws-e2e-upgrade
  • ci/prow/azure-e2e-operator
  • ci/prow/build
  • ci/prow/ci-index
  • ci/prow/gcp-e2e-operator
  • ci/prow/images
  • ci/prow/lint
  • ci/prow/platform-none-vsphere-e2e-operator
  • ci/prow/unit
  • ci/prow/vsphere-e2e-ccm-install
  • ci/prow/vsphere-e2e-operator
  • ci/prow/wicd-unit-vsphere
  • pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-ccm-install
  • pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-aws-e2e-upgrade
  • pull-ci-openshift-windows-machine-config-operator-master-azure-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-build
  • pull-ci-openshift-windows-machine-config-operator-master-ci-index
  • pull-ci-openshift-windows-machine-config-operator-master-gcp-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-images
  • pull-ci-openshift-windows-machine-config-operator-master-lint
  • pull-ci-openshift-windows-machine-config-operator-master-platform-none-vsphere-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-unit
  • pull-ci-openshift-windows-machine-config-operator-master-vsphere-e2e-ccm-install
  • pull-ci-openshift-windows-machine-config-operator-master-vsphere-e2e-operator
  • pull-ci-openshift-windows-machine-config-operator-master-wicd-unit-vsphere
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

Tests passed on this commit before and failures are after tests.
/override aws-e2e-ccm-install

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.

@aravindhp
Copy link
Contributor Author

/override ci/prow/aws-e2e-ccm-install

Test has passed before for the same commit

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 17, 2023

@aravindhp: Overrode contexts on behalf of aravindhp: ci/prow/aws-e2e-ccm-install

In response to this:

/override ci/prow/aws-e2e-ccm-install

Test has passed before for the same commit

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-merge-robot openshift-merge-robot merged commit 4209dde into openshift:release-4.12 Feb 17, 2023
@openshift-ci-robot
Copy link

@aravindhp: All pull requests linked via external trackers have merged:

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

In response to this:

The openshift/kubernetes repo does not propagate all tags from upstream. Only the X.Y.0 tag is propagated. This causes the Windows kubelet and kube-proxy Z version to lag behind its Linux counterparts. The Linux build of kubelet and kube-proxy figures out the Z version at build time. To do something similar for Windows, we can leverage the hack/update_submodules.sh script which is always used to update the kubelet and kube-proxy submodules. To achieve this, the following changes are made:

  • Add kubelet and kube-proxy version variables to the Makefile along with make endpoints
  • Call these make endpoints in the Dockerfile
  • Update hack/update_submodules.sh to pull upstream tags and generate a commit that updates the Makefile version variables

Now the built binaries will have the correct version encoded in them.

(manually cherry picked from #1401)

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

@aravindhp: new pull request created: #1420

In response to this:

/cherry-pick release-4.11

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants