7 p.m.
In the web ui I get an error about every hour: VDSM command SetVolumeDescriptionVDS
failed: Volume does not exist: (u'e3f79840-8355-45b0-ad2b-440c877be637',)
I looked in storage and disks and this disk does not exist. Its more of an annoyance than
a problem but if there is way to get rid of this error I would like to know.
My research says I can install vdsm-tools and vdsm-cli but vdsm-cli is not available and I
really don;t want to install anything until I know it's what I need.
Is there a vdsm command to purge a missing disk so this error won't show up?
Thanks in advance.
Eric
9:50 p.m.
On Mon, Jun 29, 2020 at 7:02 PM <eevans(a)digitaldatatechs.com> wrote:
In the web ui I get an error about every hour: VDSM command SetVolumeDescriptionVDS
failed: Volume does not exist: (u'e3f79840-8355-45b0-ad2b-440c877be637',)
I looked in storage and disks and this disk does not exist. Its more of an annoyance than
a problem but if there is way to get rid of this error I would like to know.
My research says I can install vdsm-tools and vdsm-cli but vdsm-cli is not available and
I really don;t want to install anything until I know it's what I need.
vdsm-cli was an old command line tool in historic versions. It was replaced
by vdsm-client.
vdsm-tool is always installed, it is part of vdsm package.
Is there a vdsm command to purge a missing disk so this error
won't show up?
Thanks in advance.
Which version are you running (engine, vdsm)?
Which storage domain (nfs, iscsi, fc, gluster, local?)
Engine updates the OVF_STORE volumes every hour. These volumes are
created by engine
when you create a storage domain and update every hour or when the
storage domain is
deactivated.
The error you get may be a bug in vdsm, failing to update the volume
or find the volume,
or a real issue if the volume is missing.
If there is a bug in vdsm, it may be fixed by restarting vdsm. Do you
experience the
same error after that?
Please file a bug for this and attach all engine and vdsm log that
contain this volume
(e3f79840-8355-45b0-ad2b-440c877be637). The logs may explain why the volume
is missing or the operation fails.
If you run 4.4, attaching output of this may help:
$ vdsm-client StorageDomain dump sd_id=stoage-domain-uuid full=1
If you run 4.3, output of this tool may help:
vdsm-tool dump-volume-chains -o json storage-domain-uuid
Nir
1607
days inactive
1607
days old
1 comments
2 participants
participants (2)
-
eevans＠digitaldatatechs.com -
Nir Soffer