Project

General

Profile

Actions

Bug #12768

open

Foreman getting wrong IP from Openstack (Float IP vs Private IP)

Added by Andrew Enstad over 8 years ago. Updated over 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - OpenStack
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I have an environment that that uses Foreman (1.7) with Openstack (Icehouse) as the backend. Occasionally I get the following happening during a new VM provision:

The new VM gets a new IP (Float IP from Openstack), but then it changes to the Openstack Private (non-routeable IP). Then DNS on the Foreman server gets updated with this non-routeable IP, which causes the VM not to be accessible. The work around has been to delete and recreate the VM. So, it looks like it is a race condition with Openstack to provide the correct Float IP to Foreman. Is there any config files to change on either the Foreman server or the Openstack server to make sure this stops happening?

This is on Centos 6.6 servers and building Centos 6.6 VMs.

Actions #1

Updated by Dominic Cleal over 8 years ago

  • Category set to Compute resources - OpenStack
Actions

Also available in: Atom PDF