Canonical Juju

ERROR juju.worker.meterstatus error running "meter-status-changed": charm missing from disk

Bug #1977848 reported by John A Meinel
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Unassigned

Bug Description

As part of just doing a normal deploy of a charm, I ended up getting:
unit-ubuntu-operator-4: 08:53:14 ERROR juju.worker.meterstatus error running "meter-status-changed": charm missing from disk

We shouldn't have an ERROR in a common workflow.
First, because we are removing things like budget, etc, we can probably get rid of meter-status-changed in 3.0. But even further we should never trigger an error. Whatever the cause of the above, it sounds like we are trying to run meter-status-changed before we've even unpacked the charm on disk.

Revision history for this message
Alok Prudhvi (alokprudhvi) wrote :

I'm facing the same issue on mysql-innodb-cluster and i see the unit is in blocked state.

Revision history for this message
Jordan Barrett (barrettj12) wrote :

I'm experiencing the same error message in Juju 3.0-beta4-af9f362 when bootstrapping an LXD controller (error from the controller charm):
```
unit-controller-0: 15:18:06 ERROR juju.worker.meterstatus error running "meter-status-changed": charm missing from disk
```

SSH'ing into the machine, the charm directory is still intact, so not sure what's happening.

Revision history for this message
Alok Prudhvi (alokprudhvi) wrote :

What i've identified in my environment is the core20 snap is not allowing mysql to start and the see few errors messages on that. So tried rebooting the lxd container and now i complete lost the control of the unit and i logged into host and tried to do an lxc list which is also not working and then saw the snap list and found that the same core20 snap is in disable state and don't know what's the issue. I'm still stuck with this problem and not able to recover the mysql-cluster

Ian Booth (wallyworld)
Changed in juju:
milestone: 2.9-next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.