Skip to content

USHIFT-6589: Fix subscription manager file usage#74501

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
ggiguash:fix-submgr-issue
Feb 6, 2026
Merged

USHIFT-6589: Fix subscription manager file usage#74501
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
ggiguash:fix-submgr-issue

Conversation

@ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Feb 6, 2026

Undo subscription files deletion from this change.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 6, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 6, 2026

@ggiguash: This pull request references USHIFT-6589 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 bug to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21.z" instead.

Details

In response to this:

Undo this change.

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 jogeo and pacevedom February 6, 2026 07:33
@ggiguash
Copy link
Contributor Author

ggiguash commented Feb 6, 2026

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

@ggiguash: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Feb 6, 2026
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 6, 2026

@ggiguash: This pull request references USHIFT-6589 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 bug to target either version "4.22." or "openshift-4.22.", but it targets "openshift-4.21.z" instead.

Details

In response to this:

Undo subscription files deletion from this change.

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
Copy link
Contributor

[REHEARSALNOTIFIER]
@ggiguash: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-microshift openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.23-e2e-aws-ovn-microshift-serial openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.22-e2e-aws-ovn-microshift openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.22-e2e-aws-ovn-microshift-serial openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.21-e2e-aws-ovn-microshift openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.21-e2e-aws-ovn-microshift-serial openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.20-e2e-aws-ovn-microshift openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.20-e2e-aws-ovn-microshift-serial openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-microshift openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-microshift-serial openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift openshift/origin presubmit Registry content changed
pull-ci-openshift-origin-release-4.18-e2e-aws-ovn-microshift-serial openshift/origin presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-footprint-and-performance openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-main-e2e-aws-ai-model-serving openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.23-e2e-aws-footprint-and-performance openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.23-e2e-aws-ai-model-serving openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.22-e2e-aws-footprint-and-performance openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.22-e2e-aws-ai-model-serving openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.21-e2e-aws-footprint-and-performance openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.21-e2e-aws-ai-model-serving openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-footprint-and-performance openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.20-e2e-aws-ai-model-serving openshift/microshift presubmit Registry content changed
pull-ci-openshift-microshift-release-4.19-e2e-aws-footprint-and-performance openshift/microshift presubmit Registry content changed

A total of 254 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@kasturinarra
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 6, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 6, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, kasturinarra

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

openshift-ci bot commented Feb 6, 2026

@ggiguash: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit ad76cd1 into openshift:master Feb 6, 2026
9 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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants