Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1805704

Summary:	Single-stack IPv6 Azure clusters on 4.3 assign only IPv4 addresses to worker nodes
Product:	OpenShift Container Platform	Reporter:	Alberto <agarcial>
Component:	Cloud Compute	Assignee:	Alberto <agarcial>
Cloud Compute sub component:	Other Providers	QA Contact:	Jianwei Hou <jhou>
Status:	CLOSED NOTABUG	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aarapov, mgugino, scuppett
Version:	4.3.z
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1805705 (view as bug list)		Environment:
Last Closed:	2020-06-09 14:33:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1803844
Bug Blocks:	1805705

Description Alberto 2020-02-21 12:06:39 UTC

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.

Comment 2 Stephen Cuppett 2020-06-09 13:42:09 UTC

Setting target release to 4.6.0 (active development branch). Where any fixes are required/requested to be backported, clones targeting those z-stream releases will be created.

Comment 3 Alberto 2020-06-09 14:33:17 UTC

this was covered by https://github.com/openshift/cluster-api-provider-azure/pull/107
Refer to https://bugzilla.redhat.com/show_bug.cgi?id=1803844#c6 for more context