Hi All
We are using Foreman (Version 1.01)/Puppet to deploy OpenStack. In this
example I have assigned IP 192.168.56.11 to the physical machine with
MAC-address 00:25:90:62:8c:0d. The IP is shown correctly on the Foreman
host details until I start to provison VMs with Openstack.
As soon OpenStack starts to provision VMs, Openstack creates a bridge on
the physical node. The IP assigned to the bridge (in my case 10.0.0.9) is
also reported to Foreman. Unfortunately Foreman replaces the original IP
(192.168.56.11) by the IP of the bridge. After that it's not possible
anymore to rebuild a host in Foreman.
Is this a bug or am I doing something wrong?
Thank you very much!
Fabrice
Hi Fabrice,
It seems like this is an issue in facter -
https://github.com/puppetlabs/facter/blob/1.6.x/lib/facter/ipaddress.rb#L5.
As you can see in that comment, Facter takes the first non-127.* address it
finds when running ifconfig and returns that as the address. Since br100
comes before eth0 alphabetically, that what gets returned.
···
On Wed, Oct 17, 2012 at 4:33 PM, Fabrice wrote:
Hi All
We are using Foreman (Version 1.01)/Puppet to deploy OpenStack. In this
example I have assigned IP 192.168.56.11 to the physical machine with
MAC-address 00:25:90:62:8c:0d. The IP is shown correctly on the Foreman
host details until I start to provison VMs with Openstack.
As soon OpenStack starts to provision VMs, Openstack creates a bridge on
the physical node. The IP assigned to the bridge (in my case 10.0.0.9) is
also reported to Foreman. Unfortunately Foreman replaces the original IP
(192.168.56.11) by the IP of the bridge. After that it’s not possible
anymore to rebuild a host in Foreman.
Is this a bug or am I doing something wrong?
Thank you very much!
Fabrice
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/qBwVabF-YTIJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
Hi Sam,
Thank you for your reply.
I am not that familiar with the Foreman internals. But wouldn't it make
more sense that Foreman takes the information for the "main-ip" from the
DHCP server instead from facter, since this IP was also submitted to the
DHCP server during first host creation and should remain consistent?
Thanks
Fabrice
···
On Wednesday, October 17, 2012 10:55:24 PM UTC+2, Sam Kottler wrote:
>
> Hi Fabrice,
>
> It seems like this is an issue in facter -
> https://github.com/puppetlabs/facter/blob/1.6.x/lib/facter/ipaddress.rb#L5.
> As you can see in that comment, Facter takes the first non-127.* address it
> finds when running ifconfig and returns that as the address. Since br100
> comes before eth0 alphabetically, that what gets returned.
>
> On Wed, Oct 17, 2012 at 4:33 PM, Fabrice <fabrice...@gmail.com > > wrote:
>
>> Hi All
>>
>> We are using Foreman (Version 1.01)/Puppet to deploy OpenStack. In this
>> example I have assigned IP 192.168.56.11 to the physical machine with
>> MAC-address 00:25:90:62:8c:0d. The IP is shown correctly on the Foreman
>> host details until I start to provison VMs with Openstack.
>> As soon OpenStack starts to provision VMs, Openstack creates a bridge on
>> the physical node. The IP assigned to the bridge (in my case 10.0.0.9) is
>> also reported to Foreman. Unfortunately Foreman replaces the original IP
>> (192.168.56.11) by the IP of the bridge. After that it's not possible
>> anymore to rebuild a host in Foreman.
>> Is this a bug or am I doing something wrong?
>>
>> Thank you very much!
>> Fabrice
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/foreman-users/-/qBwVabF-YTIJ.
>>
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> foreman-user...@googlegroups.com .
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
> Hi Sam,
>
> Thank you for your reply.
> I am not that familiar with the Foreman internals. But wouldn't it make
> more sense that Foreman takes the information for the "main-ip" from the
> DHCP server instead from facter, since this IP was also submitted to the
> DHCP server during first host creation and should remain consistent?
>
>
since we had this issue in the past, you can turn ip/mac import from
facter, simply goto more -> settings and search
for ignore_puppet_facts_for_provisioning
Cheers,
Ohad
···
On Wed, Oct 17, 2012 at 11:11 PM, Fabrice Manhart wrote:
Thanks
Fabrice
On Wednesday, October 17, 2012 10:55:24 PM UTC+2, Sam Kottler wrote:
Hi Fabrice,
It seems like this is an issue in facter - https://github.com/puppetlabs/
**facter/blob/1.6.x/lib/facter/*ipaddress.rb#L5https://github.com/puppetlabs/facter/blob/1.6.x/lib/facter/ipaddress.rb#L5.
As you can see in that comment, Facter takes the first non-127. address it
finds when running ifconfig and returns that as the address. Since br100
comes before eth0 alphabetically, that what gets returned.
On Wed, Oct 17, 2012 at 4:33 PM, Fabrice fabrice...@gmail.com wrote:
Hi All
We are using Foreman (Version 1.01)/Puppet to deploy OpenStack. In this
example I have assigned IP 192.168.56.11 to the physical machine with
MAC-address 00:25:90:62:8c:0d. The IP is shown correctly on the Foreman
host details until I start to provison VMs with Openstack.
As soon OpenStack starts to provision VMs, Openstack creates a bridge on
the physical node. The IP assigned to the bridge (in my case 10.0.0.9) is
also reported to Foreman. Unfortunately Foreman replaces the original IP
(192.168.56.11) by the IP of the bridge. After that it’s not possible
anymore to rebuild a host in Foreman.
Is this a bug or am I doing something wrong?
Thank you very much!
Fabrice
–
You received this message because you are subscribed to the Google
Groups “Foreman users” group.
To view this discussion on the web visit https://groups.google.com/d/**
msg/foreman-users/-/qBwVabF-**YTIJhttps://groups.google.com/d/msg/foreman-users/-/qBwVabF-YTIJ
.
To post to this group, send email to forema...@googlegroups.com**.
To unsubscribe from this group, send email to foreman-user…@**
googlegroups.com.
For more options, visit this group at http://groups.google.com/**
group/foreman-users?hl=enhttp://groups.google.com/group/foreman-users?hl=en
.
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/foreman-users/-/l03JxOVdYmQJ.
To post to this group, send email to foreman-users@googlegroups.com.
To unsubscribe from this group, send email to
foreman-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/foreman-users?hl=en.
