Description of problem: Could not choose device type as "disk" or "part" when create localvolumeset from web console 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.Try to create localvolumeset from web console 3.Could not choose "disk" or "part" from web console Actual results: Could not choose "disk" or "part" from web console when create localvolumeset Expected results: Should provide the choice device type "disk" or "part" for customer Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
@chaoyang I am not able to understand the issue here. Can you please explain? Are you saying that the partitioned disks are not getting provisioned, even after they matches the filter set on create local volume set view?
Hello Chao, Could you help take a screen snapshot and attach to here? Thanks!
Created attachment 1713410 [details] No device type choice
@negupta I attached one screen snapshot. And this is the yaml file if we create localvolumeset from cli. We can set deviceTypes as part or disk spec: nodeSelector: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - ip-10-0-136-9 deviceInclusionSpec: deviceTypes: - part minSize: 0Ti maxDeviceCount: 1
(In reply to Chao Yang from comment #4) > Created attachment 1713410 [details] > No device type choice Can you check if partitioned devices are picked while providing existing choices - i.e size and disk type? Adding the device type choice was not in plan for 4.6. If above works, we will move this to 4.7
Localvolumeset instance created from web could not provion partitioned device.
@chaoyang Can you please paste the request data that is being sent from UI?
I think Chao is referring to not being able to set the values to either both or one of `disk` or `part` here. It seems hard-coded to just `disk`. deviceTypes: - disk
The field deviceTypes, is an allowlist of types of devices that get picked up for provisioning. Currently valid values are `disk` and `part`. For OCS, we do want to allow the use of partitioned devices.
As Sahina mentioned, adding the device type choice is not in plan for 4.6. Hence, UI will not be able to pass it in 4.6. I would propose to move this bug to 4.7. User can use yaml for these scenarios.
(In reply to Neha Gupta from comment #13) > As Sahina mentioned, adding the device type choice is not in plan for 4.6. > Hence, UI will not be able to pass it in 4.6. I would propose to move this > bug to 4.7. > User can use yaml for these scenarios. But user should have a way to choose disk types of both disk and part if for instance, they only provide the size filter. Is this possible now? If not, can we fix that?
As discussed, there is no such filter on UI for "disk" or for "part" disktype. So if BE allows omitting the "deviceTypes" field, UI can skip it and hence, it will be applied for both device types.
Created a separate Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1878996 to track the provision issue for manually partitioned disk as this Bugzilla refers for the choice of disk and part device type, which is out of scope for 4.6. Moving this to 4.7
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