Bug 1364975 – Get PVC show capacity is 0 and access mode as empty.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1364975 - Get PVC show capacity is 0 and access mode as empty.

Summary:	Get PVC show capacity is 0 and access mode as empty.

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Storage (Show other bugs)
Sub Component:
Version:	3.3.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jan Safranek
QA Contact:	Liang Xia
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-08 06:04 EDT by Liang Xia
Modified:	2017-03-08 13 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	this bug was not in any public OpenShift release.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2016-09-27 05:42:44 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2016:1933	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.3 Release Advisory	2016-09-27 09:24:36 EDT

Groups: None (edit)

Description Liang Xia 2016-08-08 06:04:45 EDT

Description of problem:
Run comand "oc get pvc", the output show capacity is 0,
and access mode is empty.
While command "oc get pvc -o yaml/json" show the correct value.

This is address in https://trello.com/c/B1K0kBKG

Version-Release number of selected component (if applicable):
openshift v3.3.0.16
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git

How reproducible:
Always

Steps to Reproduce:
1.Create a PVC.
oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/persistent-volumes/nfs/auto/pvc.json
oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/persistent-volumes/misc/pvc.json
2.Run command "oc get pvc"
3.Run command "oc get pvc -o yaml/json"

Actual results:
In step 2, access mode is empty, capacity is 0.
In step 3, correct value show.

Expected results:
Step 2 show the correct value.

Additional info:
# oc get pvc --all-namespaces
NAMESPACE   NAME                 STATUS    VOLUME                                     CAPACITY   ACCESSMODES   AGE
5ajid       dynamic-pvc1-5ajid   Bound     pvc-c11dfda3-5d48-11e6-877a-0e3642f098ed   0                        15m
5ajid       dynamic-pvc2-5ajid   Bound     pvc-c250c257-5d48-11e6-877a-0e3642f098ed   0                        15m
5ajid       dynamic-pvc3-5ajid   Bound     pvc-c374f9dd-5d48-11e6-877a-0e3642f098ed   0                        15m
default     nfsc                 Pending   nfs                                        0                        10s

Comment 1 Jan Safranek 2016-08-08 09:38:20 EDT

Needs https://github.com/kubernetes/kubernetes/pull/29982, backporting shortly

Comment 2 Jan Safranek 2016-08-08 09:47:52 EDT

Filled https://github.com/openshift/origin/pull/10268

Comment 3 Troy Dawson 2016-08-18 16:33:22 EDT

This has been merged into ose and is in OSE v3.3.0.22 or newer.

Comment 5 Liang Xia 2016-08-18 22:10:21 EDT

Verified the issue has been fixed.

# oc get pvc --all-namespaces
NAMESPACE   NAME                 STATUS    VOLUME                                     CAPACITY   ACCESSMODES   AGE
tcblq       dynamic-pvc1-tcblq   Bound     pvc-d427dd9e-65b0-11e6-9c32-0e01a0b3d827   1Gi        RWO           6m
tcblq       dynamic-pvc2-tcblq   Bound pvc-d7edb345-65b0-11e6-9c32-0e01a0b3d827   2Gi        RWX           6m
tcblq       dynamic-pvc3-tcblq   Bound   pvc-da47a9e0-65b0-11e6-9c32-0e01a0b3d827   3Gi        ROX           6m

# openshift version
openshift v3.3.0.22
kubernetes v1.3.0+507d3a7
etcd 2.3.0+git

Comment 7 errata-xmlrpc 2016-09-27 05:42:44 EDT

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-2016:1933

Note You need to log in before you can comment on or make changes to this bug.