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

Unauthorized for url http://xxxx/api/dashboards/db, purge-dashboard not working #7265

Closed
jeevadotnet opened this issue Jul 29, 2022 · 4 comments · Fixed by #7266
Closed

Unauthorized for url http://xxxx/api/dashboards/db, purge-dashboard not working #7265

jeevadotnet opened this issue Jul 29, 2022 · 4 comments · Fixed by #7266

Comments

@jeevadotnet
Copy link

Bug Report

What happened:
Upgraded from octopus to pacific 16.2.10
And the dashboard no longer works, with ansible-playbook failing on:
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: http://10.102.73.89:3000/api/dashboards/db

I then try to purge the dashboard with the provided infrastructure playbook:
ansible-playbook -i /opt/ceph-ansible/inventory -e 'ansible_python_interpreter=/usr/bin/python3' infrastructure-playbooks/purge-dashboard.yml --limit=grafana-server

However this run successfully but does not remove all the containers as prescribed in the playbook. It only removes node-exporter but not grafana, prometheus, alertmanager

What you expected to happen:
For the dashboard elements all to be deleted & purged. So that I can redeploy it from site-container.yml --limit=grafana-server

How to reproduce it (minimal and precise):
Deploy site-container.yml to existing setup with a dashboard
or
upgrade from octopus to pacific
or
purge-dashboard.yml

Share your group_vars files, inventory and full ceph-ansibe log
Anible-log for site-container --limit=grafana-server
ansible-log for purge-dashboard --limit=grafana-server

Group_vars

Environment:

  • OS (e.g. from /etc/os-release): Ubuntu 20.04.4 LTS
  • Kernel (e.g. uname -a): Linux B-03-11-cephctl 5.4.0-122-generic
  • Docker version if applicable (e.g. docker version): 20.10.12
  • Ansible version (e.g. ansible-playbook --version): 2.9.27
  • ceph-ansible version (e.g. git head or tag or stable branch): stable-6.0
  • Ceph version (e.g. ceph -v): 16.2.10
@guits
Copy link
Collaborator

guits commented Jul 29, 2022

i see

2022-07-29 11:20:42,003 p=2715436 u=ilifu-adm n=ansible | PLAY [purge ceph monitoring] **********************************************************************************************************************************************************************************
2022-07-29 11:20:42,003 p=2715436 u=ilifu-adm n=ansible | skipping: no hosts matched

could you please share your inventory host ?

@guits
Copy link
Collaborator

guits commented Jul 29, 2022

@jeevadotnet i think it's because you are using the 'legacy' group name grafana-server

@guits
Copy link
Collaborator

guits commented Jul 29, 2022

@jeevadotnet we probably need something like this https://github.com/ceph/ceph-ansible/blob/main/infrastructure-playbooks/cephadm-adopt.yml#L30-L34 in the purge-dashboard.yml playbook

guits added a commit that referenced this issue Jul 29, 2022
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
@jeevadotnet
Copy link
Author

It only strips node-explorer.

Alertmanager, grafana server and prometheus stays behind running.

I'm using

[grafana-server]
B-03-11-cephctl.maas

guits added a commit that referenced this issue Jul 29, 2022
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
mergify bot pushed a commit that referenced this issue Jul 29, 2022
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
(cherry picked from commit a9cb444)
mergify bot pushed a commit that referenced this issue Jul 29, 2022
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
(cherry picked from commit a9cb444)
guits added a commit that referenced this issue Aug 1, 2022
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
(cherry picked from commit a9cb444)
guits added a commit that referenced this issue Aug 1, 2022
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
(cherry picked from commit a9cb444)
guits added a commit that referenced this issue Aug 4, 2022
When using the legacy group name 'grafana-server', this playbook will run but
won't remove properly all monitoring resources as expected.

Fixes: #7265

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
(cherry picked from commit a9cb444)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants