I've seen that the IP of the new nodes changes to 127.0.0.1 for all the
nodes under foreman.
I don't rely on that field that much, but the problem I'm having is that if
I try to delete a node, it will try to delete the node with IP 127.0.0.1,
causing a failure on the logs and the inability to remove such node.
The log says this:
Nov 13 12:42:33 puppet named[969]: client 127.0.0.1#12889: signer
"rndc-key" denied
Nov 13 12:42:33 puppet named[969]: client 127.0.0.1#12889: update
'1.0.0.127.in-addr.arpa/IN' denied
Thanks,
IB
I found the solution to deleting the nodes after they have been reassigned
the 127.0.0.1 network => Edit the node, set it to unmanaged => submit and
then delete the node.
BTW, I still don't know what the cause of the change in the IP address in
1.7 is. I'm currently installing a new server in CentOS 6 and in C7 to see
if I can replicate the problem and post more information on the issue.
IB
ยทยทยท
On Thursday, November 13, 2014 12:47:21 PM UTC-5, Ignacio Bravo wrote:
>
> I've seen that the IP of the new nodes changes to 127.0.0.1 for all the
> nodes under foreman.
>
> I don't rely on that field that much, but the problem I'm having is that
> if I try to delete a node, it will try to delete the node with IP
> 127.0.0.1, causing a failure on the logs and the inability to remove such
> node.
>
> The log says this:
>
> Nov 13 12:42:33 puppet named[969]: client 127.0.0.1#12889: signer
> "rndc-key" denied
> Nov 13 12:42:33 puppet named[969]: client 127.0.0.1#12889: update
> '1.0.0.127.in-addr.arpa/IN' denied
>
>
> Thanks,
> IB
>
>