I believe I ran `hosted-engine --deploy` on ovirt-1 to see if there was an
option to reenroll that way, but when it prompted and asked if it was really
what I wanted to do I ctrl-D or said no and it ran something anyways, so I
ctrl-C out of it and maybe that is what messed up vdsm on that node.
When you say "As a side note because the engine doesn't make this very clear in
the
UI: If you want to change the network used for the various roles,
(storage, VM, console, management, default gateway, migration) you do
so at the cluster level. (Main menu-> Compute -> Clusters -> Cluster
name ->
Hello,
Network configuration for an ovirt host is managed by VDSM. If you try
to make changes manually, such as through calling nmcli or manually
editing the network scripts via an ssh session on each host, VDSM will
just reset everything back to the configuration it had before. (It's on
a timer,
Hello All,
So due to some issues with provisioning new networks in our lab, I have to use
a different VLAN in for my ovirt cluster.
Cluster -> 3 Hosts (Hyperconverged)
What I want to do is essentially change the Ovirtmgmt interface to another vlan
but also change the IP Schemes, I wont be
Disregard my previous e-mail... it's for another topic
On Sat, Feb 19, 2022 at 2:11, Strahil Nikolov wrote:
Based on this one, it looks like thereis a way to init via sanlock
(https://lists.ovirt.org/pipermail/users/2016-June/073652.html)
It's something like this:
sanlock direct init -s
Based on this one, it looks like thereis a way to init via sanlock
(https://lists.ovirt.org/pipermail/users/2016-June/073652.html)
It's something like this:
sanlock direct init -s
:0:/rhev/mnt/glusterSD/_/sd_uuid/dom_md/ids:0sd_uuid
should be the directory (gluster) in
Unfortunately ovirt-ha-broker & ovirt-ha-agent are just in continual restart
loops on ovirt-1 & ovirt-3 (ovirt-engine is currently on ovirt-3).
The output for broker.log:
MainThread::ERROR::2022-02-18
22:08:58,101::broker::72::ovirt_hosted_engine_ha.broker.broker.Broker::(run)
Trying to
ovirt-2 is 'state=GlobalMaintenance' , but the other 2 nodes is uknown.Try to
start ovirt-ha-broker & ovirt-ha-agent
Also, you may try to move the hosted-engine to ovirt-2 and try again
Best Regards,Strahil Nikolov
On Fri, Feb 18, 2022 at 21:48, Joseph Gelinas wrote: I
may be in
I may be in maintenance mode, I did try to set it in the beginning of this, but
engine-setup doesn't see it. At this point my nodes say they can't connect to
the HA daemon, or have stale data.
[root@ovirt-1 ~]# hosted-engine --set-maintenance --mode=global
Cannot connect to the HA daemon,
To set the engine into maintenance mode you can ssh to any Hypervisor and
run:'hosted-engine --set-maintenance --mode=global'wait 1 minute and run
'hosted-engine --vm-status' to validate.
Best Regards,Strahil Nikolov
On Fri, Feb 18, 2022 at 19:03, Joseph Gelinas wrote: Hi,
The
Hi,
The certificates on our oVirt stack recently expired, while all the VMs are
still up, I can't put the cluster into global maintenance via ovirt-engine, or
do anything via ovirt-engine for that matter. Just get event logs about cert
validity.
VDSM ovirt-1.x.com command Get Host
11 matches
Mail list logo
