Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1535270 - PV and PVC bound failed event message is not clear
PV and PVC bound failed event message is not clear
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage (Show other bugs)
3.9.0
Unspecified Unspecified
unspecified Severity low
: ---
: 3.9.0
Assigned To: Jan Safranek
Qin Ping
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-01-16 20:40 EST by Qin Ping
Modified: 2018-03-28 10:20 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:19:53 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 10:20 EDT

  None (edit)
Description Qin Ping 2018-01-16 20:40:30 EST
Description of problem:
Block volumeMode PVC prebound a Filesystem volumeMode PV, bound failed as expected, but event message is not clear.

Version-Release number of selected component (if applicable):
oc v3.9.0-0.20.0
openshift v3.9.0-0.20.0
kubernetes v1.9.1+a0ce1bc657


How reproducible:
Always

Steps to Reproduce:
1. Create a Filesystem volumeMode PV
2. Create a Block volumeMode PVC prebound the PV created above
3. Check the PVC and PV

Actual results:
PVC is not bound to PV, but event message is not correct.
Warning  VolumeMismatch  5s    persistentvolume-controller  Volume's size is smaller than requested or volume's class does not match with claim

Expected results:
Volume's volumeMode does not match with claim?

Additional info:
# cat pv-fs.yaml 
apiVersion: v1
kind: PersistentVolume
metadata:
  name: fs-pv
spec:
  capacity:
    storage: 5Gi
  accessModes:
    - ReadWriteOnce
  volumeMode: Filesystem
  persistentVolumeReclaimPolicy: Retain
  fc:
    targetWWNs: ["500a0981891b8dc5", "500a0981991b8dc5"]
    lun: 2
    readOnly: false

# cat pvc-block.json 
{
    "apiVersion": "v1",
    "kind": "PersistentVolumeClaim",
    "metadata": {
        "name": "claim-block"
    },
    "spec": {
        "accessModes": [ "ReadWriteOnce" ],
        "volumeName" : "fs-pv",
        "volumeMode" : "Block",
        "resources": {
            "requests": {
                "storage": "5Gi"
            }
        }
    }
}

# oc describe pvc
Name:          claim-block
Namespace:     piqin
StorageClass:  
Status:        Pending
Volume:        fs-pv
Labels:        <none>
Annotations:   <none>
Finalizers:    []
Capacity:      0
Access Modes:  
VolumeMode:    Block
Events:
  Type     Reason          Age   From                         Message
  ----     ------          ----  ----                         -------
  Warning  VolumeMismatch  5s    persistentvolume-controller  Volume's size is smaller than requested or volume's class does not match with claim
Comment 1 Jan Safranek 2018-01-19 09:39:45 EST
I agree that the message is confusing, I'll change it to:
"Cannot bind to requested volume "fs-pv": %s", where %s is one of:
- "requested PV is too small"
- "storageClasseNames do not match"
- "incompatible volumeMode"
- "error checking volumeMode: api defaulting for volumeMode failed" (this should not ever happen)
Comment 2 Jan Safranek 2018-01-19 09:47:06 EST
upstream PR: https://github.com/kubernetes/kubernetes/pull/58522
Comment 3 Jan Safranek 2018-01-25 05:24:13 EST
Origin 3.9 PR: https://github.com/openshift/origin/pull/18284
Comment 4 Jan Safranek 2018-02-01 06:12:26 EST
The PR was merged yesterday.
Comment 6 Qin Ping 2018-02-05 00:25:23 EST
Verified in OCP v3.9.0-0.36.0
Comment 9 errata-xmlrpc 2018-03-28 10:19:53 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-2018:0489

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