Subnet is nil when we try to add PTR record

Support
#1

Hi ,

We are running Foreman 1.1 + patches and have a smart-proxy pointing to a
Bind DNS Server.

When we create a new host (to our Openstack backend), it adds only the "A"
record while we want both "A" and "PTR".

After digging into the code we found that Foreman is looking for a Subnet
and does not find it. However the subnet looks well configured as well as
its DNS proxy.

Any idea of why the Subnet is always null ?

Thanks,

Michael

#2

> Hi ,
>
> We are running Foreman 1.1 + patches and have a smart-proxy pointing to a
> Bind DNS Server.
>
> When we create a new host (to our Openstack backend), it adds only the "A"
> record while we want both "A" and "PTR".
>
AFAIR, openstack manage the network, and therefore the subnet is owned by
openstack…

Since I assume its a floating IP, I wonder who should be adding the dns
entry… the current code assumes its Openstack… I wonder if thats
assumption is correct.

> After digging into the code we found that Foreman is looking for a Subnet
> and does not find it. However the subnet looks well configured as well as
> its DNS proxy.
>

Yeah, once you select openstack, afair the subnet setting is not visible in
the UI at all (assuming its not relevant to the compute resource).

··· On Wed, Jun 26, 2013 at 8:25 PM, Michael Alves-lobo < alveslobo.michael@gmail.com> wrote:

Any idea of why the Subnet is always null ?

Thanks,

Michael

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

#3

Hi Ohad,

I am working with Michael on the matter. In our case, the IP is not a
floating but a native IP. As we deploy our VMs via Foreman, we use it to
add the DNS entries because we are not really happy with the implementation
of dnsmasq in openstack at the moment.

I think we confused domain and subnet a little bit : indeed you do not
select the subnet but the domain at the creation of an Openstack VM. We'll
have to try to associate the IP/Mask returned by Openstack to a Foreman
subnet in order to create the PTR.

Thank you very much for your enlightenments :slight_smile:

··· On Wednesday, June 26, 2013 9:22:44 PM UTC+2, ohad wrote: > > > > On Wed, Jun 26, 2013 at 8:25 PM, Michael Alves-lobo <alveslob...@gmail.com > > wrote: > >> Hi , >> >> We are running Foreman 1.1 + patches and have a smart-proxy pointing to a >> Bind DNS Server. >> >> When we create a new host (to our Openstack backend), it adds only the >> "A" record while we want both "A" and "PTR". >> > AFAIR, openstack manage the network, and therefore the subnet is owned by > openstack... > > Since I assume its a floating IP, I wonder who should be adding the dns > entry.... the current code assumes its Openstack... I wonder if thats > assumption is correct. > > >> After digging into the code we found that Foreman is looking for a Subnet >> and does not find it. However the subnet looks well configured as well as >> its DNS proxy. >> > > Yeah, once you select openstack, afair the subnet setting is not visible > in the UI at all (assuming its not relevant to the compute resource). > > >> >> Any idea of why the Subnet is always null ? >> >> Thanks, >> >> Michael >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Foreman users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >