Have you checked
https://lists.ovirt.org/archives/list/users@ovirt.org/message/IMHIBGCFIED32NIOBZCUXIPVAGFNSDJZ/
?
Best Regards,Strahil Nikolov
On Mon, Jan 24, 2022 at 18:45, Sandro Bonazzola wrote:
___
Users mailing list -- users@ovirt.org
To
Il giorno lun 24 gen 2022 alle ore 13:51 Christoph Köhler <
koeh...@luis.uni-hannover.de> ha scritto:
> Hello,
>
> on CentOS Stream the deployment of HE fails with the following message:
>
>
> [ INFO ] TASK [ovirt.ovirt.engine_setup : Gather facts on installed
> packages]
>
> [ INFO ] ok:
The HostedEngine does it automatically, but the option that defines the OVF
refresh interval is not accurate.
Just power it up without that option (cluster in maintenance) and keep it
running for a day.
On the next day power it off and try to power it up via hosted-engine
--vm-start.
Best
Hello,
I did something like that via "virsh edit HostedEngine".
But how is the change written back to the shared storage
("hosted_storage" so it stays permanent for HA Engine ?
I was able to boot up HostedEngine manually via virsh start after
removing the required flag from XML (I first added
On Sun, Oct 27, 2019 at 8:44 AM Michael wrote:
> Hi just just encountered the same error in my lap,
>
> complete new NFS server new ovirt node installation and first deployment
> of Engine
>
>
> [ INFO ] TASK [ovirt.hosted_engine_setup : Activate storage domain]
> [ ERROR ] Error: Fault reason
Hi just just encountered the same error in my lap,
complete new NFS server new ovirt node installation and first deployment of
Engine
[ INFO ] TASK [ovirt.hosted_engine_setup : Activate storage domain]
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[]".
HTTP response code
I have a recording of the entire process, though its ~25 mins long that I can
post. Also after the failure I was able to look at the engine log and have a
recording of that as well.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an
100% clean
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
On Fri, May 17, 2019 at 4:54 PM wrote:
> Simone,
> What would be causing the Cannot aquire host ID??
>
Was that NFS folder absolutely empty?
>
> 2019-05-17 09:03:57,638-04 INFO
> [org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
> (default task-1)
Simone,
What would be causing the Cannot aquire host ID??
2019-05-17 09:03:57,638-04 INFO
[org.ovirt.engine.core.bll.storage.domain.AttachStorageDomainToPoolCommand]
(default task-1) [9126b578-9eac-4517-9e56-960c4751c3d1] Lock Acquired to object
On Fri, May 17, 2019 at 4:10 PM wrote:
> I am having a similar problem - upgrade from 4.2.7 to 4.3.3 ... My Data
> Center would not activate, and I was getting all sorts of errors on the UI.
> I ended up shutting down the existing engine VM using --shutdown-vm ...
> trying to restart it, the
I am having a similar problem - upgrade from 4.2.7 to 4.3.3 ... My Data Center
would not activate, and I was getting all sorts of errors on the UI. I ended up
shutting down the existing engine VM using --shutdown-vm ... trying to restart
it, the console would report that the volume could not be
On Tue, Apr 30, 2019 at 2:55 PM Ralf Schenk wrote:
> Hello,
>
> that is definitely not my problem. Did a complete new deployment (after
> rebooting host)
>
> Before deploying on my storage:
> root@storage-rx:/srv/nfs/ovirt/hosted_storage# ls -al
> total 17
> drwxrwxr-x 2 vdsm vdsm 2 Apr 30 13:53
Hello,
that is definitely not my problem. Did a complete new deployment (after
rebooting host)
Before deploying on my storage:
root@storage-rx:/srv/nfs/ovirt/hosted_storage# ls -al
total 17
drwxrwxr-x 2 vdsm vdsm 2 Apr 30 13:53 .
drwxr-xr-x 8 root root 8 Apr 2 18:02 ..
While deploying in late
On Tue, Apr 30, 2019 at 1:35 PM Ralf Schenk wrote:
> Hello,
>
> I'm deploying HostedEngine to a NFS Storage. HostedEngineLocal ist setup
> and running already. But Step 4 (Moving to hosted_storage Domain on NFS)
> fails. The Host ist Node-NG 4.3.3.1 based.
>
> The intended NFS Domain gets
15 matches
Mail list logo
