bad message if dashboard is not ready

[Ian Booth]

After deploying the dashboard, you run the dashboard command to use it. But if the dashboard is not ready yet (charm not active, relation data not set), a bad message is displayed.

$ juju dashboard
ERROR getting dashboard address for controller "foo": dashboard address in relation data not found

[ALU (c-launchpadmail)]

Not sure if the issue I'm getting is a duplicate of this or not.

It seems that the dashboard is active but you still get this error with juju 3.0 even if the dashboard is successfully deployed ?

Command history:

$ juju models
Controller: R1

Model Cloud/Region Type Status Machines Units Access Last connection
controller localhost/localhost lxd available 1 1 admin just now

$ juju switch controller
R1 (controller) -> R1:admin/controller

$ juju deploy juju-dashboard
Located charm "juju-dashboard" in charm-hub, revision 6
Deploying "juju-dashboard" from charm-hub charm "juju-dashboard", revision 6 in channel stable on ubuntu@20.04/stable

$ juju expose juju-dashboard --show-log --verbose
12:53:10 INFO juju.cmd supercommand.go:56 running juju [3.0.0 35c560704ee254219ae0c4a37810bde5278e99bb gc go1.18.5]
12:53:10 INFO juju.juju api.go:86 connecting to API addresses: [10.20.172.76:17070]
12:53:10 INFO juju.api apiclient.go:703 connection established to "wss://10.20.172.76:17070/model/REDACTED/api"
12:53:10 INFO cmd supercommand.go:544 command finished

$ juju dashboard --debug --verbose
12:56:07 INFO juju.cmd supercommand.go:56 running juju [3.0.0 35c560704ee254219ae0c4a37810bde5278e99bb gc go1.18.5]
12:56:07 DEBUG juju.cmd supercommand.go:57 args: []string{"/snap/juju/21122/bin/juju", "dashboard", "--debug", "--verbose"}
12:56:07 INFO juju.juju api.go:86 connecting to API addresses: [10.20.172.76:17070]
12:56:07 DEBUG juju.api apiclient.go:1168 successfully dialed "wss://10.20.172.76:17070/api"
12:56:07 INFO juju.api apiclient.go:703 connection established to "wss://10.20.172.76:17070/api"
12:56:07 DEBUG juju.api monitor.go:35 RPC connection died
ERROR getting dashboard address for controller "R1": no dashboard found not found
12:56:07 DEBUG cmd supercommand.go:537 error stack:
no dashboard found not found
github.com/juju/juju/cmd/juju/dashboard.(*dashboardCommand).Run:137: getting dashboard address for controller "R1"

[ALU (c-launchpadmail)]

Disregard my last comment - I figured out that with juju 3.0 I missed the step

juju integrate controller juju-dashboard

[Jordan Barrett (barrettj12)]

https://github.com/juju/juju/pull/14849