Bug 1613676

I'd like to add test blocked key work since this is blocking azure disk related testing. Thanks

We picked it up in a bump ~3 weeks ago, it should be in some v1.11.1 build soon  https://github.com/openshift/origin/blame/master/vendor/k8s.io/kubernetes/pkg/cloudprovider/providers/azure/azure_storageaccount.go#L116 https://github.com/openshift/origin/pull/20354

Got an update from upstream, actually the PR I mentioned fixed the azure file creation failure, and there is a new one to fix the unmanaged disk. https://github.com/kubernetes/kubernetes/pull/67236#issuecomment-411985353

PR created: https://github.com/openshift/origin/pull/20662

Tested on below version:
openshift v3.11.0-0.22.0
kubernetes v1.11.0+d4cacc0

The dynamic provision for unmanaged disk is working now
# uname -a
Linux wehe-master-etcd-nfs-1 3.10.0-862.10.2.el7.x86_64 #1 SMP Wed Jul 4 09:41:38 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.5 (Maipo)

#oc get pods azpvcpo --output=yaml
apiVersion: v1
      kind: Pod
      metadata:
        annotations:
          openshift.io/scc: restricted
        creationTimestamp: 2018-08-27T06:35:08Z
        name: azpvcpo
        namespace: dqyh9
        resourceVersion: "24125"
        selfLink: /api/v1/namespaces/dqyh9/pods/azpvcpo
        uid: 577b93b4-a9c3-11e8-bac2-000d3a1b9719
      spec:
        containers:
        - image: aosqe/hello-openshift
          imagePullPolicy: Always
          name: dynamic
          ports:
          - containerPort: 80
            name: http-server
            protocol: TCP
          resources: {}
          securityContext:
            capabilities:
              drop:
              - KILL
              - MKNOD
              - SETGID
              - SETUID
            runAsUser: 1000360000
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          volumeMounts:
          - mountPath: /mnt/azure
            name: dynamic
          - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
            name: default-token-tkk5h
            readOnly: true
        dnsPolicy: ClusterFirst
        imagePullSecrets:
        - name: default-dockercfg-fvp2h
        nodeName: wehe-node-1
        nodeSelector:
          node-role.kubernetes.io/compute: "true"
        priority: 0
        restartPolicy: Always
        schedulerName: default-scheduler
        securityContext:
          fsGroup: 1000360000
          seLinuxOptions:
            level: s0:c19,c9
        serviceAccount: default
        serviceAccountName: default
        terminationGracePeriodSeconds: 30
        volumes:
        - name: dynamic
          persistentVolumeClaim:
            claimName: azpvc
        - name: default-token-tkk5h
          secret:
            defaultMode: 420
            secretName: default-token-tkk5h
      status:
        conditions:
        - lastProbeTime: null
          lastTransitionTime: 2018-08-27T06:35:08Z
          status: "True"
          type: Initialized
        - lastProbeTime: null
          lastTransitionTime: 2018-08-27T06:36:22Z
          status: "True"
          type: Ready
        - lastProbeTime: null
          lastTransitionTime: null
          status: "True"
          type: ContainersReady
        - lastProbeTime: null
          lastTransitionTime: 2018-08-27T06:35:08Z
          status: "True"
          type: PodScheduled
        containerStatuses:
        - containerID: docker://70e80032f360e50fe64ea29f94e7c13f22e65498ad0e974cd7a5e67bd1d7da7d
          image: docker.io/aosqe/hello-openshift:latest
          imageID: docker-pullable://docker.io/aosqe/hello-openshift@sha256:a2d509d3d5164f54a2406287405b2d114f952dca877cc465129f78afa858b31a
          lastState: {}
          name: dynamic
          ready: true
          restartCount: 0
          state:
            running:
              startedAt: 2018-08-27T06:36:21Z
        hostIP: 10.1.2.6
        phase: Running
        podIP: 10.129.0.8
        qosClass: BestEffort
        startTime: 2018-08-27T06:35:08Z

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