-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.8.z
-
None
-
+
-
Important
-
None
-
Storage Sprint 226, Storage Sprint 227, Storage Sprint 228, Storage Sprint 229, Storage Sprint 230
-
5
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
Description of problem:
The diskmaker-manager pods are not spinning up as the desired state of daemonset/diskmaker-manager is 0 due to which new PV are not getting created.
Version-Release number of selected component (if applicable):
OCP version 4.8 and LSO version local-storage-operator.4.8.0-202206281335.
Steps to Reproduce:
1. Create new localvolume to add new disk.
2. Apply the localvolume.
Actual results:
No new PVs are created
Expected results:
New PV should be created
Additional info:
- The Customer is trying to scale OCS by adding new disk for which new localvolume is created but the diskmaker-manager pods is not spinning due to which new PVs cannot be provisioned.
- The local volumes are provisioned by using the Local Storage Operator.
- Cluster was upgraded from 4.6 to 4.8.
- Checked the localvolume definition, nodeselector is correctly applied.