Skip to content

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

Open
fgallott wants to merge 1 commit intoopenshift:release-4.12from
fgallott:hermetic-4.12
Open

OCPBUGS-78110: [release-4.12] hermetic 4.12#744
fgallott wants to merge 1 commit intoopenshift:release-4.12from
fgallott:hermetic-4.12

Conversation

@fgallott
Copy link

@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
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
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign frobware for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@fgallott
Copy link
Author

/jira cherrypick OCPBUGS-78109

@openshift-ci-robot
Copy link
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
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

coderabbitai bot commented Mar 12, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: 174e9088-93e9-4e60-95f1-a19c05d55b57

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
📝 Coding Plan
  • Generate coding plan for human review comments

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.

Tip

CodeRabbit can use OpenGrep to find security vulnerabilities and bugs across 17+ programming languages.

OpenGrep is compatible with Semgrep configurations. Add an opengrep.yml or semgrep.yml configuration file to your project to enable OpenGrep analysis.

@fgallott
Copy link
Author

/retest-required

@alebedev87
Copy link
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
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
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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 17, 2026

@fgallott: 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-upgrade 1c3349c link true /test e2e-upgrade
ci/prow/e2e-aws-serial 1c3349c link true /test e2e-aws-serial

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.

@gcs278
Copy link
Contributor

gcs278 commented Mar 18, 2026

/assign @alebedev87

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants