juju status outputs ERROR "" is not a valid tag
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Undecided
|
Unassigned |
Bug Description
$ juju status
ERROR "" is not a valid tag
$ juju status --debug
11:45:53 INFO juju.cmd supercommand.go:63 running juju [2.0-rc2.4415 gc go1.6.2]
11:45:53 DEBUG juju.cmd supercommand.go:64 args: []string{"juju", "status", "--debug"}
11:45:53 INFO juju.juju api.go:72 connecting to API addresses: [10.0.5.62:17070]
11:45:53 INFO juju.api apiclient.go:507 dialing "wss://
11:45:53 INFO juju.api apiclient.go:302 connection established to "wss://
11:45:53 DEBUG juju.juju api.go:263 API hostnames unchanged - not resolving
11:45:53 DEBUG juju.api apiclient.go:558 health ping failed: connection is shut down
11:45:53 ERROR cmd supercommand.go:458 "" is not a valid tag
11:45:53 DEBUG cmd supercommand.go:459 (error details: [{"" is not a valid tag}])
$ juju version
2.0-rc2.
The current controller is LXD and the host crashed. This is the state of the system after the host has booted.
The LXD containers did start on host reboot:
$ lxc list
+------
| NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS |
+------
| juju-792d89-0 | RUNNING | 10.0.5.7 (eth0) | | PERSISTENT | 0 |
+------
| juju-7b224e-0 | RUNNING | 10.0.5.62 (eth0) | | PERSISTENT | 0 |
+------
jujud is running in that container:
$ ssh ubuntu@10.0.5.62
ubuntu@
root 391 0.0 0.0 19700 1380 ? Ss 13:07 0:00 bash /var/lib/
root 404 0.4 0.6 585344 50784 ? Sl 13:07 0:46 /var/lib/
ubuntu 1394 0.0 0.0 12944 812 pts/0 S+ 15:48 0:00 grep --color=auto jujud
Changed in juju-core: | |
status: | Incomplete → Invalid |
This happens when you have a controller bootstapped with b18 and the rc1 client. They two are not compatible.
Can you please verify that this was bootstrapped with rc1 and not with a previous beta?