Foreman/Openstack DNS issue with Float IPs

Support
#1

When creating a new VM in Foreman, somethings the Openstack Private IP gets
assigned for the VM in DNS, instead of the Public Float IP. This causes
Foreman not to be able to connect to the VM.

This happens only about 5-10% of the time when creating new VMs in Foreman.
I do not see any errors that would point to the issue in the Foreman logs
or Openstack logs.

Foreman is handling the DNS and getting the Public IPs from Openstack.

Has anyone else experienced this issue?

Foreman 1.7.5
Openstack Icehouse and also Openstack Kilo versions (multiple separate
environments that experience the same issues)

#2

From the Foreman side, the only network/subnet defined for these VMs is the
Float IPs. The Openstack Private IPs are not defined in Foreman anywhere.

I can work on getting a job to create multiple VMs as once.

Is there anything that I can look at from the foreman or openstack side
that would point to a race condition?

Any setting that would eliminate this from happening?

··· On Monday, November 9, 2015 at 3:52:00 PM UTC-6, Andrew Enstad wrote: > > > When creating a new VM in Foreman, somethings the Openstack Private IP > gets assigned for the VM in DNS, instead of the Public Float IP. This > causes Foreman not to be able to connect to the VM. > > This happens only about 5-10% of the time when creating new VMs in > Foreman. I do not see any errors that would point to the issue in the > Foreman logs or Openstack logs. > > Foreman is handling the DNS and getting the Public IPs from Openstack. > > Has anyone else experienced this issue? > > Foreman 1.7.5 > Openstack Icehouse and also Openstack Kilo versions (multiple separate > environments that experience the same issues) >
#3

I'm assuming you create hosts choosing a network that has floating IPs?
In any case, if you could find a reproducer, even if it's creating 10
vms with a script (maybe there's a race condition?) that'd help us
debugging ths issue.

··· On 11/09, Andrew Enstad wrote: > > When creating a new VM in Foreman, somethings the Openstack Private IP gets > assigned for the VM in DNS, instead of the Public Float IP. This causes > Foreman not to be able to connect to the VM. > > This happens only about 5-10% of the time when creating new VMs in Foreman. > I do not see any errors that would point to the issue in the Foreman logs > or Openstack logs.

–
Daniel Lobato Garcia

@dLobatog
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato