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

Bug 1589875

Summary: [RFE] allow a parameter to be passed in the StorageClass to target the disk being created in a different Azure resource group
Product: OpenShift Container Platform Reporter: Paul Dwyer <pdwyer>
Component: StorageAssignee: Jan Safranek <jsafrane>
Status: CLOSED ERRATA QA Contact: Wenqi He <wehe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, aos-storage-staff, bbennett, bchilds, fbertina, jokerman, jsafrane, lxia, mmccomas, piqin
Target Milestone: ---   
Target Release: 3.11.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1596319 1596668 1596673 (view as bug list) Environment:
Last Closed: 2018-10-11 07:20:33 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:    
Bug Blocks: 1596319, 1596668, 1596673    

Description Paul Dwyer 2018-06-11 15:04:09 UTC
1. Proposed title of this feature request

allow a parameter to be passed in the StorageClass to target the disk being created in a different Azure resource group

Comment 6 Jan Safranek 2018-06-29 12:03:25 UTC
Wenqi, the test case in polarion needs some updates.

- I indeed picked PR https://github.com/kubernetes/kubernetes/pull/65217 that introduces annotation for resource group, however, I picked also https://github.com/kubernetes/kubernetes/pull/65443 that moves it from annotation to StorageClass.parameters:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: jsafrane
provisioner: kubernetes.io/azure-disk
parameters:
    kind: Managed
    resourceGroup: jsafrane-test


- Please test also provisioning into non-existing resource group ("resourceGroup: non-existing").

Comment 7 Wenqi He 2018-07-02 03:41:17 UTC
(In reply to Jan Safranek from comment #6)
> Wenqi, the test case in polarion needs some updates.
> 
Sure, updated and added a new case. Please tell me if still any issue.

Comment 8 Fabio Bertinatto 2018-07-02 09:06:00 UTC
*** Bug 1595736 has been marked as a duplicate of this bug. ***

Comment 9 Jan Safranek 2018-07-10 10:11:17 UTC
Origin PR: https://github.com/openshift/origin/pull/20268

Comment 10 Jan Safranek 2018-07-30 08:21:16 UTC
The fix was part of the last kubernetes rebase in Origin.

Comment 12 Wenqi He 2018-08-27 07:59:34 UTC
Tested on below version:
openshift v3.11.0-0.22.0
kubernetes v1.11.0+d4cacc0

# 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 pvc
NAME      STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
azpvc     Bound     pvc-3ceda773-a9cd-11e8-902d-000d3a1b9719   1Gi        RWO            externalsc     10m
$ oc describe sc externalsc
Name:                  externalsc
IsDefaultClass:        No
Annotations:           <none>
Provisioner:           kubernetes.io/azure-disk
Parameters:            kind=Managed,resourceGroup=openshift-qe-eastus2
AllowVolumeExpansion:  <unset>
MountOptions:          <none>
ReclaimPolicy:         Delete
VolumeBindingMode:     Immediate
Events:                <none>
$ oc get pods
NAME      READY     STATUS    RESTARTS   AGE
pod       1/1       Running   0          1m
$ oc exec -it pod bash
bash-4.2$ ls /mnt/azure/
bash-4.2$ touch /mnt/azure/wehe
bash-4.2$ ls /mnt/azure/
wehe
bash-4.2$ exit
exit
$ oc exec -it pod bash
bash-4.2$ ls 
anaconda-post.log  dev	hello		 home  lib64	   media  opt	root  sbin  sys  usr
bin		   etc	hello-openshift  lib   lost+found  mnt	  proc	run   srv   tmp  var
bash-4.2$ cp hello /mnt/azure/
bash-4.2$ ./mnt/azure/hello 
Hello OpenShift Storage
bash-4.2$ exit
exit

Comment 14 errata-xmlrpc 2018-10-11 07:20:33 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-2018:2652