Can not place PV with two requisite nodes and replicas on same nodes #195
Comments
^^^^ That's not the storage class from above |
|
sorry, here it is: allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
annotations:
storageclass.kubernetes.io/is-default-class: "true"
name: linstor-data-r2
parameters:
linstor.csi.linbit.com/allowRemoteVolumeAccess: "false"
linstor.csi.linbit.com/placementCount: "2"
linstor.csi.linbit.com/replicasOnSame: Aux/zone
linstor.csi.linbit.com/storagePool: data
property.linstor.csi.linbit.com/DrbdOptions/Net/rr-conflict: retry-connect
property.linstor.csi.linbit.com/DrbdOptions/Resource/on-no-data-accessible: suspend-io
property.linstor.csi.linbit.com/DrbdOptions/Resource/on-suspended-primary-outdated: force-secondary
property.linstor.csi.linbit.com/DrbdOptions/auto-quorum: suspend-io
provisioner: linstor.csi.linbit.com
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumerThe vm itself has nodeSelector assigned: nodeSelector:
zone: bThe error is the same, even if I cordon |
|
The provisioning works fine when pvc runs on apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: foo
namespace: tfprod
spec:
accessModes:
- ReadWriteMany
resources:
requests:
storage: "53687091200"
storageClassName: linstor-data-r2
volumeMode: BlockPVC has selected node annotation: this works the same way for trace log: any ideas? |
|
@WanzenBug I see that it tries to place two volumes in one time, can't it be affected by the fact that |
|
no, single volume also has the problem: |
This was referenced Apr 27, 2023
4 tasks
|
Do all nodes have the |
|
yeah, they are: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @WanzenBug I'm bit confused about requisite nodes. And why their number can be more than one:
Here is my storageclass:
Then I try to provision PVC for KubeVirt using CDI with
HonorWaitForFirstConsumerfeature enabled,I see that it is created pvc, and the following error:
Despite the fact the PVC has already assigned
volume.kubernetes.io/selected-node: b-hv-3why it tries to addc-hv-5into node list?The text was updated successfully, but these errors were encountered: