Remove 'default-instance-type' from environments file.

Bug #1069883 reported by Andrew Glen-Young on 2012-10-22
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pyjuju
Medium
Martin Packman
0.5
Medium
Martin Packman
0.6
Medium
Martin Packman

Bug Description

Juju requires that the 'default-instance-type' in the environments.yaml file exist, but it is unused (at least for the openstack provider). If the variable is no longer needed, juju should emit a deprecation warning and not launch the instance.

It is confusing to a user as setting default-instance-type=m1.small and launching an instance results in a m1.tiny instance being launched.

Setting the instance type using constraints on launch works as expected.

Juju version: 0.6.0.1+bzr598
Ubuntu version: 12.04.1

Related branches

Haw Loeung (hloeung) on 2012-10-22
tags: added: canonical-webops-juju
Martin Packman (gz) wrote :

There is already a warning in the code, but the condition is backwards, so it's emitted if default-instance-type is *not* defined... which is never the case as the config doesn't treat it as optional. Additionally the value is ignored in favour if the default constraints in all cases.

Changed in juju:
importance: Undecided → Medium
status: New → Confirmed
Martin Packman (gz) on 2012-11-13
Changed in juju:
assignee: nobody → Martin Packman (gz)
milestone: none → 0.7
status: Confirmed → In Progress
Martin Packman (gz) on 2012-11-14
Changed in juju:
status: In Progress → Fix Committed
Martin Packman (gz) on 2013-04-03
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers