Initial 'unknown' status for subordinate charms is confusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
Hi,
The issue: juju sets initial status as `unknown` for subordinate charms.
It confuses (even experienced) users, the last example:
https:/
```
> Genc Tato 2:29 PM:
Hi again, I am trying to deploy pgbouncer on my local lxd, using the 1/edge channel:
> juju deploy pgbouncer --channel 1/edge
However, it stays in unknown state forever, and it doesn't even start any VM.
> App Version Status Scale Charm Channel Rev Exposed Message
> pgbouncer unknown 0 pgbouncer 1/edge 34 no
Any ideas why? ...
---
taurus 4:35 PM:
The pgbouncer (VM) is a subordinate charm, you need to relate it with a principal charm first to see the deployment progress.
Unfortunately, Juju keeps an unknown status for subordinate charms, instead of hinting users to relate it to continue...
```
It is a ticket to consider to set 'waiting' status for subordinate charms + message="Missing relation with a principal charm". Unfortunately it cannot be done inside charm as it is not yet launched.
Changed in juju: | |
assignee: | nobody → Caner Derici (cderici) |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: canonical-data-platform-eng |
Juju displays "unknown" initially by design, because that's a true indication of the state of the system. The charm is expected to communicate its status via the status-set command. Juju does not, and must not, guess what the state of any charm is; it needs to be explicitly told. If the charm does not do so, then that's a charm bug that needs to be fixed. This is not a juju issue.