Bug 1451039 – [3.6] Failed to attach disk to Azure F Instances

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1451039 - [3.6] Failed to attach disk to Azure F Instances

Summary:	[3.6] Failed to attach disk to Azure F Instances

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Storage (Show other bugs)
Sub Component:
Version:	3.6.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	hchen
QA Contact:	Wenqi He
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1451058
	Show dependency tree / graph

Reported:	2017-05-15 11:49 EDT by hchen
Modified:	2017-08-16 15 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Clones:	1451058 (view as bug list)
Environment:
Last Closed:	2017-08-10 01:24:06 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2017:1716	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.6 RPM Release Advisory	2017-08-10 05:02:50 EDT

Groups: None (edit)

Description hchen 2017-05-15 11:49:08 EDT

Description of problem:

Azure F instances 

Version-Release number of selected component (if applicable):
3.5 and higher

How reproducible:

Always

Steps to Reproduce:
1. create a vhd and use it as azure disk volume
2. create a pod that uses the azure disk volume and make sure the pod is scheduled to an Azure F instance

Actual results:
The pod cannot be created because the disk is not attached to the Azure instance


Expected results:

The volume is attached and Pod is created.

Additional info:


Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 3 Wenqi He 2017-06-05 04:29:54 EDT

Tested on below version:
openshift v3.6.86
kubernetes v1.6.1+5115d708d7

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

$ azure vm show --resource-group openshift-qe --name weheocptest.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-08-10 01:24:06 EDT

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/RHEA-2017:1716

Note You need to log in before you can comment on or make changes to this bug.