The Engine is up but the host stucks in NonResponsive.
The Webinterface stuck in "hanlding non respsonsive host". "Validating"
is green and "Executing" is spinning.
Can anybody help?
I found no errors in the logs under /var/log/ovirt-hosted-engine-ha and
journalclt
regards
gregor
Am 26.11.18
I was able to change the maintenance state in the database to finish the
upgrade with engine-setup.
these are the lines:
select vds_id,ha_global_maintenance from vds_statistics where vds_id =
'706599d5-2dbc-400c-b9da-5b5906de6dbd';
update vds_statistics set ha_global_maintenance = 't' where
Hello,
I upgraded one host from 4.0 to 4.1 without problems. Now I have a
problem with another host, in another network, where the Global
Maintenance mode is not recognized by engine-setup.
Is there a way to force the setup or set the maintenance mode inside the
database?
One problem can be
On Thu, Nov 22, 2018 at 5:51 PM Marco Lorenzo Crociani
wrote:
>
> Hi,
> I opened a bug on gluster because I have reading errors on files on a
> gluster volume:
> https://bugzilla.redhat.com/show_bug.cgi?id=1652548
>
> The files are many of the VMs images of the oVirt DATA storage domain.
> oVirt
Hello,
I've configured LDAP via IPA in oVirt 4.X. It works for locally defined
users in IPA but not those mapped from the AD DC. So I had two questions:
1) Is there a format of the username and password I need to type in for
this to work? Or is retrieving AD DC mapped users not possible
(sorry for double post earlier)
Le 25/11/2018 à 18:19, Nir Soffer a écrit :>
> Hello,
>
> Our cluster use NFS storage (on each node as data, and on a NAS for
> export)
>
>
> Looks like you invented your own hyperconverge solution.
Well, when we looks at the network specs for Gluster
I'm having an odd issue that i find hard to believe could be a bug, and
not some kind of user error, but im at a loss for where else to look.
when booting a linux ISO with QXL SPICE graphics, the boot hangs as soon
as kernel modesetting kicks in. Tried with latest debian, fedora, and
centos.
On Fri, Nov 23, 2018 at 1:01 PM Nathanaël Blanchet wrote:
> Hi,
>
> What are the best pratices about vm snapshots?
>
I think the general guideline is keep only snapshot you need, since every
snapshot has a potential performance cost.
qemu caches some image metadata in memory, so accessing data
On Fri, Nov 23, 2018 at 1:12 PM AG wrote:
> Hello,
>
> Our cluster use NFS storage (on each node as data, and on a NAS for export)
>
Looks like you invented your own hyperconverge solution.
The NFS server on the node will always be accessible on the node, but if it
is
not accessible from other
can we build ovirt selfhost inside ovirt selfhost ?
note that : 1) i have the hardware requirement to the second level of
virtualization .
2) i enable nested virtualization in ovirt node .
but it doesn't work .
___
Users mailing
10 matches
Mail list logo
