We'll add back in the individual unit status items to the relation block, so you'll get to see both the relation status as originally intended, plus the unit status as requested. It will look something like the below. Note also we were incorrectly showing peer units in the relations section so this has been fixed also.
units:
keystone/0:
status: active
since: 2018-09-27 11:38:28Z
relations:
identity-service:
glance:
status: joined
since: 2018-09-27 11:37:16Z
glance/0:
status: active
since: 2018-09-27 11:27:19Z
glance/1:
status: active
since: 2018-09-27 11:27:34Z
glance/2:
status: active
since: 2018-09-27 11:27:55Z
glance/3:
status: active
since: 2018-09-27 11:27:28Z
glance/4:
status: waiting
since: 2018-09-27 11:29:42Z
shared-db:
mysql:
status: joined
since: 2018-09-27 11:34:26Z
mysql/0:
status: active
since: 2018-09-27 11:13:29Z
We'll add back in the individual unit status items to the relation block, so you'll get to see both the relation status as originally intended, plus the unit status as requested. It will look something like the below. Note also we were incorrectly showing peer units in the relations section so this has been fixed also.
units:
keystone/0:
status: active
since: 2018-09-27 11:38:28Z
relations:
identity-service:
glance:
status: joined
since: 2018-09-27 11:37:16Z
glance/0:
status: active
since: 2018-09-27 11:27:19Z
glance/1:
status: active
since: 2018-09-27 11:27:34Z
glance/2:
status: active
since: 2018-09-27 11:27:55Z
glance/3:
status: active
since: 2018-09-27 11:27:28Z
glance/4:
status: waiting
since: 2018-09-27 11:29:42Z
shared-db:
mysql:
status: joined
since: 2018-09-27 11:34:26Z
mysql/0:
status: active
since: 2018-09-27 11:13:29Z