Hide Forgot
Description of problem: The #heketi-cli node info <id>" returns "Error: Id not found" whenever server is busy at processing other request. [root@client ~]# heketi-cli node info 31fdf6007a7d4a8d61fa917916e51cb0 Error: Id not found Version-Release number of selected component (if applicable): heketi-cli 3.0.0 Steps to Reproduce: *) In one terminal issue heketi-cli command to create a volume. [root@client ~]# heketi-cli volume create --size=4 *) as soon as above command is issued, in second terminal, execute: [root@client ~]# heketi-cli node info 31fdf6007a7d4a8d61fa917916e51cb0 Error: Id not found [root@client ~]# heketi-cli node info 31fdf6007a7d4a8d61fa917916e51cb0 Error: Id not found [root@client ~]# heketi-cli node info 31fdf6007a7d4a8d61fa917916e51cb0 Error: Id not found Once the first command ( volume create) is executed successfully or when execution is completed, the node info will start responding properly. [root@client ~]# heketi-cli node info 31fdf6007a7d4a8d61fa917916e51cb0 Node Id: 31fdf6007a7d4a8d61fa917916e51cb0 State: online Cluster Id: 968e0e194d9b5de3d9a23dbf3f5e6c96 Zone: 1 Management Hostname: 192.168.68.4 Storage Hostname: 192.168.68.4 Devices: Id:06c57dae3b19bf40b8652f7b68f862f7 Name:/dev/vdg State:online Size (GiB):699 Used (GiB):4 Free (GiB):695 Id:1096bf1e0a61e87944025a206e06b34d Name:/dev/vdf State:online Size (GiB):49 Used (GiB):32 Free (GiB):17 Id:6bc65b15ec557aaeb01f9a349246d840 Name:/dev/vdc State:online Size (GiB):49 Used (GiB):0 Free (GiB):49 Id:d21172b7fdb37b3cec95a6ae0ccf3140 Name:/dev/vdd State:online Size (GiB):49 Used (GiB):8 Free (GiB):41 Id:d7b5a06be19ac7c4ae7ca6d92728f49f Name:/dev/vde State:online Size (GiB):49 Used (GiB):0 Free (GiB):49 Actual results: Getting "Id not found" error. Expected results: The node info should work without issues. Giving "Id not found" error is NOT acceptable at all or its completely wrong. Additional info: The commands like "volume info"..etc work without issues.
Ref # https://github.com/heketi/heketi/blob/master/apps/glusterfs/app_node.go#L170
Looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1346621 . Please do confirm.
(In reply to Prasanth from comment #3) > Looks like a duplicate of > https://bugzilla.redhat.com/show_bug.cgi?id=1346621 . Please do confirm. Thanks Prasnath. At glance, this is duplicate. Because toplogy info internally call 'node info' and it could be causing the same behaviour.
(In reply to Humble Chirammal from comment #4) > (In reply to Prasanth from comment #3) > > Looks like a duplicate of > > https://bugzilla.redhat.com/show_bug.cgi?id=1346621 . Please do confirm. > > Thanks Prasnath. At glance, this is duplicate. Because toplogy info > internally call 'node info' and it could be causing the same behaviour. Closing this as duplicate *** This bug has been marked as a duplicate of bug 1346621 ***