Suckful user experience: warnings are not shown unless -v is specified

David Cheney david.cheney at canonical.com
Wed Jul 10 06:19:13 UTC 2013


lucky(~/src/launchpad.net/juju-core/environs/ec2) % juju bootstrap
error: cannot start bootstrap instance: no "precise" images in
ap-southeast-2 with arches [amd64 i386]

# oh dear, what could be wrong ...

lucky(~/src/launchpad.net/juju-core/environs/ec2) % juju bootstrap -v
2013-07-10 06:16:56 INFO juju ec2.go:128 environs/ec2: opening environment
"ap-southeast-2"
2013-07-10 06:16:56 INFO juju ec2.go:238 environs/ec2: bootstrapping
environment "ap-southeast-2"
2013-07-10 06:17:05 INFO juju tools.go:25 environs: reading tools with
major version 1
2013-07-10 06:17:05 INFO juju tools.go:29 environs: falling back to public
bucket
2013-07-10 06:17:06 INFO juju tools.go:52 environs: filtering tools by
series: precise
2013-07-10 06:17:06 INFO juju tools.go:75 environs: picked newest version:
1.11.2
2013-07-10 06:17:07 WARNING juju.environs.ec2 image.go:43 no matching image
meta data for constraints: &{ap-southeast-2 precise [amd64 i386]
cpu-power=100 0xc2102f5fb0}
2013-07-10 06:17:07 ERROR juju supercommand.go:234 command failed: cannot
start bootstrap instance: no "precise" images in ap-southeast-2 with arches
[amd64 i386]
error: cannot start bootstrap instance: no "precise" images in
ap-southeast-2 with arches [amd64 i386]

# oh, if I add the magic flag, it tells me that something went wrong with
simplestreams and no images that matched my constraint were returned (along
with some stuff I don't care about)

Can I get a +1 for lowering the cutoff threshold so that warnings are
printed without having to pass -v (debug)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20130710/a6e2e636/attachment.html>


More information about the Juju-dev mailing list