default aws instance type too large

[John A Meinel]

I just did

 sudo snap refresh juju --channel 2.5/stable
 /snap/bin/juju/bootstrap aws test

And ended up with a d2.xlarge instance running in us-east-1a (4 cores, 31GB RAM). I don't know if we got our price listing wrong, or if there was a problem with one of our constraints, but that's 2x the CPUs and 10x the memory we should be targeting.

Note that I didn't specify a VPC (which I probably should), but we still shouldn't be defaulting to an instance that big. (I did try to find any reference to a load test, etc, that I might have configured, but I did not find anything and I don't have an 'aws' cloud that is separately defined.

[John A Meinel (jameinel)]

$ juju show-machine 0
model: controller
machines:
  "0":
    juju-status:
      current: started
      since: 27 May 2019 11:12:26Z
      version: 2.5.7
    dns-name: 100.24.107.104
    ip-addresses:
    - 100.24.107.104
    - 10.51.161.20
    instance-id: i-03fbe0746b239bbf6
    machine-status:
      current: running
      message: running
      since: 27 May 2019 11:12:34Z
    modification-status:
      current: idle
      since: 27 May 2019 11:12:16Z
    series: bionic
    network-interfaces:
      eth0:
        ip-addresses:
        - 10.51.161.20
        mac-address: 22:00:0a:33:a1:14
        gateway: 10.51.161.1
        is-up: true
    constraints: mem=3584M
    hardware: arch=amd64 cores=4 cpu-power=1344 mem=31232M root-disk=32768M availability-zone=us-east-1a
    controller-member-status: has-vote

[Anastasia (anastasia-macmood)]

Removing from a milestone as this work will not be done in 2.5 series.

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

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