OCPBUGS-641: grafana: bump to 7.5.11

[jan--f]

Signed-off-by: Jan Fajerski jfajersk@redhat.com

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

[openshift-ci-robot]

@jan--f: This pull request references Jira Issue OCPBUGS-641, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.9.z) matches configured target version for branch (4.9.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-640 is in the state Closed (Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE))
• dependent Jira Issue OCPBUGS-640 targets the "4.10.0" version, which is one of the valid target versions: 4.10.0, 4.10.z
• bug has dependents

In response to this:

Signed-off-by: Jan Fajerski jfajersk@redhat.com

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

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]

@jan--f: 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.

Retaining the bugzilla/valid-bug label as it was manually added.

In response to this:

OCPBUGS-641: grafana: bump to 7.5.11

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.

[jan--f]

The version bump is in openshift/grafana#88

[openshift-ci]

@jan--f: The following tests 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/versions	47c0144	link	false	/test versions
ci/prow/e2e-aws-single-node	47c0144	link	false	/test e2e-aws-single-node

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.

[jan--f]

/label backport-risk-assessed

[juzhao]

tested with PR, OCP 4.9 grafana version is 7.5.11 and no regression issue
/label qe-approved

[juzhao]

/label cherry-pick-approved

[jan--f]

/lgtm

[openshift-ci]

@jan--f: you cannot LGTM your own PR.

In response to this:

/lgtm

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.

[raptorsun]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, raptorsun

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 [jan--f,raptorsun]

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

[openshift-ci-robot]

@jan--f: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

• openshift/grafana#88 is open

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

Signed-off-by: Jan Fajerski jfajersk@redhat.com

• I added CHANGELOG entry for this change.
• No user facing changes, so no entry in CHANGELOG was needed.

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.