juju deploy output is misleading for bundles

[Dean Henrichsmeyer]

When you deploy a bundle using Juju 2, it reports the status of its database model to the user - which is irrelevant to the user.

As a user, I don't care that Juju added a container, deployed a service, and established a relation in the mongodb. I only care whether it actually happened or not.

Seeing things like:

annotations set for service rabbitmq-server
created new machine 0 for holding haproxy, landscape-server, postgresql and rabbitmq-server units
related landscape-server and rabbitmq-server
related landscape-server and haproxy
related landscape-server:db and postgresql:db-admin
created 0/lxc/0 container in machine 0 for holding haproxy unit
created 0/lxc/1 container in machine 0 for holding landscape-server unit
created 0/lxc/2 container in machine 0 for holding postgresql unit
created 0/lxc/3 container in machine 0 for holding rabbitmq-server unit
added haproxy/0 unit to machine 0/lxc/0
added landscape-server/0 unit to machine 0/lxc/1
added postgresql/0 unit to machine 0/lxc/2
added rabbitmq-server/0 unit to machine 0/lxc/3

is just not helpful because it isn't true. I mean if you look at that, it says it established a relation to a service (application) that it didn't even create a container for yet.

It would be far better and more accurate to feed back to the user either that Juju is initiating these operations or where it can, report the end state (agent status in the case of a unit). Telling me things are done that are not remotely close to being done is misleading and a bad experience.

[Cheryl Jennings (cherylj)]

Improving the output from the bundle deploy is in our plans for 2.1.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.