Juju status command fails parsing charm

[Joseph Phillips]

When running "juju status" we don't see this, but when using "watch" the error is visible.

Every 2.0s: juju status -m default --relations --storage --color THYR: Mon Mar 28 14:32:30 2022

ERROR failed to parse charm: cannot parse URL "ch:amd64/trusty/mediawiki-28": schema "ch" not valid
ERROR failed to parse charm: cannot parse URL "ch:amd64/focal/ubuntu-19": schema "ch" not valid
Model Controller Cloud/Region Version SLA Timestamp
default dst lxd/default 2.9.28.1 unsupported 14:32:30+02:00

SAAS Status Store URL
mariadb active scratch admin/default.mariadb

App Version Status Scale Charm Store Rev OS Notes
mediawiki 1.19.14 active 1 0 ubuntu
ubuntu 20.04 active 1 0 ubuntu

Unit Workload Agent Machine Public address Ports Message
mediawiki/0* active idle 1 10.161.87.222 80/tcp Ready
ubuntu/0* active idle 0 10.161.87.237

Machine State DNS Inst id Series AZ Message
0 started 10.161.87.237 juju-147a94-0 focal Running
1 started 10.161.87.222 juju-147a94-1 trusty Running

Relation provider Requirer Interface Type Message
mariadb:db mediawiki:db mysql regular

[Joseph Phillips (manadart)]

Pastebin with better formatting:
https://pastebin.canonical.com/p/DKf8xfQQjs/

[John A Meinel (jameinel)]

So that is expected if you were using juju 2.8 to run status, and it is
plausible that `watch` is finding a different `juju` than your normal `juju
status` which is where the disagreement comes. You could `watch juju
--version` to confirm that suspicion, I think.

On Mon, Mar 28, 2022 at 8:45 AM Joseph Phillips <email address hidden>
wrote:

> Pastebin with better formatting:
> https://pastebin.canonical.com/p/DKf8xfQQjs/
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1966676
>
> Title:
> Juju status command fails parsing charm
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1966676/+subscriptions
>
>