Buggy behaviour when using --version flag

Bug #1998783 reported by Juan M. Tirado
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Unassigned

Bug Description

The `--version` flag forces a buggy behaviour in Juju. See these examples:

juju bootstrap --version
ERROR unknown cloud "version", please try "juju update-public-clouds"

juju status --version
<hanged>

juju model --version
<hanged>

Changed in juju:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Juan M. Tirado (tiradojm) wrote :

After running `juju update-public-clouds` `juju bootstrap --version` continues showing the same error.

Revision history for this message
Robert Gildein (rgildein) wrote :

I hit similar issue with our plugin called `juju-spell`.

This issue occurs as follows.
```bash
$ juju spell --version
# debug print ['/home/rgildein/code/canonical/multijuju/.venv/bin/juju-spell', 'version']
Usage: juju-spell [options] command [args]...
Try 'juju-spell -h' for help.

Error: no such command 'version'

$ juju-spell --version
['/home/rgildein/code/canonical/multijuju/.venv/bin/juju-spell', '--version']
JujuSpell: 0.0.1
```

It look like that juju will remove `--` and pass only `version`.

I'm using juju "2.9.38-ubuntu-amd64" version.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.