Why are the errors "not a valid name for this device" showing in VDSM logs?

Issue

• In a RHHI setup, the following errors are observed in the vdsm log files, at /var/log/vdsm/vdsm.log, every few hours:

  2020-06-23 08:44:46,430+0200 ERROR (jsonrpc/0)    [jsonrpc.JsonRpcServer] Internal server error (__init__:350)
  Traceback (most recent call last):
    File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request
  res = method(**params)
    File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 194, in _dynamicMethod
      result = fn(*methodArgs)
    File "/usr/lib/python2.7/site-packages/vdsm/gluster/apiwrapper.py", line 84, in storageDevicesList
      return self._gluster.storageDevicesList()
    File "/usr/lib/python2.7/site-packages/vdsm/gluster/api.py", line 93,   in wrapper
      rv = func(*args, **kwargs)
    File "/usr/lib/python2.7/site-packages/vdsm/gluster/api.py", line 519,  in storageDevicesList
      status = self.svdsmProxy.glusterStorageDevicesList()
    File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__
      return callMethod()
    File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda>
      **kwargs)
    File "<string>", line 2, in glusterStorageDevicesList
    File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod
      raise convert_to_error(kind, result)
         ValueError:     gluster_thinpool_gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3 is not a valid name for this device
  

• They point to thin pool gluster_thinpool_gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3 as not having a valid name. However, checking the status of this thin pool , using for example an lvs -acommand, it's looks healthy:

  3600508b1001c0ccc07ddd1090e3147f4p3                                                                                              253:3    0 832.2G  0 part
      ├─gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3-  gluster_thinpool_gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3_t meta   253:9    0     3G  0 lvm
      │ └─gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3-gluster_thinpool_gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3-tpool 253:11   0 826.2G  0 lvm
      │   ├─gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3-gluster_thinpool_gluster_vg_3600508b1001c0ccc07ddd1090e3147f4p3
  

• Why are these messages seen? How to prevent them from occurring?