designate-bind charm does not go into "blocked" state even if designate relations is missing

Bug #1784603 reported by Nobuto Murata on 2018-07-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Designate-Bind Charm
Medium
Unassigned

Bug Description

designate-bind charm becomes "Ready" just after the deployment. However, designate relation is required to be functional so the charm should go into "blocked" state when the relation is missing.

$ juju status --relations designate-bind
Model Controller Cloud/Region Version SLA Timestamp
default localhost-localhost localhost/localhost 2.4.1 unsupported 19:19:54+09:00

App Version Status Scale Charm Store Rev OS Notes
designate-bind 9.10.3.dfsg.P4 active 1 designate-bind local 0 ubuntu

Unit Workload Agent Machine Public address Ports Message
designate-bind/0* active idle 0 10.0.8.62 Unit is ready

Machine State DNS Inst id Series AZ Message
0 started 10.0.8.62 juju-48e2b8-0 xenial Running

Relation provider Requirer Interface Type Message
designate-bind:cluster designate-bind:cluster openstack-ha peer

Model Controller Cloud/Region Version SLA Timestamp
designate-bind icey-serverstack serverstack/serverstack 2.5.4 unsupported 07:58:09Z

App Version Status Scale Charm Store Rev OS Notes
designate-bind 9.10.3.dfsg.P4 active 1 designate-bind jujucharms 65 ubuntu

Unit Workload Agent Machine Public address Ports Message
designate-bind/0* active idle 0 10.5.0.36 Unit is ready

Machine State DNS Inst id Series AZ Message
0 started 10.5.0.36 3c8f7363-6158-47aa-bdc0-7ee662287890 xenial nova ACTIVE

Changed in charm-designate-bind:
status: New → Confirmed
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers