-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.15.3 GA
-
False
-
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
If PV is specified
spec:
...
system:
...
searchdSpec:
persistentVolumeClaim:
volumeName: xxxxxxxxxx
...
deployment of system-searchd fails with Pending status.
system-searchd-1-deploy 0/1 Completed 0 136m system-searchd-2-7mjkg 1/1 Running 0 127m system-searchd-2-deploy 0/1 Completed 0 127m system-searchd-78d464cc6-8mcq4 0/1 Pending 0 88m
and the following events happened.
2m44s Warning FailedBinding persistentvolumeclaim/system-searchd-manticore volume "xxxxxxxxxx" already bound to a different claim. 87m Normal ScalingReplicaSet deployment/system-searchd Scaled up replica set system-searchd-78d464cc6 to 1 7m55s Warning FailedScheduling pod/system-searchd-78d464cc6-8mcq4 0/6 nodes are available: pod has unbound immediate PersistentVolumeClaims. preemption: 0/6 nodes are available: 6 Preemption is not helpful for scheduling.
