Skip to content

OCPBUGS-77766: OCPBUGS-77765: NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile#168

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-163-to-release-4.19
Mar 4, 2026
Merged

OCPBUGS-77766: OCPBUGS-77765: NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile#168
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.19from
openshift-cherrypick-robot:cherry-pick-163-to-release-4.19

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #163

/assign lgarciaaco

Hermetic (Cachito/cachi2) builds override GOBIN, so go install places binaries in a different location than /go/bin, causing COPY --from=builder /go/bin/* /usr/bin/ to fail. Fix is to replace make install (which uses go install) with make build (which uses go build) and explicitly output binaries to /go/node-feature-discovery/bin, then copy from that deterministic path into /usr/bin/.
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 3, 2026

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@yevgeny-shnaidman
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, yevgeny-shnaidman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 Mar 4, 2026
@yevgeny-shnaidman
Copy link
Contributor

/lgtm

@yevgeny-shnaidman
Copy link
Contributor

/verified bypass

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

@yevgeny-shnaidman: The verified label has been added.

Details

In response to this:

/verified bypass

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.

@yevgeny-shnaidman
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 4, 2026
@lgarciaaco
Copy link
Contributor

/hold for testing

@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 Mar 4, 2026
@lgarciaaco
Copy link
Contributor

/unhold
test references openshift-eng/ocp-build-data#9221

@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 Mar 4, 2026
@lgarciaaco
Copy link
Contributor

/retitle NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile

@openshift-ci openshift-ci bot changed the title [release-4.19] NO-JIRA: fix hermetic build binary path issue in dockerfile NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile Mar 4, 2026
@lgarciaaco
Copy link
Contributor

/label jira/valid-bug

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 4, 2026

@lgarciaaco: The label(s) jira/valid-bug cannot be applied or removed, because you are not in one of the allowed teams and are not an allowed user. Must be a member of one of these teams: openshift-patch-managers, openshift-staff-engineers, openshift-release-oversight, openshift-sustaining-engineers

Details

In response to this:

/label jira/valid-bug

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.

@lgarciaaco
Copy link
Contributor

/jira cherrypick OCPBUGS-77763

@openshift-ci-robot
Copy link
Contributor

@lgarciaaco: Jira Issue OCPBUGS-77763 has been cloned as Jira Issue OCPBUGS-77765. Will retitle bug to link to clone.
/retitle OCPBUGS-77765: NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile

Details

In response to this:

/jira cherrypick OCPBUGS-77763

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 openshift-ci bot changed the title NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile OCPBUGS-77765: NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile Mar 4, 2026
@openshift-ci-robot openshift-ci-robot added 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 Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77765, which is invalid:

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.

Details

In response to this:

This is an automated cherry-pick of #163

/assign lgarciaaco

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.

@lgarciaaco
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@lgarciaaco: This pull request references Jira Issue OCPBUGS-77765, which is invalid:

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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

@lgarciaaco
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@lgarciaaco: This pull request references Jira Issue OCPBUGS-77765, which is invalid:

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.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

@lgarciaaco
Copy link
Contributor

/jira cherrypick OCPBUGS-77764

@openshift-ci-robot
Copy link
Contributor

@lgarciaaco: Jira Issue OCPBUGS-77764 has been cloned as Jira Issue OCPBUGS-77766. Will retitle bug to link to clone.
/retitle OCPBUGS-77766: OCPBUGS-77765: NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile

Details

In response to this:

/jira cherrypick OCPBUGS-77764

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 openshift-ci bot changed the title OCPBUGS-77765: NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile OCPBUGS-77766: OCPBUGS-77765: NO-JIRA: [release-4.19] fix hermetic build binary path issue in dockerfile Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-77766, which is invalid:

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

Details

In response to this:

This is an automated cherry-pick of #163

/assign lgarciaaco

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.

@lgarciaaco
Copy link
Contributor

/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. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Mar 4, 2026
@openshift-ci-robot
Copy link
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state New, 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-77764 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-77764 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ggordani@redhat.com), skipping review request.

Details

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit e21805d into openshift:release-4.19 Mar 4, 2026
5 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-77766: All pull requests linked via external trackers have merged:

All linked pull requests have the verified tag. Jira Issue OCPBUGS-77766 has been moved to the VERIFIED state.

Details

In response to this:

This is an automated cherry-pick of #163

/assign lgarciaaco

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants