Plugins » Ansible

Acually, I comply to all those pre-requisites. I've compared the YAML from a correctly working host (so, one I can rebuild) compared to the failing host and it doesn't appear that there are any differences, however, the UI behaves differently:
- Both hosts have an IPv6 address set in YAML but the failing host doesn't show it in the UI at all
- The IPv6 subnet is correctly showing up for both hosts, however, trying to remove the IPv6 subnet never works, it keeps reverting the removal and so, a subnet is always added.

Tonight I'm going to deep-dive into the code to really try and understand why the UI fails, by this I hope to understand why the rest if failing. Perhaps I've configured something incorrectly somewhere but at this point it's not apparent.

Will keep you guys posted!

Okay, so I managed to "overcome" the problem by doing the following:

  def del_dns_record(type)
    return true if dns_record(type).nil?
    dns_record(type).destroy
  end

So basically the code becomes a bit more forgiving, however, this does not yet gives me the root cause of why the IPv6 was removed to begin with. I long suspected the rebuild config, as it seems to destroy all my DNS records (A & AAAA records AFAIK) but never brings them back. However, the ip6 field is never cleared by that as well. Still looking at what could've done this...

I found why the build_config fails to do as expected: my DNS records are replicated to a master DNS server, however this DNS server did not remove the records if I deleted them in the slave (no notifications were set-up). Because of this, it seems somewhere in code, the records are tested for existence in another server and thus it isn't recreated.

I suspect that my current system-architecture, in which I don't notify my DNS master but let a record expire instead, probably destroyed the ip6 record and so on. Will look into where in the code this DNS resolve is being done instead of a record existence on the local DNS server and will try to fix that as a sub-optimal DNS architecture shouldn't affect the recreation of my DNS records.

So, currently I've manage to overcome the DNS recreate issue by naivly always deleting the DNS records and recreating them.

I've noticed that there are more issues related to this:
https://projects.theforeman.org/issues/13696
https://projects.theforeman.org/issues/2668

Will look if there's a less naive but equally qualitative patch that can be made for this. Again, I haven't managed to recreate the situation that triggered my original issue; so I'll keep focussing on that.

So, I've finally found the root-cause! My ansible callback seems to remove the IPv6 address, so now this should be trivial to fix.
Expect a few pull-requests to be posted in the next few days including tests.

Sorry for the monologue but just wanted to keep everyone in the loop on my research (in case someone had some pointers)