openshift-ci-robot
commented
8 months ago @simonpasquier: This pull request references Jira Issue OCPBUGS-18326, which is invalid:
- expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "4.15.0" 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/2254):
>This commit adds the "capability.openshift.io/name: Console" annotation to the dashboard configmaps.
>
>It also renames the existing configmaps from "grafana-xxx" to "xxx" because otherwise CVO would enable the Console capability on all clusters, even those where the capability was initially disabled [1]. The CVO team has a feature request [2] to improve the situation but for now, we have no other option than creating the configmaps with a different name and deleting the old configmaps (anyway the "grafana-" prefix is misleading since OCP doesn't ship any Grafana instance by default).
>
>[1] https://github.com/openshift/enhancements/blob/master/enhancements/installer/component-selection.md#how-to-implement-a-new-capability
>[2] https://issues.redhat.com/browse/OTA-1039
>
>
>
>* [ ] I added CHANGELOG entry for this change.
>* [X] No user facing changes, so no entry in CHANGELOG was needed.
>
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
openshift-ci[bot]
jan--f
machine424
openshift-bot
openshift-merge-robot
This commit adds the "capability.openshift.io/name: Console" annotation to the dashboard configmaps.
It also renames the existing configmaps from "grafana-xxx" to "xxx" because otherwise CVO would enable the Console capability on all clusters, even those where the capability was initially disabled [1]. The CVO team has a feature request [2] to improve the situation but for now, we have no other option than creating the configmaps with a different name and deleting the old configmaps (anyway the "grafana-" prefix is misleading since OCP doesn't ship any Grafana instance by default).
[1] https://github.com/openshift/enhancements/blob/master/enhancements/installer/component-selection.md#how-to-implement-a-new-capability [2] https://issues.redhat.com/browse/OTA-1039