Description of problem: kubernetes.io/hostname values are larger than filter when create localvolumeset from webconsole Version-Release number of selected component (if applicable): local-storage-operator.4.9.0-202108130204 4.9.0-0.nightly-2021-08-14-065522 How reproducible: Always Steps to Reproduce: 1.Deploy local storage operator 2.Create localvolumeset cr from web console 3.Filter Disk by --> Disks on all nodes(3 nodes) 4. oc get localvolumeset lvstest -o json | jq .spec { "deviceInclusionSpec": { "deviceTypes": [ "disk", "part" ], "minSize": "1Gi" }, "nodeSelector": { "nodeSelectorTerms": [ { "matchExpressions": [ { "key": "kubernetes.io/hostname", "operator": "In", "values": [ "ip-10-0-135-13.us-east-2.compute.internal", "ip-10-0-151-9.us-east-2.compute.internal", "ip-10-0-167-119.us-east-2.compute.internal", "ip-10-0-172-71.us-east-2.compute.internal", "ip-10-0-198-53.us-east-2.compute.internal", "ip-10-0-210-2.us-east-2.compute.internal" ] } ] } ] }, "storageClassName": "lvstest", "volumeMode": "Block" } Actual results: All nodes including master and workers are chosen in the localvolumeset cr. Expected results: Only 3 workers are included in the localvolumeset cr. Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
Passed with oc get csv NAME DISPLAY VERSION REPLACES PHASE local-storage-operator.4.10.0-202110052245 Local Storage 4.10.0-202110052245 Succeeded
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.10.3 security 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-2022:0056