OCPBUGS-78110: [release-4.12] hermetic 4.12#744
OCPBUGS-78110: [release-4.12] hermetic 4.12#744openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.12from
Conversation
|
@fgallott: This pull request explicitly references no jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira cherrypick OCPBUGS-78109 |
|
@fgallott: Jira Issue OCPBUGS-78109 has been cloned as Jira Issue OCPBUGS-78110. Will retitle bug to link to clone. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@fgallott: This pull request references Jira Issue OCPBUGS-78110, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Review skipped — only excluded labels are configured. (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
/retest-required |
|
/retitle OCPBUGS-78110: [release-4.12] hermetic 4.12 |
|
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
done |
|
/assign @alebedev87 |
|
/retest-required |
|
@alebedev87 may you have a look at this one? the failing tests are not related to this change |
|
[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 DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/override ci/prow/e2e-aws-serial |
|
@jupierce: Overrode contexts on behalf of jupierce: ci/prow/e2e-aws-serial, ci/prow/e2e-upgrade DetailsIn 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-sigs/prow repository. |
|
@fgallott: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
186bf22
into
openshift:release-4.12
|
@fgallott: Jira Issue Verification Checks: Jira Issue OCPBUGS-78110 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. 🕓 DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Fix included in accepted release 4.12.0-0.nightly-2026-04-09-020127 |
same as #743