Skip to content

NO-JIRA: fix: disable sigstore image policy verification#54

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift-eng:mainfrom
fonta-rh:NO_JIRA_SIGSTORE_FIX
Mar 13, 2026
Merged

NO-JIRA: fix: disable sigstore image policy verification#54
openshift-merge-bot[bot] merged 2 commits intoopenshift-eng:mainfrom
fonta-rh:NO_JIRA_SIGSTORE_FIX

Conversation

@fonta-rh
Copy link
Contributor

@fonta-rh fonta-rh commented Mar 12, 2026

Summary

  • Add OPENSHIFT_INSTALL_EXPERIMENTAL_DISABLE_IMAGE_POLICY=true to config_arbiter_example.sh and config_fencing_example.sh for dev-scripts deployments
  • Set the same variable in the kcli deploy task environment to ensure it's available during kcli create cluster

Test plan

  • Deploy arbiter topology cluster using dev-scripts with updated config
  • Deploy fencing topology cluster using dev-scripts with updated config
  • Deploy cluster using kcli method and verify no sigstore verification failures

🤖 Generated with Claude Code

fonta-rh and others added 2 commits March 12, 2026 09:43
…mples

Add OPENSHIFT_INSTALL_EXPERIMENTAL_DISABLE_IMAGE_POLICY=true to both
config_arbiter_example.sh and config_fencing_example.sh to prevent
image signature verification failures during installation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Set OPENSHIFT_INSTALL_EXPERIMENTAL_DISABLE_IMAGE_POLICY=true in the
environment for the kcli cluster creation command to prevent image
signature verification failures during installation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@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 12, 2026
@openshift-ci-robot
Copy link

@fonta-rh: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

  • Add OPENSHIFT_INSTALL_EXPERIMENTAL_DISABLE_IMAGE_POLICY=true to config_arbiter_example.sh and config_fencing_example.sh for dev-scripts deployments
  • Set the same variable in the kcli deploy task environment to ensure it's available during kcli create cluster

Test plan

  • Deploy arbiter topology cluster using dev-scripts with updated config
  • Deploy fencing topology cluster using dev-scripts with updated config
  • Deploy cluster using kcli method and verify no sigstore verification failures

🤖 Generated with Claude Code

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 qJkee and slintes March 12, 2026 08:49
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 12, 2026
@fonta-rh fonta-rh marked this pull request as draft March 12, 2026 08:49
@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 Mar 12, 2026
@fonta-rh fonta-rh marked this pull request as ready for review March 13, 2026 08:23
@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 Mar 13, 2026
@openshift-ci openshift-ci bot requested a review from jaypoulz March 13, 2026 08:23
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fonta-rh, lucaconsalvi

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-merge-bot openshift-merge-bot bot merged commit a3351b0 into openshift-eng:main Mar 13, 2026
2 checks passed
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. 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.

3 participants