Bug 1462551 - Dynamically created Azure blob container is open to public
Summary: Dynamically created Azure blob container is open to public
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: hchen
QA Contact: Wenqi He
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-18 19:35 UTC by hchen
Modified: 2017-08-16 19:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-10 05:28:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 09:02:50 UTC

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
Note You need to log in before you can comment on or make changes to this bug.