You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
[A clear and concise description of what the bug is, and the sequence of operations performed / commands you ran.]
helm install 3.3.1
kubectl get bd -n openebs
NAME NODENAME SIZE CLAIMSTATE STATUS AGE
blockdevice-102253af77d45d264eaac2e2d5ba230b A 2147482582528 Unclaimed Active 28h
blockdevice-8dd07a04e59af42d034d81f4a20516ab B 2147482582528 Unclaimed Inactive 50s
in B
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 4G 0 disk
sr0 11:0 1 492K 0 rom
vda 253:0 0 200G 0 disk
└─vda1 253:1 0 200G 0 part /
vdb 253:16 0 2T 0 disk
└─vdb1 253:17 0 2T 0 part
kubectl get bd -n openebs
NAME NODENAME SIZE CLAIMSTATE STATUS AGE
blockdevice-102253af77d45d264eaac2e2d5ba230b A 2147482582528 Unclaimed Active 29h
blockdevice-a2368ea3ef3a21d2b67d18109f41c6cb B 2147482582528 Unclaimed Inactive 107s
I compare the pod log on between A and B
eventcode=ndm.blockdevice.create.success msg=Created blockdevice object in etcd rname=xxxxx
On A log after success the probe will stop but in B log ndm.blockdevice.deactivate.success or ndm.blockdevice.update.success constantly appear
The output of the following commands will help us better understand what's going on:
[Pasting long output into a GitHub gist or other pastebin is fine.]
What steps did you take and what happened:
[A clear and concise description of what the bug is, and the sequence of operations performed / commands you ran.]
helm install 3.3.1
in B
Follow this https://openebs.io/docs/troubleshooting/ndm I have wipe the disk, restart ndm pod on Node B
but the block device still Inactive
I compare the pod log on between A and B
On A log after success the probe will stop but in B log
ndm.blockdevice.deactivate.success
orndm.blockdevice.update.success
constantly appearndm pod on Node B log openebs-ndm-vl694.log.zip
What did you expect to happen:
The output of the following commands will help us better understand what's going on:
[Pasting long output into a GitHub gist or other pastebin is fine.]
kubectl get pods -n openebs
Environment:
kubectl version
):/etc/os-release
): CentOS Linux 7The text was updated successfully, but these errors were encountered: