Closed papanito closed 4 years ago
Ok maybe not an issue at all, just deleted the old config and recreated it again
# kubectl delete KadaluStorage storage-pool-1
kadalustorage.kadalu-operator.storage "storage-pool-1" deleted
# kubectl apply -f storage-config.yml
kadalustorage.kadalu-operator.storage/storage-pool-1 created
There is still another problem as the volume claim is still in state pending
.
container kadalu-operator is not valid for pod server-storage-pool-1-0-node1-0
@papanito Glad the first issue got resolved.
But about still pending issue, what does the pod and pvc describe and logs show?
@amarts I tought to maybe create a separate issue. The log says
[2020-01-05 13:01:49,720] ERROR [glusterfsd - 125:create_and_mount_brick] - Failed to mount export brick fstype=xfs device=/dev/md3 mountdir=/bricks/storage-pool-1/data error=[32] b'' b'mount: /bricks/storage-pool-1/data: wrong fs type, bad option, bad superblock on /dev/md3, missing codepage or helper program, or other error.'
I followed the guidelines but somehow the "storage export pods" are not created. This is my storage config which uses
/dev/md3
.but no pods
pvc thus stay in state
pending
Operator logs
I've first applied a wrong config - 2 nodes configured instead 1. However I corrected it and re-applied again. There is nothing else logged after that
my disk configuration