Bug 1805705 - Single-stack IPv6 Azure clusters on 4.3 assign only IPv4 addresses to worker nodes
Summary: Single-stack IPv6 Azure clusters on 4.3 assign only IPv4 addresses to worker ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.3.z
Assignee: Brad Ison
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On: 1803844 1805704
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-21 12:08 UTC by Alberto
Modified: 2020-05-18 21:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1805704
Environment:
Last Closed: 2020-05-18 21:03:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alberto 2020-02-21 12:08:53 UTC 
+++ This bug was initially created as a clone of Bug #1805704 +++

This bug was initially created as a copy of Bug #1803844

I am copying this bug because: 



When creating a single-stack IPv6 (or presumably dual-stack) Azure 4.3 cluster using the as-yet-unmerged installer PR https://github.com/openshift/installer/pull/3029 and a hacked 4.3-ipv6 release image (eg as in the comment https://github.com/openshift/installer/pull/3029#issuecomment-586975568), the cluster comes up to a certain point but then fails because the workers have only IPv4 host IPs. (That is, "ip -6 addr" shows only a link-local address on the primary network interface, and the Azure console shows that the node has been assigned an IPv4 address, but not an IPv6 address.) This is in contrast to the master nodes, which get both IPv4 and IPv6 addresses.

Clayton had seen similar behavior in 4.4/master in December, but then it went away.

This blocks 4.3 IPv6 CI.
Note You need to log in before you can comment on or make changes to this bug.