Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1076262 - FreeIPA does not handle IPv6 only / dual stack hosts correctly.
Summary: FreeIPA does not handle IPv6 only / dual stack hosts correctly.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: freeipa
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rob Crittenden
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-13 23:57 UTC by William Brown
Modified: 2015-08-19 11:12 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-18 21:10:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description William Brown 2014-03-13 23:57:55 UTC
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

Comment 1 Rob Crittenden 2014-03-14 01:18:07 UTC
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)

Comment 2 Martin Kosek 2014-03-14 07:43:53 UTC
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.

Comment 3 Martin Kosek 2014-03-14 07:50:50 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/4249

Comment 4 Fedora End Of Life 2015-01-09 22:24:21 UTC
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.

Comment 5 William Brown 2015-01-11 00:25:24 UTC
I'll do an ipv6 only install later to confirm is this issue is fixed now.


Note You need to log in before you can comment on or make changes to this bug.