console icon indicating copy to clipboard operation
console copied to clipboard

[release-4.17] OCPBUGS-43073: Telemetry userPreference results in empty nodes output to the DOM

Open openshift-cherrypick-robot opened this issue 1 year ago • 6 comments

This is an automated cherry-pick of #14291

/assign lokanandaprabhu

@openshift-cherrypick-robot: Jira Issue OCPBUGS-38717 has been cloned as Jira Issue OCPBUGS-43073. Will retitle bug to link to clone. /retitle [release-4.17] OCPBUGS-43073: Telemetry userPreference results in empty nodes output to the DOM

In response to this:

This is an automated cherry-pick of #14291

/assign lokanandaprabhu

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 avatar Oct 11 '24 04:10 openshift-ci-robot

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-43073, 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". For more information you can reference the OpenShift Bug Process.
  • expected dependent Jira Issue OCPBUGS-38717 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:

This is an automated cherry-pick of #14291

/assign lokanandaprabhu

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 avatar Oct 11 '24 04:10 openshift-ci-robot

Tested using cluster bot. Working fine.

https://github.com/user-attachments/assets/c759c63f-4bc6-4ed3-9e1b-e0d720d304b4

/lgtm /retest

lokanandaprabhu avatar Oct 11 '24 06:10 lokanandaprabhu

[APPROVALNOTIFIER] This PR is APPROVED

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

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[bot] avatar Oct 11 '24 06:10 openshift-ci[bot]

@openshift-cherrypick-robot: all tests passed!

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.

openshift-ci[bot] avatar Oct 11 '24 08:10 openshift-ci[bot]

/cc @vikram-raj @sanketpathak @The-Anton

lokanandaprabhu avatar Oct 23 '24 06:10 lokanandaprabhu

/jira refresh

lokanandaprabhu avatar Nov 08 '24 04:11 lokanandaprabhu

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-43073, 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". For more information you can reference the OpenShift Bug Process.

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.

openshift-ci-robot avatar Nov 08 '24 04:11 openshift-ci-robot

/jira refresh

lokanandaprabhu avatar Nov 08 '24 04:11 lokanandaprabhu

@lokanandaprabhu: This pull request references Jira Issue OCPBUGS-43073, 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-38717 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-38717 targets the "4.18.0" version, which is one of the valid target versions: 4.18.0
  • bug has dependents

Requesting review from QA contact: /cc @sanketpathak

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 avatar Nov 08 '24 04:11 openshift-ci-robot

/label cherry-pick-approved

The-Anton avatar Nov 20 '24 05:11 The-Anton

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

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

In response to this:

This is an automated cherry-pick of #14291

/assign lokanandaprabhu

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 avatar Nov 20 '24 14:11 openshift-ci-robot

/cherrypick release-4.16

lokanandaprabhu avatar Nov 22 '24 05:11 lokanandaprabhu

@lokanandaprabhu: new pull request created: #14528

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.