Bug 1387226 - Volume provision failed when StorageClass has different zone with master even multizone set to true
Summary: Volume provision failed when StorageClass has different zone with master even...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Jan Safranek
QA Contact: Liang Xia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 11:41 UTC by Liang Xia
Modified: 2016-10-21 08:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-21 08:57:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Liang Xia 2016-10-20 11:41:53 UTC 
Description of problem:
A cluster with master in zone1, node in zone2 (in the same region).
Volume provision failed when using StorageClass with region set to zone2.
The error show:
Failed to provision volume with StorageClass "sc1-kjzgt": kubernetes does not manage zone "us-central1-b"

Version-Release number of selected component (if applicable):
openshift v3.4.0.13
kubernetes v1.4.0+776c994
etcd 3.1.0-alpha.1

How reproducible:
Always

Steps to Reproduce:
1.Set up cluster with 1 master and 2 nodes, 1 master and 1 node in zone1, the other node in zone2.
2.Config master and all node, and restart the service.
# cat /etc/gce/gce.conf 
[global]
multizone=true

# vi /etc/origin/master/master-config.yaml
  apiServerArguments:
    cloud-provider:
    - "gce"
    cloud-config:
    - "/etc/gce/gce.conf"
  controllerArguments:
    cloud-provider:
    - "gce"
    cloud-config:
    - "/etc/gce/gce.conf"

# vi /etc/origin/node/node-config.yaml
kubeletArguments:
  cloud-provider:
  - 'gce'
  cloud-config:
  - '/etc/gce/gce.conf'

3.Create StorageClass with region set to zone2.
4.Create PVC with above StorageClass.
5.Check PV/PVC status.

Actual results:
No PV/volume provisioned.
PVC still pending.

Expected results:
PVC should bound to provisoned PV.

Additional info:
Comment 1 Liang Xia 2016-10-21 08:46:32 UTC 
Tried again today, can not reproduce it(might be caused by some mis-config yesterday).

This can be closed as not a bug now.
Note You need to log in before you can comment on or make changes to this bug.