Description of problem:

IPv6 support in Satellite/Capsule 6.8. Not to be construed as Full IPv6 support as referenced in RFE BZ https://bugzilla.redhat.com/show_bug.cgi?id=1200095

Version-Release number of selected component (if applicable):

6.8.0


How reproducible:

N/A

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Based on following Use Cases as follows:

- Only IPv6 stack. No dual stack.
- Does not include compute resources.

- IPv6 - Install Satellite Server/Capsule over IPv6 Network
   ==========
   - As a Satellite Admin I need support for IPv6 in the following use cases:
   In Scope:
   - I can install a satellite server with only IPv6 networks.
   - I can install a capsule server with only IPv6 networks.

- IPv6 - Content Management / Remote Execution
   ==========
   - As a Satellite Admin I need support for IPv6 in the following use cases:
   In Scope
   - I can use REX through the capsule to install packages and errata to an IPV6 machine (ansible only)
   - Package state and errata are reported back to the satellite via an IPv6 network
   - All content should be mirrored on capsules over an IPV6 network.

- IPv6 - Container Management
   ==========
   - As a Satellite Admin I need support for IPv6 in the following use cases:
   In Scope
   - Satellite needs to support container uploads and container tools pulling images over an IPv6 network

- IPV6 - Provisioning
   =========
   - As a Satellite User, I can provision a physical machine using an image and UEFI-Netboot with a SLAAC (Stateless Address Auto Configuration) address.
   In Scope
   - Need to support SLAAC provisioning (StateLess Address Auto Configuration)
   - Need to support UEFI Netboot provisioning
   - Using Image based builds
   - Physical devices