Description of problem: Joining a host to a freeipa domain never creates AAAA records if dual stacked, and in a pure IPv6 environment there are many other issues: for example, service checks seem to only check if a name is resolveable on A records. Finally, even once joined, dns record updates don't (seem) to create or update AAAA records on the domain network. 1) ipa-join should be able to handle * v4 only * v4 and v6 (Uploading both A and AAAA records and PTRs) * v6 only 2) service checks should check both A and AAAA and provided *one* of these exists it should validate. In general, I think that freeipa needs more ipv6-only network testing .... Version-Release number of selected component (if applicable): freeipa-3.3.4
This seems somewhat related to https://bugzilla.redhat.com/show_bug.cgi?id=952676 and closed ticket https://fedorahosted.org/freeipa/ticket/909 (closed worksforme though not sure why)
Also related ticket: https://fedorahosted.org/freeipa/ticket/4164 - already scheduled for 4.0. You are definitely right we should do more IPv6-only testing. There were several related efforts and bugfixes: https://fedorahosted.org/freeipa/ticket/2913 https://fedorahosted.org/freeipa/ticket/2695 We occasionally do test and fix IPv6, but sometimes a bug slips in. I will open an upstream ticket for this issue.
Upstream ticket: https://fedorahosted.org/freeipa/ticket/4249
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I'll do an ipv6 only install later to confirm is this issue is fixed now.
Fixed upstream ipa-4-2: https://fedorahosted.org/freeipa/changeset/ff34125bcaa99898859cb8ceefea88a4497959b3 master: https://fedorahosted.org/freeipa/changeset/8ba1392a3903894dda06c733bf37853c6cc3108c
Fixed upstream master: https://fedorahosted.org/freeipa/changeset/9fe67dcf2b6c10ca4eebab1c573d101316f481cd ipa-4-2: https://fedorahosted.org/freeipa/changeset/7924007a83a82674a495afe0e63a4bc85ab2a5ab
Fixed upstream master: https://fedorahosted.org/freeipa/changeset/f160aa3d0a3f8714463c12dac1acc479d1e18a8d ipa-4-2: https://fedorahosted.org/freeipa/changeset/d0c41bd2f2d125fa591b13c602c125a2a112a6c7