Bug 1535270
| Summary: | PV and PVC bound failed event message is not clear | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Storage | Assignee: | Jan Safranek <jsafrane> |
| Status: | CLOSED ERRATA | QA Contact: | Qin Ping <piqin> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.9.0 | CC: | aos-bugs, aos-storage-staff, jsafrane |
| Target Milestone: | --- | ||
| Target Release: | 3.9.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-03-28 14:19:53 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: | |||
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) upstream PR: https://github.com/kubernetes/kubernetes/pull/58522 Origin 3.9 PR: https://github.com/openshift/origin/pull/18284 The PR was merged yesterday. Verified in OCP v3.9.0-0.36.0 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 |
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