Skip to content

[release-4.17] OCPBUGS-57324: Fix bearer token exposure in exit condition as well #29910

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
Merged
merged 1 commit into from
Jul 21, 2025
Merged

[release-4.17] OCPBUGS-57324: Fix bearer token exposure in exit condition as well #29910

merged 1 commit into from
Jul 21, 2025

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jun 11, 2025

This is an automated cherry-pick of #29882

/assign alokgoswami-ag

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 11, 2025
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 11, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56995 has been cloned as Jira Issue OCPBUGS-57324. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-57324: Fix bearer token exposure in exit condition as well

In response to this:

This is an automated cherry-pick of #29882

/assign alokgoswami-ag

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 changed the title [release-4.17] OCPBUGS-56995: Fix bearer token exposure in exit condition as well [release-4.17] OCPBUGS-57324: Fix bearer token exposure in exit condition as well Jun 11, 2025
@openshift-ci-robot openshift-ci-robot added 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 11, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 11, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-57324, which is invalid:

  • expected dependent Jira Issue OCPBUGS-56995 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.

In response to this:

This is an automated cherry-pick of #29882

/assign alokgoswami-ag

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 simonpasquier and sjenning June 11, 2025 10:21
@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-metal-ipi-ovn-kube-apiserver-rollout

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-azure-ovn-upgrade

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-aws-ovn-upgrade

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-metal-ipi-ovn

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-aws-ovn-edge-zones

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-aws-ovn-single-node-upgrade

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-openstack-ovn

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-metal-ipi-ovn-ipv6

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-aws-ovn-serial

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 16, 2025

/test e2e-gcp-csi

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 17, 2025

/test e2e-openstack-ovn

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 17, 2025

/test e2e-azure-ovn-upgrade

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 17, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 17, 2025

/test e2e-aws-ovn-single-node-upgrade

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 17, 2025

/test e2e-gcp-csi

1 similar comment
@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 17, 2025

/test e2e-gcp-csi

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 17, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 25, 2025

/test e2e-aws-ovn-single-node-upgrade

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jun 25, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 2, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

1 similar comment
@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 7, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 7, 2025

/test e2e-aws-ovn-single-node-upgrade

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 7, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

2 similar comments
@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 9, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 14, 2025

/test e2e-vsphere-ovn-dualstack-primaryv6

@tvardema
Copy link
Contributor

tvardema commented Jul 16, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2025
@neisw
Copy link
Contributor

neisw commented Jul 17, 2025

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw, openshift-cherrypick-robot, tvardema

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 17, 2025
@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 18, 2025

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

@alokgoswami-ag: This pull request references Jira Issue OCPBUGS-57324, which is invalid:

  • expected dependent Jira Issue OCPBUGS-56995 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.

In response to this:

/jira refresh

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.

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 18, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-56995 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-56995 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

In response to this:

/jira refresh

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 openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 18, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

/retest-required

Remaining retests: 0 against base HEAD 88df91b and 2 for PR HEAD e5543fc in total

2 similar comments
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 18, 2025

/retest-required

Remaining retests: 0 against base HEAD 88df91b and 2 for PR HEAD e5543fc in total

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 19, 2025

/retest-required

Remaining retests: 0 against base HEAD 88df91b and 2 for PR HEAD e5543fc in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 19, 2025 •
edited
Loading

@openshift-cherrypick-robot: 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-vsphere-ovn-dualstack-primaryv6 e5543fc link false /test e2e-vsphere-ovn-dualstack-primaryv6

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.

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Jul 21, 2025

/test e2e-aws-ovn-serial

@openshift-merge-bot openshift-merge-bot bot merged commit 1d48f49 into openshift:release-4.17 Jul 21, 2025
29 of 30 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 21, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-57324: All pull requests linked via external trackers have merged:

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

In response to this:

This is an automated cherry-pick of #29882

/assign alokgoswami-ag

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

openshift-bot commented Jul 22, 2025

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.17.0-202507211835.p0.g1d48f49.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Jul 22, 2025

Fix included in accepted release 4.17.0-0.nightly-2025-07-22-124947

@alokgoswami-ag
Copy link
Contributor

alokgoswami-ag commented Oct 10, 2025

/cherrypick release-4.16

@openshift-cherrypick-robot
Copy link
Author

openshift-cherrypick-robot commented Oct 10, 2025

@alokgoswami-ag: new pull request created: #30365

In response to this:

/cherrypick 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 Oct 10, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@simonpasquier simonpasquier Awaiting requested review from simonpasquier

@sjenning sjenning Awaiting requested review from sjenning

Assignees

@tvardema tvardema

@alokgoswami-ag alokgoswami-ag

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. 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.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

8 participants

@openshift-cherrypick-robot @openshift-ci-robot @alokgoswami-ag @tvardema @neisw @openshift-bot @openshift-merge-robot @Shilpa-Gokul