Bug 1469044
| Summary: | ISCSI plugin fail to mount gluster block volume. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Humble Chirammal <hchiramm> | ||||
| Component: | Storage | Assignee: | Pavel Pospisil <ppospisi> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Jianwei Hou <jhou> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6.1 | CC: | aos-bugs, bchilds | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-07-11 11:30:52 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: | |||||||
| Attachments: |
|
||||||
The iscsi session for this lun is 'active' as in attachment and also can see that, there is a device file exist. The 'diskbypath' is also available in the system. However one thing which I dont get here is, why the device is not shown in 'blkid'? More isolation was done on this today and have found that this is an issue with Gluster Block target. I am closing this bug for now. |
Created attachment 1295778 [details] Outputs. Description of problem: After the block volume is provisioned and once the PVC Is in bound status, if we try to attch that PVC to a pod, it fails with "FS" formatting error. Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: I0710 13:55:45.797788 2790 mount_linux.go:347] `fsck` error fsck from util-linux 2.23.2 Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: fsck.ext2: Invalid argument while trying to open /dev/sdh Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: /dev/sdh: Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: The superblock could not be read or does not describe a correct ext2 Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: filesystem. If the device is valid and it really contains an ext2 Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: filesystem (and not swap or ufs or something else), then the superblock Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: is corrupt, and you might try running e2fsck with an alternate superblock: Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: e2fsck -b 8193 <device> Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: E0710 13:55:45.896898 2790 mount_linux.go:122] Mount failed: exit status 32 Jul 10 13:55:45 dhcp46-248.lab.eng.blr.redhat.com atomic-openshift-node[2790]: Mounting command: mount Version-Release number of selected component (if applicable): [root@dhcp46-248 ~]# oc version oc v3.6.133 kubernetes v1.6.1+5115d708d7 features: Basic-Auth GSSAPI Kerberos SPNEGO How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: The FS formatting should work on the block volume. Expected results: Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info: Check attachment.