Bug 1393278 - requirement of ipv6 enabled is missing in documentation.
Summary: requirement of ipv6 enabled is missing in documentation.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Linux_Domain_Identity_Management_Guide
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Aneta Šteflová Petrová
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On: 1404596
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-09 09:11 UTC by Kim Borup
Modified: 2019-12-16 07:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-14 09:35:57 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kim Borup 2016-11-09 09:11:45 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/installing-ipa.html

Section Number and Name: 
0

Describe the issue: 
Not having ip v6 enabled on the system will make the system replica break, and uninstallable. 

Suggestions for improvement: 
Put in that IP v6 is needed on the system, if you dont have it enabled in some form on the interface, it will break the replica installation 

Additional information: 
See internal case for output that happens if ipv6 is not enabled.

Comment 2 Aneta Šteflová Petrová 2016-11-21 14:27:09 UTC
I considered adding the ipv6 requirement to replica installation prerequisites, but in most environments, it will probably be enabled (it's the default in RHEL 7).

I'll probably add a new troubleshooting section for this to Appendix A. Troubleshooting Identity Management.

Comment 6 Aneta Šteflová Petrová 2017-01-02 13:36:00 UTC
To resolve this report, I added a new troubleshooting section: A.1.3. Installing a Server Fails on a System with IPv6 Disabled. Kim reviewed and acked the update.

Comment 9 Aneta Šteflová Petrová 2017-03-14 09:35:57 UTC
The update is now available on the Customer Portal.


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