Skip to content

OCPBUGS-52340: Ensure that PSA label is latest instead of pinning versions#600

Merged
openshift-merge-bot[bot] merged 1 commit into
operator-framework:masterfrom
camilamacedo86:fix-psa-label-latest
Mar 14, 2025
Merged

OCPBUGS-52340: Ensure that PSA label is latest instead of pinning versions#600
openshift-merge-bot[bot] merged 1 commit into
operator-framework:masterfrom
camilamacedo86:fix-psa-label-latest

Conversation

@camilamacedo86

@camilamacedo86 camilamacedo86 commented Mar 6, 2025

Copy link
Copy Markdown
Contributor

Description of the change:

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

@openshift-ci openshift-ci Bot requested review from ankitathomas and grokspawn March 6, 2025 09:51
@camilamacedo86 camilamacedo86 changed the title Ensure that PSA label is latest instead of pinning versions OCPBUGS-52340: Ensure that PSA label is latest instead of pinning versions Mar 6, 2025
@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/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Mar 6, 2025
@openshift-ci-robot

openshift-ci-robot commented Mar 6, 2025

Copy link
Copy Markdown
Contributor

@camilamacedo86: This pull request references Jira Issue OCPBUGS-52340, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

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

Details

In response to this:

Description of the change:

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

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 commented Mar 6, 2025

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.18 release-4.17 release-4.16

@openshift-cherrypick-robot

openshift-cherrypick-robot commented Mar 6, 2025

Copy link
Copy Markdown

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

Details

In response to this:

/cherry-pick release-4.18 release-4.17 release-4.16

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.

@camilamacedo86

camilamacedo86 commented Mar 6, 2025

Copy link
Copy Markdown
Contributor Author

/cherry-pick release-4.17

@perdasilva

perdasilva commented Mar 6, 2025

Copy link
Copy Markdown
Contributor

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 6, 2025
@openshift-ci

openshift-ci Bot commented Mar 6, 2025

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Mar 6, 2025
@jianzhangbjz jianzhangbjz mentioned this pull request Mar 7, 2025
Closed
@jianzhangbjz

jianzhangbjz commented Mar 7, 2025

Copy link
Copy Markdown
Contributor

Test pass, details: https://issues.redhat.com/browse/OCPBUGS-52340

@jianzhangbjz

jianzhangbjz commented Mar 7, 2025

Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Mar 7, 2025
@openshift-ci-robot

openshift-ci-robot commented Mar 7, 2025

Copy link
Copy Markdown
Contributor

@camilamacedo86: This pull request references Jira Issue OCPBUGS-52340, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

In response to this:

Description of the change:

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

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 commented Mar 7, 2025

Copy link
Copy Markdown
Contributor Author

/retest-required

@camilamacedo86

camilamacedo86 commented Mar 7, 2025

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-ovn-serial

@openshift-ci

openshift-ci Bot commented Mar 7, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

@camilamacedo86: The following test 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 715d9f6 link false /test okd-scos-e2e-aws-ovn

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.

@camilamacedo86

camilamacedo86 commented Mar 14, 2025

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-ovn-serial

@camilamacedo86

camilamacedo86 commented Mar 14, 2025

Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console-olm

@openshift-merge-bot openshift-merge-bot Bot merged commit ea8fbfe into operator-framework:master Mar 14, 2025
@openshift-ci-robot

openshift-ci-robot commented Mar 14, 2025

Copy link
Copy Markdown
Contributor

@camilamacedo86: Jira Issue OCPBUGS-52340: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-52340 has been moved to the MODIFIED state.

Details

In response to this:

Description of the change:

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

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-cherrypick-robot

openshift-cherrypick-robot commented Mar 14, 2025

Copy link
Copy Markdown

@camilamacedo86: new pull request created: #601

Details

In response to this:

/cherry-pick release-4.18 release-4.17 release-4.16

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Mar 14, 2025
Merged
@openshift-bot

openshift-bot commented Mar 14, 2025

Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: marketplace-operator
This PR has been included in build marketplace-operator-container-v4.19.0-202503142240.p0.gea8fbfe.assembly.stream.el9.
All builds following this will include this PR.

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

Reviewers

@ankitathomas ankitathomas Awaiting requested review from ankitathomas

@grokspawn grokspawn Awaiting requested review from grokspawn

Assignees

@perdasilva perdasilva

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@camilamacedo86 @openshift-ci-robot @openshift-cherrypick-robot @perdasilva @jianzhangbjz @openshift-bot