+++ This bug was initially created as a clone of Bug #1792298 +++
--- Additional comment from Dan Winship on 2020-01-17 08:50:56 EST ---
tested by ipv6 developers/testers. Not QE-able at this time.
Met error when using payload registry.svc.ci.openshift.org/ocp/release:4.3.0-0.nightly-2020-02-05-220314
level=debug msg=" Loading Pull Secret..."
level=debug msg=" Loading Platform..."
level=fatal msg="failed to fetch Terraform Variables: failed to load asset \"Install Config\": invalid \"install-config.yaml\" file: [networking.serviceNetwork: Invalid value: \"fd02::/112\": must use IPv4, networking.clusterNetwork.cidr: Invalid value: \"fd01::/48\": must use IPv4]"t
for now I still cannot setup one ipv6 cluster with 4.3.z and 4.4 nightly build except using KNI branch.
see 4.4 ipv6 bugs https://bugzilla.redhat.com/show_bug.cgi?id=1798878
QE is not going to be able to test any of the IPv6 backports yet. There are other people working on this though.
@Dan thanks the information.
Assigning all 4.3.z IPv6 bugs to Marius Cornea for QA, as they are not yet QA-able in stock release-4.3 builds.
This BZ cannot be verified for now on the 4.3-ipv6 release as the latest build(4.3.0-0.nightly-2020-02-10-055634-ipv6.3) includes a custom cluster-network-operator image according to https://github.com/openshift-kni/ocp-ipv6/blob/master/builds.yaml
this issue can be verified since it's has been merged to latest nightly 4.3 build
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.