Hello, After some issues with installing ovirt node version 4.5.3 i went back a version and installed 4.5.2 instead on my hosts.I also install the self hosted engine but for some reason it does not login to the portals when trying with admin user it comes up with invalid username/pass error as i
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 dev
Hello,
Both node version 4.5.3 and 4.5.2 ate installing the master version.
The version of the engine that gets installed is
4.5.4-0.2.master.20221025103923.git936a8fcd09.el8
I do not understand why master version was installed, as I wanted the
stable version.
_
Hi Vladimir,
Done. I sent you the account details in a separate mail.
Thanks,
Sharon
On Tue, Oct 25, 2022 at 10:15 AM Vladimir Talankin
wrote:
> Hello, Sharon,
>
> Yes, you may use my email address as an username and account email.
>
> Regards,
> Vladimir
>
> пн, 24 окт. 2022 г. в 14:02, Sharo
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 any
Hi,
When running hosted-engine --deploy with the el8 ovirt-node, ansible 2.13 uses
python3.9 by default.
But the installation fails two times because of missing netaddr and jmespath
module for python3.9. I suppose the issue is not present in el9 because default
python 3.9 presence.
The workaroun
Downgrade ansible-core to ansible-core-2.12. [1], [2]
[1]
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NIANNOHGJHC6BFVUBRVMBWSDOGNQ6C4C/#7QKZWCMWEQ2UTJX4WN6MZYHK4FINL5MT
[2]
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/JI72US3JIOXBWTMTVVGDLVAZV7UJXBYF/#JI72US3JIOXBW
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') Req
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, 2022,
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, 2022, 4:10:01 PM - Host reports about one of the Active
Storage Domains as Problemati
10 matches
Mail list logo