Bug 39510 - IPv6 addresses not set in ldap object in dualstack setups
IPv6 addresses not set in ldap object in dualstack setups
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: System setup
UCS 4.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-09 14:44 CEST by Bastian Reitemeier
Modified: 2019-01-03 07:14 CET (History)
4 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments
ucs-kvm-create logfile (384.24 KB, text/x-log)
2015-10-09 14:45 CEST, Bastian Reitemeier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bastian Reitemeier univentionstaff 2015-10-09 14:44:46 CEST
Running system-setup on a configuration with both an IPv4 address and an IPv6 address, the network will be set up correctly, but only the IPv4 address will show up in LDAP. As a result of this, there will be no DNS AAAA record for this system, meaning IPv6 only systems will be unable to join. 

Attached is ucs-kvm-create logfile of such a configuration, with a doublestack master and an IPv6 slave, which will be unable to join because there is no AAAA DNS entry for the master.
Comment 1 Bastian Reitemeier univentionstaff 2015-10-09 14:45:26 CEST
Created attachment 7206 [details]
ucs-kvm-create logfile
Comment 2 Philipp Hahn univentionstaff 2015-10-14 08:33:52 CEST
My last request to store all IP addresses was denied: Bug #28562
As multiple IPv6 addresses are the norm, this should be re-evaluated.
Comment 3 Julian Hupertz univentionstaff 2016-03-18 16:17:35 CET

*** This bug has been marked as a duplicate of bug 39920 ***
Comment 4 Janek Walkenhorst univentionstaff 2016-04-06 19:06:29 CEST
(In reply to Julian Hupertz from comment #3)
> *** This bug has been marked as a duplicate of bug 39920 ***
Erroneously, already taken back.
Comment 5 Stefan Gohmann univentionstaff 2019-01-03 07:14:56 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.