bootstrapping private openstack, with --metadata-source fails when instance-type constraint is specified
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
In Progress
|
High
|
Anastasia | ||
1.25 |
Triaged
|
High
|
Unassigned |
Bug Description
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-
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://
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.
description: | updated |
Changed in juju-core: | |
status: | Triaged → New |
Changed in juju-core: | |
status: | New → Triaged |
tags: | added: constraints |
tags: | added: bootstrap |
tags: | added: simplestreams |
Changed in juju-core: | |
assignee: | nobody → Anastasia (anastasia-macmood) |
In the end, he served up the metadata on his web server and pointed juju at it with image-metadata-url.