Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grafana role changes monitoring stack config if user workload monitoring was not enabled #1458

Closed
witekwww opened this issue Sep 9, 2024 · 1 comment · Fixed by #1547 or #1549
Closed
Labels
Bug Report Something isn't working Critical - Tracked in Jira Issues that have been escalated internally and are tracked in Jira now
Milestone

Comments

@witekwww
Copy link
Contributor

witekwww commented Sep 9, 2024

Collection version

22.5.2

Environment information

quay.io/ibmmas/cli 10.9.2

What happened?

When installing MAS Core using oneclick playbook the grafana role is run. This role checks if there is user workload monitoring enabled. If not it changes the cluster-monitoring-config ConfigMap. The role does not append the 'enableUserWorkload: true' but removes all the config that was in the configmap before. It should only append the necessary entry and not remove all previous configuration.

Relevant log output

no log available.
The code responsible for the bug is this (ibm/mas_devops/roles/grafana/tasks/install/main.yml, lines 11-23):

- name: "install : Configure User Workload Monitoring"
  when: uwm_secret_lookup.resources | length == 0
  kubernetes.core.k8s:
    template: templates/cluster-monitoring-config.yml.j2
@witekwww witekwww added the Bug Report Something isn't working label Sep 9, 2024
@durera durera added the Critical - Tracked in Jira Issues that have been escalated internally and are tracked in Jira now label Nov 1, 2024
@durera
Copy link
Contributor

durera commented Nov 1, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Something isn't working Critical - Tracked in Jira Issues that have been escalated internally and are tracked in Jira now
Projects
None yet
2 participants