Goal:

• After registration, any content distribution on a "dual stack" network should function identically to any other standard network configuration. All registered systems receive content updates and patches.
  • Note: In this context, "dual stack" refers to a Satellite installation which has simultaneous network endpoints on both IPv4 and IPv6 networks. The Satellite server should be able to connect to and serve content to all devices irrespective of network type. See the parent feature for more context.
• All remaining Satellite components owned by Phoenix content and subscription teams should be verified as functioning on a "dual-stack" network. 
  • Note: This section will function best being QE-lead like previous IPv6 efforts on the Phoenix team.
  • Note: Based on prior experience in "dual-stack" Satlab environments, we do not foresee any failures occurring with content sync after registration.
  • Note: We are currently running Robotello tests once for each network type. While not explicitly "dual-stack," we believe these tests effectively cover "dual-stack" setups.
    • Re-tooling our Robotello runs to feature multiple hosts, capsules, etc, for each individual test will be an enormous effort for little gain. If other Satellite teams choose to go down this route, Phoenix will follow, but the intention is to not make these sweeping changes if they are not deemed critical.
    • SAT-26983 and the related Phoenix IPv6 split testing initiative will cover all content distribution and patching verification for individual network types.
  • We will need to create a few dedicated tests to indicate content sync success on dual-network pre-registered systems.
• Content sync and patching documentation should be modified to inform customers about any necessary considerations or troubleshooting (if applicable). 
• Phoenix work will require completion of SAT-31320 and SAT-30045.