bootstrapping private openstack, with --metadata-source fails when instance-type constraint is specified

[Andrew Wilkins]

Helping a user get Juju (1.25.3) bootstrapped on their private OpenStack. We've generated custom image metadata using "juju metadata generate-image". Their default flavor's disk was too small, which caused bootstrap to fail with an error from Mongo. So we tried again with "--constraints instance-type=<their-flavor>" which has a bigger disk. That failed with:

2016-04-08 04:16:19 DEBUG juju.state open.go:306 closed state without error
2016-04-08 04:16:19 ERROR juju.cmd supercommand.go:429 cannot set initial environ constraints: index file has no data for cloud {RegionOne http://172.29.55.5:35357/v2.0} not found
2016-04-08 04:16:19 ERROR juju.cmd supercommand.go:429 failed to bootstrap environment: subprocess encountered error code 1

I think what's happening is that when we set the constraints in state, we validate instance-type against simplestreams metadata. We're trying to get that from the public source, which is failing because that naturally does not have information for the private cloud.

[Andrew Wilkins (axwalk)]

In the end, he served up the metadata on his web server and pointed juju at it with image-metadata-url.

[Anastasia (anastasia-macmood)]

Yes, supported architectures needs to be adjusted to also pull architectures from metadata in state.

There was a plan to get metadata from both public sources and from state and return union of both set eliminating duplicates.

[Anastasia (anastasia-macmood)]

PR against master: https://github.com/juju/juju/pull/5903

[Anastasia (anastasia-macmood)]

This is a duplicate of bug # 1591488 as bootstrapping any cloud with any constraint when using --metadata-source fails.

Feel free to re-open if you feel otherwise.