[release-4.15] OCPBUGS-28769: fix generation of telemeter token hash

openshift-cherrypick-robot commented 6 months ago

This is an automated cherry-pick of #2298

/assign simonpasquier

openshift-ci-robot commented 6 months ago

@openshift-cherrypick-robot: Jira Issue OCPBUGS-28650 has been cloned as Jira Issue OCPBUGS-31904. Will retitle bug to link to clone. /retitle [release-4.15] OCPBUGS-31904: fix generation of telemeter token hash

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2303): >This is an automated cherry-pick of #2298 > >/assign simonpasquier Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift-ci-robot commented 6 months ago

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

expected dependent Jira Issue OCPBUGS-28650 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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](https://github.com/openshift/cluster-monitoring-operator/pull/2303): >This is an automated cherry-pick of #2298 > >/assign simonpasquier Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

simonpasquier commented 6 months ago

/retitle [release-4.15] OCPBUGS-28769: fix generation of telemeter token hash

openshift-ci-robot commented 6 months ago

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

expected dependent Jira Issue OCPBUGS-28650 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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](https://github.com/openshift/cluster-monitoring-operator/pull/2303): >This is an automated cherry-pick of #2298 > >/assign simonpasquier Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

simonpasquier commented 6 months ago

/label backport-risk-assessed /lgtm

openshift-ci[bot] commented 6 months ago

[APPROVALNOTIFIER] This PR is APPROVED

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

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: - ~~[OWNERS](https://github.com/openshift/cluster-monitoring-operator/blob/release-4.15/OWNERS)~~ [simonpasquier] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

simonpasquier commented 6 months ago

/cc @jan--f

openshift-ci[bot] commented 6 months ago

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

juzhao commented 6 months ago

/cc @Tai-RedHat

Tai-RedHat commented 6 months ago

test PR with cluster-bot, telemeter token has been encrypted /label cherry-pick-approved

simonpasquier commented 6 months ago

/jira redresh

simonpasquier commented 6 months ago

/jira refresh

openshift-ci-robot commented 6 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-28769, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
expected dependent Jira Issue OCPBUGS-28650 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](https://github.com/openshift/cluster-monitoring-operator/pull/2303#issuecomment-2047143219): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

simonpasquier commented 6 months ago

/jira refresh

openshift-ci-robot commented 6 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-28769, which is invalid:

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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](https://github.com/openshift/cluster-monitoring-operator/pull/2303#issuecomment-2051267410): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

simonpasquier commented 6 months ago

/jira refresh

openshift-ci-robot commented 6 months ago

@simonpasquier: This pull request references Jira Issue OCPBUGS-28769, 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.15.z) matches configured target version for branch (4.15.z) * bug is in the state ASSIGNED, 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-28650](https://issues.redhat.com//browse/OCPBUGS-28650) 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-28650](https://issues.redhat.com//browse/OCPBUGS-28650) targets the "4.16.0" version, which is one of the valid target versions: 4.16.0 * bug has dependents

Requesting review from QA contact: /cc @Tai-RedHat

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2303#issuecomment-2051281976): >/jira refresh Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift-ci-robot commented 6 months ago

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

openshift/cluster-monitoring-operator#2303

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

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2303): >This is an automated cherry-pick of #2298 > >/assign simonpasquier Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

openshift-bot commented 6 months ago

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-monitoring-operator-container-v4.15.0-202404120705.p0.g66612ac.assembly.stream.el9 for distgit cluster-monitoring-operator. All builds following this will include this PR.

openshift-merge-robot commented 6 months ago

Fix included in accepted release 4.15.0-0.nightly-2024-04-16-070254

openshift / cluster-monitoring-operator

[release-4.15] OCPBUGS-28769: fix generation of telemeter token hash #2303