Skip to content

OCPBUGS-42526: Ensure that PSA label is latest instead of pinning versions#972

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
camilamacedo86:ensure-that-psa-label-latest
Mar 14, 2025
Merged

OCPBUGS-42526: Ensure that PSA label is latest instead of pinning versions#972
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
camilamacedo86:ensure-that-psa-label-latest

Conversation

@camilamacedo86
Copy link
Copy Markdown
Contributor

No description provided.

@openshift-ci openshift-ci Bot requested review from oceanc80 and perdasilva March 6, 2025 09:48
@camilamacedo86 camilamacedo86 changed the title Ensure that PSA label is latest instead of pinning versions OCPBUGS-42526: 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
Copy link
Copy Markdown

@camilamacedo86: This pull request references Jira Issue OCPBUGS-42526, 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 ASSIGNED, 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:

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

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

@openshift-cherrypick-robot
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 force-pushed the ensure-that-psa-label-latest branch from 41cabe9 to b6b4883 Compare March 6, 2025 10:46
@jianzhangbjz
Copy link
Copy Markdown
Contributor

jianzhangbjz commented Mar 7, 2025

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

@jianzhangbjz
Copy link
Copy Markdown
Contributor

/label qe-approved
/lgtm

@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
Copy link
Copy Markdown

@camilamacedo86: This pull request references Jira Issue OCPBUGS-42526, 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:

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 added the lgtm Indicates that a PR is ready to be merged. label Mar 7, 2025
@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/retest-required

Copy link
Copy Markdown
Contributor

@anik120 anik120 left a comment

Choose a reason for hiding this comment

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

/approve

Verified context from https://issues.redhat.com/browse/OCPBUGS-41849:

What
Set the version label of warn, audit and enforce to "latest" from "v1.24".

Why
We kept it at "v1.24" due to potential issues with HyperShift.
We are moving to "latest" to avoid the cost of maintaining it by-version.
It was discussed and decided in a meeting with David Eads (Wed Sep 12 2024).

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 7, 2025
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

1 similar comment
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console-olm

2 similar comments
@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console-olm

@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console-olm

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

1 similar comment
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

4 similar comments
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@camilamacedo86
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-console-olm

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 13, 2025

@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/e2e-gcp-olm-flaky b6b4883 link false /test e2e-gcp-olm-flaky

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-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD b6b4883 in total

@openshift-merge-bot openshift-merge-bot Bot merged commit 601c4fb into openshift:main Mar 14, 2025
2 checks passed
@openshift-ci-robot
Copy link
Copy Markdown

@camilamacedo86: Jira Issue OCPBUGS-42526: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

Details

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.

@openshift-cherrypick-robot
Copy link
Copy Markdown

@camilamacedo86: new pull request created: #983

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

[ART PR BUILD NOTIFIER]

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

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.19.0-202503140309.p0.g601c4fb.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.19.0-202503140610.p0.g601c4fb.assembly.stream.el9.
All builds following this will include this PR.

@camilamacedo86
Copy link
Copy Markdown
Contributor Author

Hi @anik120

Verified context from https://issues.redhat.com/browse/OCPBUGS-41849:

What
Set the version label of warn, audit and enforce to "latest" from "v1.24".

Why
We kept it at "v1.24" due to potential issues with HyperShift.
We are moving to "latest" to avoid the cost of maintaining it by-version.
It was discussed and decided in a meeting with David Eads (Wed Sep 12 2024).

To clarify:

@camilamacedo86 camilamacedo86 deleted the ensure-that-psa-label-latest branch March 15, 2025 08:10
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/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

Development

Successfully merging this pull request may close these issues.

6 participants