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

Pebble plan still contains logging endpoints even after loki is removed #27

Open
swetha1654 opened this issue Nov 28, 2024 · 1 comment

Comments

@swetha1654
Copy link
Contributor

swetha1654 commented Nov 28, 2024

Bug Description

I initially deployed the maubot charm and the loki charm (developed using anyCharm) and integrated those two. After deleting the loki charm, i can see the loki configuration details in the pebble plan of maubot-

As you can see here, loki application has been removed -
image

You can see the logging details here when i run pebble plan inside maubot after deleting loki app-
image

I believe the maubot operator should remove such information from the pebble plan once the application is removed

To Reproduce

juju deploy maubot
juju deploy loki-k8s # i originally deployed loki using anyCharm but i believe this is reproducible with the normal loki charm as well
juju integrate maubot loki-k8s
juju remove-application loki-k8s --force --no-wait --no-prompt
juju ssh --container maubot maubot/0 
pebble plan

Environment

user@myubuntu:~$ juju --version
3.5.4-genericlinux-amd64
user@myubuntu:~$ microk8s version
MicroK8s v1.29.10 revision 7396

Juju is run locally

Relevant log output

This contains all the revisions and the channels of the apps deployed - 

user@myubuntu:~/Canonical/maubot-operator$ juju status
Model     Controller    Cloud/Region        Version  SLA          Timestamp
testing1  mycontroller  microk8s/localhost  3.5.4    unsupported  16:53:41+05:30

App                       Version  Status  Scale  Charm                     Channel      Rev  Address         Exposed  Message
any-grafana                        active      1  any-charm                 latest/beta   44  10.152.183.22   no
any-loki                           active      1  any-charm                 latest/beta   44  10.152.183.162  no
maubot                             active      1  maubot                                   0  10.152.183.220  no
nginx-ingress-integrator           active      1  nginx-ingress-integrator  latest/edge   44  10.152.183.100  no       Ingress IP(s): 127.0.0.1, Service IP(s): 10.152.183.236
postgresql-k8s            14.12    active      1  postgresql-k8s            14/stable    444  10.152.183.42   no
synapse                            active      1  synapse                   latest/edge  493  10.152.183.77   no

Unit                         Workload  Agent  Address      Ports  Message
any-grafana/0*               active    idle   10.1.39.163
any-loki/0*                  active    idle   10.1.39.134
maubot/0*                    active    idle   10.1.39.165
nginx-ingress-integrator/0*  active    idle   10.1.39.188         Ingress IP(s): 127.0.0.1, Service IP(s): 10.152.183.236
postgresql-k8s/0*            active    idle   10.1.39.190         Primary
synapse/0*                   active    idle   10.1.39.178

Additional context

No response

@amandahla
Copy link
Collaborator

Issue will be tracked in ISD-2795

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

No branches or pull requests

2 participants