-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Description
Describe the bug
Provision fio application with CSI operator yaml , pod is going into pending state.
Ran the command parted /dev/nvme1n1 unit b print --script -m inside a daemon set pod openebs-device-node and wrt node volume.
$kubectl exec -it openebs-device-node-phwqw -c openebs-device-plugin -n kube-system -- sh
/ # parted /dev/nvme1n1 unit b print --script -m
BYT;
/dev/nvme1n1:107374182400B:nvme:512:512:gpt:Amazon Elastic Block Store:;
1:1048576B:10485759B:9437184B::test-device:msftdata;
Inside node wrt attached volume
root@ip-172-31-40-216 ~]# parted /dev/nvme1n1 unit b print --script -m
BYT;
/dev/nvme1n1:107374182400B:nvme:512:512:gpt:NVMe Device:;
1:1048576B:10485759B:9437184B::test-device:;
Both places output are different.
Expected behavior
# parted /dev/nvme1n1 unit b print --script -m command output should be same without msftdata flag data.
Environment:
NAME="Amazon Linux"
ID="amzn"
ID_LIKE="centos rhel fedora"
Screenshot :
$ kubectl get pod
NAME READY STATUS RESTARTS AGE
fio 0/1 Pending 0 87m
$ kubectl get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
csi-devicepv openebs-device-sc 89m
Metadata
Metadata
Assignees
Labels
No labels


