Skip to content

OCPBUGS-78110: [release-4.12] hermetic 4.12#744

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.12from
fgallott:hermetic-4.12
Apr 8, 2026
Merged

OCPBUGS-78110: [release-4.12] hermetic 4.12#744
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.12from
fgallott:hermetic-4.12

Conversation

@fgallott
Copy link
Copy Markdown

@fgallott fgallott commented Mar 2, 2026

same as #743

@fgallott fgallott changed the title hermetic 4.12 [release-4.12] NO-JIRA: hermetic 4.12 Mar 2, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 2, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: This pull request explicitly references no jira issue.

Details

In response to this:

same as #743

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 requested review from alebedev87 and frobware March 2, 2026 15:25
@fgallott
Copy link
Copy Markdown
Author

/jira cherrypick OCPBUGS-78109

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: Jira Issue OCPBUGS-78109 has been cloned as Jira Issue OCPBUGS-78110. Will retitle bug to link to clone.
/retitle OCPBUGS-78110: [release-4.12] NO-JIRA: hermetic 4.12

Details

In response to this:

/jira cherrypick OCPBUGS-78109

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 [release-4.12] NO-JIRA: hermetic 4.12 OCPBUGS-78110: [release-4.12] NO-JIRA: hermetic 4.12 Mar 10, 2026
@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Mar 10, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: This pull request references Jira Issue OCPBUGS-78110, which is invalid:

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

same as #743

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 12, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7b6b16ab-490a-44ed-aa54-f3c3d8554866

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@fgallott
Copy link
Copy Markdown
Author

/retest-required

@alebedev87
Copy link
Copy Markdown
Contributor

/retitle OCPBUGS-78110: [release-4.12] hermetic 4.12

@openshift-ci openshift-ci bot changed the title OCPBUGS-78110: [release-4.12] NO-JIRA: hermetic 4.12 OCPBUGS-78110: [release-4.12] hermetic 4.12 Mar 17, 2026
@alebedev87
Copy link
Copy Markdown
Contributor

Can you please 1) squash/fixup commits into a single one, 2) reference Jira bug in the commit message too, 3) explain more why the change is needed for hermetic build in the commit message too?

Hermetic builds require that all dependencies are vendored and that
the vendor directory is fully consistent with go.mod. The build was
failing with:

  Error: PackageRejected: The content of the vendor directory is not
  consistent with go.mod.

This was caused by a missing file (vendor/github.com/getsentry/
raven-go/Dockerfile.test) which was likely excluded by a .gitignore
rule matching "Dockerfile*". Running `go mod vendor` restores this
file, and it must be committed with `git add --force` to satisfy
the hermetic build's vendor consistency check.

Additionally, test certificates in validation_test.go and
plugin_test.go were regenerated because they had expired, which
caused unit test failures.

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@fgallott
Copy link
Copy Markdown
Author

Can you please 1) squash/fixup commits into a single one, 2) reference Jira bug in the commit message too, 3) explain more why the change is needed for hermetic build in the commit message too?

done

@gcs278
Copy link
Copy Markdown
Contributor

gcs278 commented Mar 18, 2026

/assign @alebedev87

@fgallott
Copy link
Copy Markdown
Author

/retest-required

@fgallott
Copy link
Copy Markdown
Author

@alebedev87 may you have a look at this one? the failing tests are not related to this change

@jupierce jupierce added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. verified Signifies that the PR passed pre-merge verification criteria and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 8, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

@jupierce jupierce added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 8, 2026
@jupierce
Copy link
Copy Markdown
Contributor

jupierce commented Apr 8, 2026

/override ci/prow/e2e-aws-serial
/override ci/prow/e2e-upgrade

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

@jupierce: Overrode contexts on behalf of jupierce: ci/prow/e2e-aws-serial, ci/prow/e2e-upgrade

Details

In response to this:

/override ci/prow/e2e-aws-serial
/override ci/prow/e2e-upgrade

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

@fgallott: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit 186bf22 into openshift:release-4.12 Apr 8, 2026
8 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: Jira Issue Verification Checks: Jira Issue OCPBUGS-78110
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-78110 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

same as #743

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.

@fgallott fgallott deleted the hermetic-4.12 branch April 8, 2026 14:32
@openshift-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.12.0-0.nightly-2026-04-09-020127

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

10 participants