Description of problem: Attempting to boot a SNO dualstack spoke cluster from a discovery ISO fails if the mirrored RHCOS image host is IPv6 fails. The cluster acquires in IPv4 address initially upon discovery ISO boot and then tries to retrieve the RHCOS images - It does not acquire an IPv6 address until after the images are retrieved, so it is stuck if the RHCOS image host is ipv6 as the cluster will only have an IPv4 address. Version-Release number of selected component (if applicable): Master assisted service index git_revision: 34c986435c1e85776b2bcb0544eab2e6e77a2c2b Hub and spoke = 4.9.0-rc.0 Disconnected IPv6 hub cluster, IPv6 RHCOS image host, dualstack SNO cluster. How reproducible: 100% Steps to Reproduce: 1. Deploy dualstack SNO cluster using CRDs/kubeapi with Assisted Service 2. Check spoke cluster console Actual results: Console will show spoke cluster failing to reach rhcos live iso url Expected results: Spoke cluster can reach rhcos live iso url Additional info:
@mkowalsk looked into this a bit and it does sound like a valid use case. It looks like we may not be waiting long enough for all the interfaces to get their IP from dhcp before we attempt to download the rhcos image. Maybe something in the initrd that needs to be tweaked.
That's correct. Without investigating deeper it looks to me like a valid use-case.
Looks like it's related to https://bugzilla.redhat.com/show_bug.cgi?id=1931852 and https://bugzilla.redhat.com/show_bug.cgi?id=1990460 https://coreos.slack.com/archives/CUPJTHQ5P/p1633865618150700 So Mat maybe you can close this bug
*** This bug has been marked as a duplicate of bug 1990460 ***