Force OVH to use ipv4 in shade

OVH instances are getting ipv6 addresses now. This is great except that
the only info on these addresses seems to be in the nova/neutron api and
not via ipv6 router advertisements or config drive metadata. Until we
sort out a programmatic way to configure ipv6 on the instances at boot
lets not attempt to use ipv6 when connecting to OVH instances.

Change-Id: I48e773b9f29fae9a15f6c95fc64831ab0749cc60
This commit is contained in:
Clark Boylan 2017-09-07 10:32:10 -07:00
parent a03e49153d
commit cb51d5b332
3 changed files with 12 additions and 0 deletions

View File

@ -17,6 +17,9 @@ clouds:
force_ipv4: true
ovh:
profile: ovh
# OVH has a weird new ipv6 setup that we can't handle properly
# for now ignore ipv6
force_ipv4: true
regions:
- BHS1
- GRA1

View File

@ -89,6 +89,9 @@ clouds:
- SBG1
- BHS1
profile: ovh
# OVH has a weird new ipv6 setup that we can't handle properly
# for now ignore ipv6
force_ipv4: true
auth:
username: <%= @puppetmaster_clouds['openstackci_ovh_username'] %>
password: <%= @puppetmaster_clouds['openstackci_ovh_password'] %>
@ -143,6 +146,9 @@ clouds:
- SBG1
- BHS1
profile: ovh
# OVH has a weird new ipv6 setup that we can't handle properly
# for now ignore ipv6
force_ipv4: true
auth:
username: <%= @puppetmaster_clouds['openstackjenkins_ovh_username'] %>
password: <%= @puppetmaster_clouds['openstackjenkins_ovh_password'] %>

View File

@ -28,6 +28,9 @@ clouds:
- SBG1
- BHS1
profile: ovh
# OVH has a weird new ipv6 setup that we can't handle properly
# for now ignore ipv6
force_ipv4: true
auth:
username: <%= @puppetmaster_clouds['openstackci_ovh_username'] %>
password: <%= @puppetmaster_clouds['openstackci_ovh_password'] %>