Bug 1882630
Summary: | Fstype is changed after deleting pv provisioned by localvolumeset instance | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Chao Yang <chaoyang> |
Component: | Storage | Assignee: | Santosh Pillai <sapillai> |
Storage sub component: | Local Storage Operator | QA Contact: | Chao Yang <chaoyang> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | aos-bugs, hekumar, jelopez, jsafrane, rtalur, sapillai |
Version: | 4.6 | ||
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-24 15:21:14 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1872079, 1885648, 1885700 |
Description
Chao Yang
2020-09-25 08:17:17 UTC
is it happening with LocalVolumeSet only or with LocalVolume as well? The root cause is that `lsblk -o +fstype` info is out of date. Running `udevadm trigger` before `lsblk` refreshes it, but is considered somewhat expensive. We could run it only on the discovery pod (every 5 minutes) because by the time we run into this the localvolume/localvolumeset controller has already finished its job (symlinking). Moving out to 4.7 as per discussion. 1.Create pvc/pod - deviceID: /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_vol0b9b38a379841f8e0 fstype: ext4 model: 'Amazon Elastic Block Store ' path: /dev/nvme2n1 property: NonRotational serial: vol0b9b38a379841f8e0 size: 1073741824 status: state: NotAvailable type: disk vendor: "" discoveredTimeStamp: "2020-10-10T05:42:06Z" 2.Delete pod/pvc - deviceID: /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_vol0b9b38a379841f8e0 fstype: "" model: 'Amazon Elastic Block Store ' path: /dev/nvme2n1 property: NonRotational serial: vol0b9b38a379841f8e0 size: 1073741824 status: state: Available type: disk vendor: "" discoveredTimeStamp: "2020-10-10T05:52:06Z" oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.6.0-0.nightly-2020-10-08-210814 True False 20h Cluster version is 4.6.0-0.nightly-2020-10-08-210814 When pv is in available, blkid will return empty for /dev/nvme2n1, so the fstype is empty also. @hekumar Can we accept this? > When pv is in available, blkid will return empty for /dev/nvme2n1, so the fstype is empty also.
> @hekumar Can we accept this?
That seems fine. Deleting the PVC results in calling wipefs on volume and hence fstype is empty. And although there is a PV on it, currently we don't track unused PVs and mark backing devices as "Unavailable". We could *do* that for local-storage PVs I think, by checking for existing symlinks in `/mnt/local-storage` for the backing device. Is that what you were expecting Chao Yang?
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633 |