Without --show-detail, crm_mon shows a single line per replica of a bundle. The state of the container is shown as the state of the replica (started, stopped, etc.). This can be misleading because the replica may have an IP, remote connection, and bundled primitive resource as well, that may be in a different state.
Show the state of the replica as started etc. only if all of the replica's resources are in that state. If some are started and others are starting, show starting; if some are stopped and others are stopping, show stopping; and so on as appropriate. When an overall state is not obvious, we could show "pending", "partially started", or something like that.
In particular, the output after setting a bundle's target-role to Disabled goes through the following:
- Stopping cluster01 (disabled)
- Stopped cluster01 (disabled)
- Stopped (disabled)
- Stopped cluster01
- Started cluster01
We really should just say "Starting" or "Stopping" until all implicit resources have finished.
Similar issues occur with other state descriptions such as unmanaged. We should show "unmanaged" only if all of the replica's resources are unmanaged, and show something like "partially unmanaged" if only some of its resources are unmanaged.
Also, bundle nodes are currently displayed as GuestNode. It would probably be a good idea to use something like Bundle node instead. (This might be worth doing at a major or minor series bump in case anyone is parsing the text output.)
When restarting a bundle resource, the output in crm_mon reflects the status of the container resource and not the underlying implicit resources. So if the container has started, the output will say "Started" even if the implicit resource are not yet up.