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:
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
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