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

Bug 1462551

Summary:	Dynamically created Azure blob container is open to public
Product:	OpenShift Container Platform	Reporter:	hchen
Component:	Storage	Assignee:	hchen
Status:	CLOSED ERRATA	QA Contact:	Wenqi He <wehe>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.6.0	CC:	aos-bugs, eparis, smunilla
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-10 05:28:09 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:

Description hchen 2017-06-18 19:35:10 UTC

Description of problem:

As documented at https://github.com/kubernetes/kubernetes/pull/47605#issuecomment-309159093



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

How reproducible:
If the storage account doesn't have vhds container, dynamically created vhds are worldly visible.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Dynamically created vhds are privately accessible.

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 4 Wenqi He 2017-06-29 08:10:57 UTC

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

Now the container of vhds is private.

Comment 6 errata-xmlrpc 2017-08-10 05:28:09 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/RHEA-2017:1716