Error message when trying to deploy to node 0 on LXC needs to be more user friendly

Bug #1378792 reported by Jorge Castro
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Anastasia

Bug Description

This error needs to be worded better:

    ERROR cannot assign unit "wordpress/0" to machine 0: machine "0" cannot host units

Maybe something like:

    ERROR cannot assign unit "wordpress/0" to machine 0: machine "0" is LXC host and cannot host units, use another machine.

(or something that gives the user a place to go) See: https://lists.ubuntu.com/archives/juju/2014-October/004309.html

Tags: papercut ui
Jorge Castro (jorge)
tags: added: papercut
Revision history for this message
Andrew Wilkins (axwalk) wrote :

There is talk about updating the local provider to not have machine 0 on the host, which would make this problem go away altogether. We should make the error message more useful in the mean time, though.

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → next-stable
Revision history for this message
Martin Packman (gz) wrote :

Catch here is the error message is from inside state, and just looks at the JobHostUnits flag, so it doesn't actually know there whether the machine can't host because it's machine 0 on a local provider.

Ian Booth (wallyworld)
Changed in juju-core:
assignee: nobody → Anastasia (anastasia-macmood)
milestone: next-stable → 1.21-alpha2
Curtis Hovey (sinzui)
tags: added: ui
Changed in juju-core:
status: Triaged → In Progress
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
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.