Skip to content

Conversation

@aguidirh
Copy link
Contributor

@aguidirh aguidirh commented Oct 9, 2025

Description

Having the flag --remove-signatures as false results to always mirroring the signature as default.

Github / Jira issue: CLID-459

Type of change

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update on openshift docs

How Has This Been Tested?

Run m2d/d2m or m2m.

Expected Outcome

The target registry should have the signature of the container images mirrored (see one example below):

Fetching tags for repository: openshift/release-images
{
  "name": "openshift/release-images",
  "tags": [
    "4.15.58-x86_64",
    "sha256-427fc0b133cc2aa45a68c36b603403ab278c845c0232e1c59387c4abfff01b9a.sig"
  ]
}

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@aguidirh: This pull request references CLID-459 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

Description

Having the flag --remove-signatures as false results to always mirroring the signature as default.

Github / Jira issue: CLID-459

Type of change

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update on openshift docs

How Has This Been Tested?

Run m2d/d2m or m2m.

Expected Outcome

The target registry should have the signature of the container images mirrored (see one example below):

Fetching tags for repository: openshift/release-images
{
 "name": "openshift/release-images",
 "tags": [
   "4.15.58-x86_64",
   "sha256-427fc0b133cc2aa45a68c36b603403ab278c845c0232e1c59387c4abfff01b9a.sig"
 ]
}

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 a review from r4f4 October 9, 2025 18:56
@openshift-ci
Copy link

openshift-ci bot commented Oct 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aguidirh

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

The pull request process is described here

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 Oct 9, 2025
@aguidirh
Copy link
Contributor Author

aguidirh commented Oct 9, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

@aguidirh: This pull request references CLID-459 which is a valid jira issue.

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.

@aguidirh
Copy link
Contributor Author

aguidirh commented Oct 9, 2025

/cherry-pick release-4.20

@openshift-cherrypick-robot

@aguidirh: once the present PR merges, I will cherry-pick it on top of release-4.20 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.20

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.

@r4f4
Copy link
Contributor

r4f4 commented Oct 13, 2025

It seems that trying to copy the signatures is breaking both our e2e and the integration tests. Is oc-mirror supposed to fail if an image is not signed?

@aguidirh
Copy link
Contributor Author

It seems that trying to copy the signatures is breaking both our e2e and the integration tests. Is oc-mirror supposed to fail if an image is not signed?

The idea was to fail only for internal images provided by us that we can guarantee the signatures. I will have a look at the code to see if I need to improve this mechanism in someway. Moving it to WIP.

@aguidirh aguidirh changed the title CLID-459: changes the flag remove-signatures default to false WIP: CLID-459: changes the flag remove-signatures default to false Oct 14, 2025
@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 Oct 14, 2025
@mcapala
Copy link

mcapala commented Oct 28, 2025

Indeed was about to issue an support case about this. Expanding on what r4f4 said - mirroring shouldn't simply fail if image signature is missing.
Possible solutions that I can see:

  1. Report it as warning instead.
  2. Report it as warning unless the image is related to redhat-operator-index (then image is expected to be signed I guess).
  3. Flag to ignore missing signatures.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 9, 2025
@r4f4
Copy link
Contributor

r4f4 commented Nov 10, 2025

Fixes #1300

@aguidirh aguidirh linked an issue Nov 11, 2025 that may be closed by this pull request
Having the flag --remove-signatures as false results to always mirroring
the signature as default.

Signed-off-by: Alex Guidi <[email protected]>
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 12, 2025
@openshift-ci
Copy link

openshift-ci bot commented Nov 12, 2025

@aguidirh: 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 c219cbe link true /test e2e
ci/prow/integration 38ab66c link true /test integration

Full PR test history. Your PR dashboard.

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.

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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. 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.

Change default behavior for signed images

6 participants