Alex Zheng

The whole process is "k8s dynamic provisioning" via linstor-csi. So something must have told linstor-csi that creation failed. Besides, even after the log records volume deletion, `linstor v l` still...

Linstor version 1.4.2 still works with filethin pool and csi, execept for the "Allocated capacity". So what is wrong in 1.5.2 must be things that have been changed since 1.4.2

yes. It is. ``` linstor rd l +----------------------------------------------------------------------------+ | ResourceName | Port | ResourceGroup | State | |============================================================================| | pvc-a1fc73fa-b07a-4de9-8f44-fa5916a28ca5 | | DfltRscGrp | DELETING | +----------------------------------------------------------------------------+ ```

@ghernadi Is it possible to temporarily roll back the related code to that of v1.4.2? We can try fix the "Allocated capacity" another day since it is a non-blocking issue.

yes, it is from `kubectl log` with no manual intervention. The problem starts with v1.4.3 and persists to v1.5.2

hi, @JoelColledge I mapped entire /var/lib/piraeus directory (rw) to the satellite pod, and then `mkdir -vp /var/lib/piraeus/storagepools/DfltStorPool` ``` volumeMounts: - name: var-lib-piraeus mountPath: /var/lib/piraeus volumes: - name: var-lib-piraeus hostPath: path:...

The storage class I used is of a single replica. It is works as expected with v1.4.2. ``` --- apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: piraeus-dflt-raw provisioner: linstor.csi.linbit.com allowVolumeExpansion: true...

My guess is that the `stat` error somehow tricked `linstor-csi` to believe that resource creation has failed. `linstor-csi` then keeps deleting "failed" resource and then retry creating the resource on...

With linstor v1.6.1, layer drbd also reports the same error after a hard reboot. ``` linstor v l +----------------------------------------------------------------------------------------------------------------------------------------------+ | Node | Resource | StoragePool | VolumeNr | MinorNr |...

1. Accessing Linstor API outside of K8S requires the IP of the node on which linstor controller is, for example "standalone linstor cmd client", etc. 2. piraeus-operator is actually using...