Description of problem:

IOP containers are not configured for IPv6, Leading to difficulty testing Vulnerabilities in downstream Satellite.  

Currently we only support IPv4 subnets and gateways within core-network.pp

How reproducible: 100%

Is this issue a regression from an earlier version: ?

 No

Steps to Reproduce:

1.Set up Satellite with IOP enabled
2.Try to create a vulnerability and update insights-client 
3.Vulnerabilities do not get updated

Actual behavior:
Vulnerabilities are not being pulled in correctly when running an insights-client update on IPv6 (connection cannot be established) 

Expected behavior:
Vulnerabilities can be created and synced with insights when on IPV6 network

Business Impact / Additional info:

After doing some research, The fix here should be to just add some IPv6 subnets and gateways here. When manually adding them in, IPv6 worked as expected. 

https://github.com/theforeman/puppet-iop/blob/master/manifests/core_network.pp#L14