origin
origin copied to clipboard
openshift
[release-4.16] OCPBUGS-57311: Replace RunHostCmd with Exec function to censor bearer token being exposed
This is an automated cherry-pick of #29539
/assign KeerthanaAP
@openshift-cherrypick-robot: Jira Issue OCPBUGS-50664 has been cloned as Jira Issue OCPBUGS-57311. Will retitle bug to link to clone. /retitle [release-4.16] OCPBUGS-57311: Replace RunHostCmd with Exec function to censor bearer token being exposed
In response to this:
This is an automated cherry-pick of #29539
/assign KeerthanaAP
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: This pull request references Jira Issue OCPBUGS-57311, which is invalid:
- expected dependent Jira Issue OCPBUGS-50664 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 #29539
/assign KeerthanaAP
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.
@KeerthanaAP: This pull request references Jira Issue OCPBUGS-57311, 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.16.z) matches configured target version for branch (4.16.z)
- bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
- release note text is set and does not match the template
- dependent bug Jira Issue OCPBUGS-50664 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-50664 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dgoodwin, openshift-cherrypick-robot, tvardema
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [dgoodwin]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@openshift-cherrypick-robot: Jira Issue OCPBUGS-57311: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-57311 has been moved to the MODIFIED state.
In response to this:
This is an automated cherry-pick of #29539
/assign KeerthanaAP
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.
[ART PR BUILD NOTIFIER]
Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.16.0-202508010636.p0.g334a53b.assembly.stream.el9. All builds following this will include this PR.
Fix included in accepted release 4.16.0-0.nightly-2025-08-01-120002
@AnushaIH11: only openshift org members may request cherry picks. If you are already part of the org, make sure to change your membership to public. Otherwise you can still do the cherry-pick manually.
In response to this:
/cherry-pick release-4.15
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.
@alokgoswami-ag: #29908 failed to apply on top of branch "release-4.15":
Applying: Replace RunHostCmd with oc exec function to censor bearer token being exposed
Using index info to reconstruct a base tree...
M test/extended/prometheus/prometheus.go
M test/extended/router/metrics.go
M test/extended/util/client.go
M test/extended/util/prometheus/helpers.go
Falling back to patching base and 3-way merge...
Auto-merging test/extended/util/prometheus/helpers.go
CONFLICT (content): Merge conflict in test/extended/util/prometheus/helpers.go
Auto-merging test/extended/util/client.go
Auto-merging test/extended/router/metrics.go
CONFLICT (content): Merge conflict in test/extended/router/metrics.go
Auto-merging test/extended/prometheus/prometheus.go
CONFLICT (content): Merge conflict in test/extended/prometheus/prometheus.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Replace RunHostCmd with oc exec function to censor bearer token being exposed
In response to this:
/cherry-pick release-4.15
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.