Bug 1872126
| Summary: | Localvolumediscovery detect aws st1 hdd device as NonRotational | ||
|---|---|---|---|
| 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, jsafrane |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.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: | 2020-10-27 16:32: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: | |||
discovery is correctly fetching the results from `lsblk` output in this case. added new HDD(st1) volume nvme1n1 to the node. Results: sh-4.4# cat /sys/block/nvme1n1/queue/rotational 0 sh-4.4# lsblk /dev/nvme1n1 --bytes --pairs --output "NAME,ROTA" NAME="nvme1n1" ROTA="0" sh-4.4# @Chao Can this be closed? Passed on 4.6.0-0.ci-2020-09-21-225645 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196 |
Description of problem: Localvolumediscovery detect aws st1 hdd device as NonRotational Version-Release number of selected component (if applicable): local-storage-operator.4.6.0-202008210209.p0 4.6.0-0.nightly-2020-08-23-214712 How reproducible: Always Steps to Reproduce: 1.Deploy Local-storage-operator 2.Attach hdd device(on aws platform, attach one st1 device) Disk /dev/nvme3n1: 500 GiB, 536870912000 bytes, 1048576000 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes 3.Check localvolumediscoveryresult Vendor: Device ID: /dev/disk/by-id/nvme-Amazon_Elastic_Block_Store_vol0a8412b50eff9fa12 Fstype: Model: Amazon Elastic Block Store Path: /dev/nvme3n1 Property: NonRotational Serial: vol0a8412b50eff9fa12 Size: 536870912k Status: State: Available Type: disk Actual results: st1 device is detected by localvolumediscovery as NonRotational Expected results: st1 device should be detected by localvolumediscovery as Rotational Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info: