memcached charm report unknown state to Juju
Bug #1657810 reported by
Aymen Frikha
This bug affects 9 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| memcached-charm |
Fix Released
|
Medium
|
David Ames | ||
Bug Description
After each deployment of memcached charm there is unknown state of the charm (not active) even if the charm succeded to be deployed
| affects: | mongodb (Juju Charms Collection) → memcached (Juju Charms Collection) |
| no longer affects: | memcached (Juju Charms Collection) |
| Changed in memcached-charm: | |
| status: | New → Confirmed |
Revision history for this message
| Felipe Reyes (freyes) wrote | #1 |
| Changed in memcached-charm: | |
| importance: | Undecided → Medium |
| status: | Confirmed → Fix Committed |
| assignee: | nobody → David Ames (thedac) |
| tags: | added: sts |
Revision history for this message
| Felipe Reyes (freyes) wrote | #2 |
| Changed in memcached-charm: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in 1c416ae ( https:/
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
default snowspeeder-
App Version Status Scale Charm Store Rev OS Notes
memcached active 1 memcached local 69 ubuntu
Unit Workload Agent Machine Public address Ports Message
memcached/0* active idle 0 192.168.10.14 11211/tcp Unit is ready
Machine State DNS Inst id Series AZ Message
0 started 192.168.10.14 juju-ddde27-0 xenial Running