Bug 1451058

Summary:	[3.5] Failed to attach disk to Azure F Instances
Product:	OpenShift Container Platform	Reporter:	hchen
Component:	Storage	Assignee:	hchen
Status:	CLOSED ERRATA	QA Contact:	Wenqi He <wehe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	aos-bugs, bchilds, eparis, jhou
Target Milestone:	---
Target Release:	3.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Azure data disks failed to attach to Azure F instance. Consequence: Pods running on Azure F instance cannot start Fix: Probe attached disks on the nodes to detect Azure disks based on LUN number that is retrieved from Azure metadata service. Result: Disks are detected and Pods can start.	Story Points:	---
Clone Of:	1451039	Environment:
Last Closed:	2017-06-15 18:39:38 UTC	Type:	Bug
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:	1451039
Bug Blocks:

Comment 3 Wenqi He 2017-06-05 08:22:33 UTC

Tested on below version:
openshift v3.5.5.23
kubernetes v1.5.2+43a9be4

F serials vm can attach azure disk and pod could be running:

$ azure vm show --resource-group openshift-qe --name storageocptest.azure.com | grep Size
data:      Size                          :Standard_F4

$ oc get pods
NAME      READY     STATUS    RESTARTS   AGE
azcaro    1/1       Running   0          6m

Comment 5 errata-xmlrpc 2017-06-15 18:39:38 UTC

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.

https://access.redhat.com/errata/RHBA-2017:1425