hpcloud: index file has no data for cloud

[Curtis Hovey]

For many hours, all hplcloud based ci tests are failing
    test-cloud-hp
    hp-deploy-precise-amd64
    hp-upgrade-precise-amd64
The first test is stable juju testing the health of the clouds. The last two tests check devel juju in the clouds

All fail with this kind of message
    2014-06-11 06:12:36 ERROR juju.cmd supercommand.go:308 index file has no data for cloud {az-3.region-a.geo-1 https://region-a.geo-1.identity.hpcloudsvc.com:35357/v2.0/} not found

I suspect networking issues are the cause or caused by the recent retirement of regions.

[Curtis Hovey (sinzui)]

I think the HP issue is caused by Hp's recent region changes. The environments.yaml need updating. There is a secondary issue that CI doesn't have permission to create security groups in the new regions.

This doesn't explain why canonistact lcy02 tests failed. I can move the canonistack tests to lcy01.

[Curtis Hovey (sinzui)]

Hp rejects
    region: az-3.region-a.geo-1
but
    region: region-a.geo-1
allows bootstrap to start...but bootstrap fails. I cannot ssh into the machine during bootstrap. I suspect a machine could not be provisioned for that region?

[Curtis Hovey (sinzui)]

Antonio updated the account CI uses to have greater network privs, which allowed juju to create the security group, but still no bootstrap.

[Curtis Hovey (sinzui)]

Users are now reporting that Juju doesn't work with HP.

[Curtis Hovey (sinzui)]

I have had to reset up the account for the regions (again) Antonio gave access to networks and security. I re-registered the keys used by CI. Since doing this, the cloud health check is creating instances, but it cannot access them to complete bootstrap. The instances are left behind.

I have tried to bootstrap with the same credentials, but using region: region-a.geo-1. This is the error:

2014-06-11 19:06:26 INFO juju.provider.openstack provider.go:890 started instance "213054d4-2a2d-4142-9286-aa257fc4b86b"
 - 213054d4-2a2d-4142-9286-aa257fc4b86b
Waiting for address
Attempting to connect to 10.0.0.23:22
2014-06-11 19:11:23 ERROR juju.provider.common bootstrap.go:118 bootstrap failed: refreshing addresses: failed to get details for serverId: 213054d4-2a2d-4142-9286-aa257fc4b86b
caused by: failed executing the request https://region-a.geo-1.compute.hpcloudsvc.com/v2/17031369947864/servers/213054d4-2a2d-4142-9286-aa257fc4b86b
caused by: Get https://region-a.geo-1.compute.hpcloudsvc.com/v2/17031369947864/servers/213054d4-2a2d-4142-9286-aa257fc4b86b: read tcp 168.87.243.159:443: connection reset by peer
Stopping instance...
Bootstrap failed, destroying environment
2014-06-11 19:11:28 INFO juju.provider.common destroy.go:15 destroying environment "curtis-hp"
2014-06-11 19:11:32 ERROR juju.cmd supercommand.go:308 refreshing addresses: failed to get details for serverId: 213054d4-2a2d-4142-9286-aa257fc4b86b
caused by: failed executing the request https://region-a.geo-1.compute.hpcloudsvc.com/v2/17031369947864/servers/213054d4-2a2d-4142-9286-aa257fc4b86b
caused by: Get https://region-a.geo-1.compute.hpcloudsvc.com/v2/17031369947864/servers/213054d4-2a2d-4142-9286-aa257fc4b86b: read tcp 168.87.243.159:443: connection reset by peer

[Curtis Hovey (sinzui)]

Bootstrap is failing because the host is unreachable via private IP.

Juju bootstraps on hp when I update the config to use a region without an AZ and always use floating IP
    use-floating-ip: true
    region: region-a.geo-1

While I am indifferent to AZ for testing, there are a finite number of pubic IP addresses to use.

[Curtis Hovey (sinzui)]

We agreed to change the boilerplate for HP to
    use-floating-ip: true
and remove the AZ from the comment about region.