Charm channel is not displayed correctly in `juju status` output
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Evanson Mwangi | ||
Bug Description
A charm channel is not displayed correctly in the `juju status` output.
I tried to deploy a charm using a non-stable channel:
```
juju bootstrap aws aws
juju add-model test
juju deploy mysql --channel=beta
juju status
```
And got the incorrect channel value in the status output:
```
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
test aws aws/us-east-1 3.0-beta1 unsupported 18:45:00+03:00
App Version Status Scale Charm Channel Rev Exposed Message
mysql 5.7.33 unknown 1 mysql stable 58 no
Unit Workload Agent Machine Public address Ports Message
mysql/0* active idle 0 3.81.119.53 3306/tcp Ready
Machine State Address Inst id Series AZ Message
0 started 3.81.119.53 i-015b32b8c5ba16d0b xenial us-east-1a running
```
The channel was `stable` instead of `beta`.
| Changed in juju: | |
| milestone: | none → 3.0-beta2 |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in juju: | |
| milestone: | 3.0-beta2 → 3.0-beta3 |
| Changed in juju: | |
| assignee: | nobody → Evanson Mwangi (mr-parish) |
| no longer affects: | snapstore-server |
| Vitaly Antonenko (anvial) wrote | #1 |
duplicate:
https:/