The proxy.log hasn't been written to since October 18th

It's likely that pending_dns_record_changes? is true in the DNS orchestration when the host is updated.

The only way I see for that to happen is either for the IPv4 address, IPv6 address or hostname to have changed - though the log doesn't indicate any hostname or v4 change, or for the empty IPv6 field to change from NULL to "" or similar (it's not robustly checking for a change).

If you're willing to add debug to your instance, please edit ~foreman/app/models/concerns/orchestration/dns.rb and change the pending_dns_record_changes? method (circa line 99) to:

def pending_dns_record_changes?
  Rails.logger.info("IPv4: #{old.ip.inspect} to #{ip.inspect}")
  Rails.logger.info("IPv6: #{old.ip6.inspect} to #{ip6.inspect}")
  Rails.logger.info("Hostname: #{old.hostname.inspect} to #{hostname.inspect}")
  old.ip != ip || old.ip6 != ip6 || old.hostname != hostname
end

And restart Foreman (Apache/httpd). You should see three additional log lines when updating the host.

Hi, this has been downgraded to normal but this is an absolute show stopper. Every time we make a change to a puppet entry IT DELETES THE ROUTE53 DNS ENTRIES RELATING TO THE HOST, THIS IS NOT ACCEPTABLE

Just seen your edit after that last post Dominc, will try it

- It's likely that pending_dns_record_changes? is true in the DNS orchestration when the host is updated.

Nope, no change to ip or host name

- The only way I see for that to happen is either for the IPv4 address, IPv6 address or hostname to have changed - though the log doesn't indicate any hostname or v4 change, or for the empty IPv6 field to change from NULL to "" or similar (it's not robustly checking for a change).

Nope definitely not
- If you're willing to add debug to your instance, please edit ~foreman/app/models/concerns/orchestration/dns.rb and change the pending_dns_record_changes? method (circa line 99) to:

def pending_dns_record_changes?
Rails.logger.info("IPv4: #{old.ip.inspect} to #{ip.inspect}")
Rails.logger.info("IPv6: #{old.ip6.inspect} to #{ip6.inspect}")
Rails.logger.info("Hostname: #{old.hostname.inspect} to #{hostname.inspect}")
old.ip != ip || old.ip6 != ip6 || old.hostname != hostname
end

And restart Foreman (Apache/httpd). You should see three additional log lines when updating the host.

Will do

Thanks Dominic. Two questions:
1. Why does a change of ipv6 with no change of ipv4 result in deletion of the DNS entry?
2. Is it possible to configure Foreman to ignore ipv6 altogether?

Paul Smyth wrote:

Thanks Dominic. Two questions:
1. Why does a change of ipv6 with no change of ipv4 result in deletion of the DNS entry?

The two sets of records are bundled together - all forward and reverse records recreated if there's a change.

2. Is it possible to configure Foreman to ignore ipv6 altogether?

No.

So what you're saying that even though the ipv4 address is the same and still exists a change in the ipv6 address justifies removing the DNS entry for the host? Please advise on next steps

You've already filed the bug report, I've offered to fix it by assigning it to myself. It's likely that a fix will be in an upcoming patch release.

Thanks Dominic