[release-4.11] OCPBUGS-9908: Garbage collect grafana-dashboard-etcd

[Elbehery]

this is a manual cherrypick of #1016

resolves https://issues.redhat.com/browse/OCPBUGS-9908

[openshift-ci]

@Elbehery: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-4.11] OCPBUGS-9908: Garbage collect grafana-dashboard-etcd

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/test-infra repository.

[openshift-ci-robot]

@Elbehery: This pull request references Jira Issue OCPBUGS-9908, which is invalid:

• expected dependent Jira Issue OCPBUGS-8393 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ASSIGNED 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 a manual cherrypick of #1016

resolves https://issues.redhat.com/browse/OCPBUGS-9908

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/test-infra repository.

[Elbehery]

/assign @dusk125

[tjungblu]

/lgtm

[Elbehery]

/assign @wking

[dusk125]

/approve
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, Elbehery, tjungblu

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 [dusk125]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Elbehery]

/assign @geliu2016

[geliu2016]

/label cherry-pick-approved

[tjungblu]

/cherry-pick release-4.10

[openshift-cherrypick-robot]

@tjungblu: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.10

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/test-infra repository.

[tjungblu]

/jira refresh

[openshift-ci-robot]

@tjungblu: This pull request references Jira Issue OCPBUGS-9908, which is invalid:

• expected dependent Jira Issue OCPBUGS-8393 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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 kubernetes/test-infra repository.

[tjungblu]

actually, we might not need this in 4.10, correct?

[Elbehery]

actually, we might not need this in 4.10, correct?

No, I think only till 4.11 iiuc

cc @wking

[openshift-cherrypick-robot]

@Elbehery: once the present PR merges, I will cherry-pick it on top of cancel in a new PR and assign it to you.

In response to this:

/cherry-pick cancel

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/test-infra repository.

[Elbehery]

/cherry-pick release-4.10

i tried /cherry-pick cancel but it is wrong :D .. how to cancel this ?

[Elbehery]

/jira refresh

[openshift-ci-robot]

@Elbehery: This pull request references Jira Issue OCPBUGS-9908, which is invalid:

• expected dependent Jira Issue OCPBUGS-8393 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), 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 kubernetes/test-infra repository.

[Elbehery]

/jira refresh

[openshift-ci-robot]

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

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.11.z) matches configured target version for branch (4.11.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-8393 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-8393 targets the "4.12.z" version, which is one of the valid target versions: 4.12.0, 4.12.z
• bug has dependents

Requesting review from QA contact:
/cc @geliu2016

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 kubernetes/test-infra repository.

[Elbehery]

@geliu2016 can you label this & verify please ?

[tjungblu]

/test e2e-operator

[Elbehery]

/test e2e-operator

[Elbehery]

/retest-required

[openshift-ci]

@Elbehery: 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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@Elbehery: Jira Issue OCPBUGS-9908: All pull requests linked via external trackers have merged:

• openshift/cluster-etcd-operator#1022

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

In response to this:

this is a manual cherrypick of #1016

resolves https://issues.redhat.com/browse/OCPBUGS-9908

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/test-infra repository.

[openshift-cherrypick-robot]

@tjungblu: #1022 failed to apply on top of branch "release-4.10":

Applying: OCPBUGS-9908: Garbage collect grafana-dashboard-etcd
Using index info to reconstruct a base tree...
M	hack/generate.sh
Falling back to patching base and 3-way merge...
Auto-merging hack/generate.sh
CONFLICT (content): Merge conflict in hack/generate.sh
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OCPBUGS-9908: Garbage collect grafana-dashboard-etcd
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.10

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/test-infra repository.

[Elbehery]

@geliu2016 can we verify this as well ?

Please ignore 4.10 backport 👍🏽