On Tue, Oct 25, 2022 at 7:38 PM Darrell Budic wrote:
>
> Both the initial messages and the additional detail in these vdsm logs show
> that it can’t mount a storage volume. In a multi node environment, it’s
> usually iscsi, gluster, etc, so start by looking at your network and the
> storage
Both the initial messages and the additional detail in these vdsm logs show
that it can’t mount a storage volume. In a multi node environment, it’s usually
iscsi, gluster, etc, so start by looking at your network and the storage
devices and figuring out why it can’t mount them. Comparison to
Hi Tomas,
[root@host1 vdsm]# tail -f vdsm.log
StorageUnavailableError: Unable to get volume size for domain
107f73a2-8c3e-43a7-bf18-ce8ef4be2a19 volume 581f65d2-3db5-4fde-960f-4c4ffe27341e
2022-10-25 16:39:51,785+0800 INFO (periodic/3) [virt.vm]
(vmId='a8d6fcaf-a673-46df-b00a-925a8b9791ef')
On Tue, Oct 25, 2022 at 08:16:56AM -, eug...@knorydev.com wrote:
> Oct 25, 2022, 4:10:01 PM - Failed to connect Host to Storage Pool
>
> Oct 25, 2022, 4:10:01 PM - Host cannot access the Storage
> Domain(s) VM_Data attached to the . Setting Host state to
> Non-Operational.
> Oct 25,
4 matches
Mail list logo
