Skip to content

[release-4.19] OCPBUGS-88566: Verify extension packages are installed#6182

Open
isabella-janssen wants to merge 1 commit into
openshift:release-4.19from
isabella-janssen:ocpbugs-65645-419
Open

[release-4.19] OCPBUGS-88566: Verify extension packages are installed#6182
isabella-janssen wants to merge 1 commit into
openshift:release-4.19from
isabella-janssen:ocpbugs-65645-419

Conversation

@isabella-janssen

@isabella-janssen isabella-janssen commented Jun 12, 2026

Copy link
Copy Markdown
Member

Closes: OCPBUGS-88566

- What I did
This is a manual backport of #6114.

- How to verify it
See verification steps in #6010.

- Description for the changelog
OCPBUGS-88566 : Verify extension packages are installed

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@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 Jun 12, 2026
@openshift-ci

openshift-ci Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

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

@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 805dbbfc-6072-4968-80e1-5c3749e5256c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci

openshift-ci Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: isabella-janssen

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 12, 2026
@isabella-janssen

Copy link
Copy Markdown
Member Author

/jira cherrypick OCPBUGS-86864

@isabella-janssen isabella-janssen changed the title (WIP) OCPBUGS-65645 4.19 Verify extension packages are installed Jun 15, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@isabella-janssen: Jira Issue OCPBUGS-86864 has been cloned as Jira Issue OCPBUGS-88566. Will retitle bug to link to clone.
/retitle OCPBUGS-88566: (WIP) OCPBUGS-65645 4.19

Details

In response to this:

/jira cherrypick OCPBUGS-86864

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.

@isabella-janssen isabella-janssen changed the title Verify extension packages are installed [release-4.19] OCPBUGS-88567: Verify extension packages are installed Jun 15, 2026
@isabella-janssen isabella-janssen marked this pull request as ready for review June 15, 2026 15:24
@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 Jun 15, 2026
@openshift-ci openshift-ci Bot changed the title [release-4.19] OCPBUGS-88567: Verify extension packages are installed OCPBUGS-88566: (WIP) OCPBUGS-65645 4.19 Jun 15, 2026
@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 Jun 15, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 15, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@isabella-janssen: This pull request references Jira Issue OCPBUGS-88567, which is invalid:

  • expected dependent Jira Issue OCPBUGS-86864 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Closes: OCPBUGS-88567

- What I did
This is a manual backport of #6114.

- How to verify it
See verification steps in #6010.

- Description for the changelog
OCPBUGS-88567 : Verify extension packages are installed

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

@isabella-janssen: This pull request references Jira Issue OCPBUGS-88566, which is invalid:

  • expected dependent Jira Issue OCPBUGS-86864 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Closes: OCPBUGS-88567

- What I did
This is a manual backport of #6114.

- How to verify it
See verification steps in #6010.

- Description for the changelog
OCPBUGS-88567 : Verify extension packages are installed

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 Jun 15, 2026
@isabella-janssen isabella-janssen changed the title OCPBUGS-88566: (WIP) OCPBUGS-65645 4.19 [release-4.19] OCPBUGS-88566: Verify extension packages are installed Jun 15, 2026
@isabella-janssen

Copy link
Copy Markdown
Member Author

/test security

@openshift-ci

openshift-ci Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

@isabella-janssen: 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.

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. 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.

2 participants