Skip to content

Conversation

@tomasdavidorg
Copy link
Contributor

@tomasdavidorg tomasdavidorg commented Dec 4, 2025

@tomasdavidorg tomasdavidorg added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 4, 2025
@openshift-ci
Copy link

openshift-ci bot commented Dec 4, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 4, 2025

@tomasdavidorg: This pull request references OCPERT-239 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.

Details

In response to this:

This is just a draft.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 4, 2025
@openshift-ci
Copy link

openshift-ci bot commented Dec 4, 2025

[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 tomasdavidorg 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

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2025

@tomasdavidorg: This pull request references OCPERT-239 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.22.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/OCPERT-239

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.

@tomasdavidorg tomasdavidorg changed the title OCPERT-239: DRAFT migrate image consistency check OCPERT-239 Add migrated image consistency check Dec 18, 2025
@tomasdavidorg tomasdavidorg marked this pull request as ready for review December 18, 2025 07:28
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2025
@openshift-ci-robot
Copy link

@tomasdavidorg: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

https://issues.redhat.com/browse/OCPERT-239

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 removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Dec 18, 2025
Comment on lines 92 to 94
# FIXME: If multiple images are found, should we fail the check?
logger.error(f"Multiple images found in Red Hat catalog. Please check manually.")
return False
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to figure out how to recognize if the image is the correct one.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this is error case. even multiple items found, it means the image is already shipped.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So should I just pass if resp_data["total"] >= 1. I didn't find any example where there are more found items. I don't know how to recognize if one of the items is the correct one.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, we can add some trace logs from resp payload, like

curl -s "https://catalog.redhat.com/api/containers/v1/images?filter=image_id==sha256:45041834fa4fee1fed5415cee69f9723d50890a9685605f9b750635d8b1b01dd" | jq '.data[].repositories[]|.registry+"/"+.repository'
"registry.access.redhat.com/openshift4/ose-vsphere-problem-detector-rhel9"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Logging added.

@tomasdavidorg tomasdavidorg changed the title OCPERT-239 Add migrated image consistency check OCPERT-239: Add migrated image consistency check Dec 18, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 18, 2025

@tomasdavidorg: This pull request references OCPERT-239 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.22.0" version, but no target version was set.

Details

In response to this:

https://issues.redhat.com/browse/OCPERT-239

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.

for shipment_pullspec in self.shipment_image_pullspecs:
if self.all_image_metadata[payload_pullspec].has_same_name(self.all_image_metadata[shipment_pullspec]):
has_same_name = True
logger.info(f"Found an image with the same name but different identifier. Please check manually.")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a valid case? even name is same, but digest is not, they're not same image

Copy link
Contributor Author

@tomasdavidorg tomasdavidorg Dec 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. See the line 136-138.
The method _find_images_with_same_name is just for investigation purposes. If there is image with same name but different identificators, it will debug log detais.

It is taken from the previous implementation. https://gitlab.cee.redhat.com/aosqe/openshift-misc/-/blob/master/jenkins/v4-image-test/errata_test/errata_test.py?ref_type=heads#L97-L127

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

debugging purpose is ok.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Marking as resolved.

@tomasdavidorg
Copy link
Contributor Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Dec 19, 2025

@tomasdavidorg: 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/images 7e42d2a link true /test images
ci/prow/oar-check 7e42d2a link false /test oar-check

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.

@tomasdavidorg
Copy link
Contributor Author

https://github.com/openshift-eng/art-tools changed structure of project. Looking.

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

Labels

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.

3 participants