After an update 2 days ago we no longer able to log into the oVirt console.
The certificate was expiring, so we ran the system update and the ovirt-engine
update as well. It went fine and re-issued (upgraded) certificates. After the
work was done, we no longer able to log into the WEB UI. The err
apper/3600c0ff00019eb74f1efa95e0100
Multipathed Devices
/dev/sdc /dev/sdd
How do I proceed?
M
On Thu, 2020-05-28 at 15:12 -0500, Michael Thomas wrote:
> On 5/28/20 2:48 PM, Me wrote:
> > Hi All
> >
> > Not sure where to start, but here goes.
> >
> [...]
> > Issue 2, I use FF 72
Hi All
Not sure where to start, but here goes.
I'm not totally new to oVirt, I used RHEV V3.x in production for several
years, it was a breeze to setup.
Installing 4.4 on to a host with local SSD and FC for storage.
Issue 1, having selected the SSD for install which has failed 4.4 beta
on it (s
"trade-off between time [developing] and time spent debugging such cases when
they do happen"
Your call. All I know is, it took me over a month to install oVirt, including
three weeks of one-to-one time with Simone Tiraboschi from Red Hat. He sent me
eleven emails but eventual
Googling the pertinent text from the above long error:
duplicate key value violates unique constraint "name_server_pkey"
led me to this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1530944
and the discovery I had a duplicate DNS IP address in /etc/resolv.conf
Removing this
Fixed my problem. I had a duplicate DNS IP address in my /etc/resolv.conf.
Removing the duplicate and adding the host again worked :-) See further
details how I deduced this in thread here:
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/J65PSDSA2HR4KOCKR4J6GXKOSPNSU54H/
Please r
Actually, I think I've found the most detailed error in
/var/log/ovirt-engine/engine.log. It occurs at exactly the time the webui
errors ("Failed to configure management network on host"):
2019-06-16 23:16:47,888+01 ERROR
[org.ovirt.engine.core.vdsbroker.vdsbroker.CollectVdsNetworkDataAfterIns
Not sure if it's related, but while adding the host, about a minute before the
timeout\error occurs, /var/log/vdsm/mom.log shows:
2019-06-16 22:58:46,799 - mom - ERROR - Failed to initialize MOM threads
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/mom/__init__.py",
Yeh, I'm pretty scoobied too. I'm tried with\without bond, with\without DHCP
for the engine IP. I'm trying plain centos now instead of using Node for the
host.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovi
/:6900):
Compute – Hosts – Click on your Host and then click the Network Interfaces tab
and “Setup Host Networks” button. Add the ovirtmgmt management network to the
appropriate interface.
But this didn't work for me (errored when trying to save c
I'ved added a record to the DNS server here:
ovirt-engine.example.com 10.0.0.109
This IP address is on the physical network that the host is on (host is on
10.0.0.171). I trust this is correct and I should not resolve to a natted IP
instead. I notice that regardless of this record, the name
I should qualify "I went back to using a bond (instead of an individual NIC).
Above network problem
is fixed and now proceeds as far as ever."
After running yum install ovirt-engine-appliance I ran the usual hosted-engine
-deploy command again per the advice here:
https://ovirt.org/documentatio
Okay, I went back to using a bond (instead of an individual NIC). Above
network problem is fixed and now proceeds as far as ever. Hangs for around 10
minutes at:
[ INFO ] TASK [Check engine VM health]
The hosted-engine-setup-ansible-create_target_vm log has:
2018-10-08 23:42:01,664+0100 INFO
Thanks for the suggestion Simone. Tried sudo yum install
ovirt-engine-appliance, no joy:
"
=
Package Arch Version
Fresh installed again. After boot, did not configure bond this time.
Attempted install. Chose the first NIC, got as far as:
[ INFO ] TASK [Check the resolved address resolves on the selected interface]
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
resolved address do
Okay, the above failure at "TASK [Clean /etc/hosts on the host]" seems to have
been due to the fact I hadn't emptied the shared NFS storage after the last
attempt. After fresh-installing node and emptying (rm -rf *), it proceeded a
few steps further to:
[ INFO ] TASK [Clean /etc/hosts on the
Hi,
I've been attempting to install hosted engine intermittently for months without
success. I have raised and had one bug fixed
(https://bugzilla.redhat.com/show_bug.cgi?id=1622240) and am hitting various
other problems. I've freshly installed oVirt Node v4.2.7 (Second Release
Candidate).
Hi,
I've just installed hosted-engine. It proceeds to near the end of the Ansible
script, then pauses at:
"TASK [Check engine VM health]"
then eventually errors:
"Engine VM is not running, please check vdsm logs. The VDSM logs have error:
"libvirtError: internal error: Unknown CPU model Broadwe
18 matches
Mail list logo