juju deploy panics with invalid --to option
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Heather Lanigan |
Bug Description
Not a big issue, but maybe worth some input sanitizing:
root@server:~# juju --version
2.9.7-ubuntu-amd64
root@server:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
Accidentally used "--to 0,1,2," with the trailing comma, which caused a panic.
root@server:~# juju deploy -n 3 --to 0,1,2, --config vip=10.0.0.101 keystone
WARNING 3 unit(s) will be deployed, extra placement directives will be ignored
Located charm "keystone" in charm-hub, revision 533
Deploying "keystone" from charm-hub charm "keystone", revision 533 in channel stable
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1c54ce6]
goroutine 1 [running]:
github.
github.
github.
github.
github.
github.
github.
github.
github.
github.
main.main()
Command ran fine after fixing the --to option:
root@server:~# juju deploy -n 3 --to 0,1,2 --config vip=10.0.0.101 keystone
Located charm "keystone" in charm-hub, revision 533
Deploying "keystone" from charm-hub charm "keystone", revision 533 in channel stable
no longer affects: | charm-openstack-dashboard |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Heather Lanigan (hmlanigan) |
milestone: | none → 2.9.31 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.9.31 → 2.9.30 |
milestone: | 2.9.30 → 2.9.31 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Triaged as medium, but added "bitesize" tag so that it's easy to find for someone looking for low hanging fruit.