Skip to content

OPRUN-3890,OPRUN-3983: Upgrade CatalogSources to use images from OCP release 4.20 #393

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

OPRUN-3890,OPRUN-3983: Upgrade CatalogSources to use images from OCP release 4.20 #393

wants to merge 1 commit into from
+13 −13

Conversation

camilamacedo86
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot requested review from bentito and dtfranz July 1, 2025 23:14
@camilamacedo86 camilamacedo86 changed the title UPSTREAM: <carry>: Upgrade CatalogSources to use images from OCP release 4.20 Upgrade CatalogSources to use images from OCP release 4.20 Jul 1, 2025
@camilamacedo86 camilamacedo86 changed the title Upgrade CatalogSources to use images from OCP release 4.20 (HOLD) Upgrade CatalogSources to use images from OCP release 4.20 Jul 1, 2025
@camilamacedo86 camilamacedo86 force-pushed the add-update-images-catalogs branch from 032944c to 79c6803 Compare July 3, 2025 11:19
@camilamacedo86 camilamacedo86 changed the title (HOLD) Upgrade CatalogSources to use images from OCP release 4.20 OPRUN-3983: Upgrade CatalogSources to use images from OCP release 4.20 Jul 3, 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 Jul 3, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 3, 2025 •
edited by openshift-ci bot
Loading

@camilamacedo86: This pull request references OPRUN-3983 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.20.0" version, but no target version was set.

In 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.

@camilamacedo86 camilamacedo86 force-pushed the add-update-images-catalogs branch from 79c6803 to 5670f6f Compare July 3, 2025 11:53
@camilamacedo86
Copy link
Contributor Author

/retest-required

@dtfranz
Copy link
Contributor

dtfranz commented Jul 16, 2025

It looks like (at least) the community-operator-index for 4.20 isn't available yet? From catalogd logs in must-gather:
"Reconciler error" err="source catalog content: error creating image source: reading manifest v4.20 in registry.redhat.io/redhat/community-operator-index: manifest unknown" controller="catalogd-clustercatalog-controller"

@camilamacedo86
Copy link
Contributor Author

It looks like (at least) the community-operator-index for 4.20 isn't available yet?

No, it is not :-(
We are waiting for that.

@camilamacedo86
Copy link
Contributor Author

/retest-required

1 similar comment
@camilamacedo86
Copy link
Contributor Author

/retest-required

@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@camilamacedo86
Copy link
Contributor Author

/retest-required

1 similar comment
@camilamacedo86
Copy link
Contributor Author

/retest-required

@camilamacedo86 camilamacedo86 changed the title OPRUN-3983: Upgrade CatalogSources to use images from OCP release 4.20 OPRUN-3890OPRUN-3983: Upgrade CatalogSources to use images from OCP release 4.20 Jul 29, 2025
@camilamacedo86 camilamacedo86 changed the title OPRUN-3890OPRUN-3983: Upgrade CatalogSources to use images from OCP release 4.20 OPRUN-3890,OPRUN-3983: Upgrade CatalogSources to use images from OCP release 4.20 Jul 29, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 29, 2025 •
edited by openshift-ci bot
Loading

@camilamacedo86: This pull request references OPRUN-3890 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.20.0" version, but no target version was set.

This pull request references OPRUN-3983 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.20.0" version, but no target version was set.

In 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.

@camilamacedo86 camilamacedo86 reopened this Aug 1, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 1, 2025 •
edited by openshift-ci bot
Loading

@camilamacedo86: This pull request references OPRUN-3890 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.20.0" version, but no target version was set.

This pull request references OPRUN-3983 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.20.0" version, but no target version was set.

In 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.

@camilamacedo86
Copy link
Contributor Author

/retest-required

1 similar comment
@camilamacedo86
Copy link
Contributor Author

/retest-required

@camilamacedo86 camilamacedo86 force-pushed the add-update-images-catalogs branch from 5670f6f to 149c2bd Compare August 1, 2025 17:15
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 1, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 1, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, grokspawn

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

@camilamacedo86
Copy link
Contributor Author

/restest required

@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

4 similar comments
@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@camilamacedo86
Copy link
Contributor Author

/retest-required

@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1b06fc6 and 2 for PR HEAD 149c2bd in total

6 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1b06fc6 and 2 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1b06fc6 and 2 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1b06fc6 and 2 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1b06fc6 and 2 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1b06fc6 and 2 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1b06fc6 and 2 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD af40962 and 1 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 778bd57 and 0 for PR HEAD 149c2bd in total

@openshift-ci-robot
Copy link

/hold

Revision 149c2bd was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 8, 2025
@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@camilamacedo86 camilamacedo86 force-pushed the add-update-images-catalogs branch from 149c2bd to 9db536d Compare August 11, 2025 17:38
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 11, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 11, 2025

New changes are detected. LGTM label has been removed.

@camilamacedo86
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 11, 2025
@camilamacedo86 camilamacedo86 force-pushed the add-update-images-catalogs branch from 9db536d to 9db7789 Compare August 11, 2025 17:56
@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

1 similar comment
@camilamacedo86
Copy link
Contributor Author

/test openshift-e2e-aws

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Aug 12, 2025

@camilamacedo86: 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/okd-scos-e2e-aws-ovn 9db7789 link false /test okd-scos-e2e-aws-ovn
ci/prow/openshift-e2e-aws 9db7789 link true /test openshift-e2e-aws
ci/prow/openshift-e2e-aws-techpreview 9db7789 link false /test openshift-e2e-aws-techpreview

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
Reviewers

@grokspawn grokspawn grokspawn approved these changes

@bentito bentito Awaiting requested review from bentito

@dtfranz dtfranz Awaiting requested review from dtfranz

Assignees

@grokspawn grokspawn

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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@camilamacedo86 @openshift-ci-robot @dtfranz @grokspawn