ovirt 4.4 self-hosted deployment questions
by Michael Thomas
I have not been able to find answers to a couple of questions in the
self-hosted engine documentation[1].
* When installing a new Enterprise Linux host for ovirt, what are the
network requirements? Specifically, am I supposed to set up the
ovirtmgmt bridge myself on new hosts, or am I supposed to let that be
handled by the engine when I add the new host to the engine?
* In the 'New Host' dialog on the engine management page, does the
Hostname/IP that I enter have to be the host's name on the ovirtmgmt
LAN? If so, then it seems to me that I need to configure the ovirtmgmt
bridge myself on new hosts.
* Does the engine need to be able to route outside of the cluster (eg to
the WAN), or is it allowed to restrict the engine's routing to the local
cluster?
* In the 'New Host' dialog on the engine management page, what is the
meaning of 'Choose hosted engine deployment action'? From the way it is
phrased, it sounds like this will create a second engine in my cluster,
which doesn't make sense. Or does this mean that the new host will be
able to run the Engine VM in a HA manner?
In my current test deployment I have 3 subnets in my cluster. Network
WAN is the WAN. Network CLUSTER is for communication between cluster
compute nodes, storage servers, and management servers. Network OVIRT
is for ovirt management and VM migration between hosts.
My first self-hosted engine host is connected to networks CLUSTER and
OVIRT. The engine VM is only connected to network OVIRT through a
bridge on the host, but has a gateway that lets it route traffic to
network CLUSTER (but not network WAN).
Is this an appropriate network setup for ovirt, or should there be no
distinction between the CLUSTER and OVIRT networks?
--Mike
[1]https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_e...
4 years, 3 months
Gluster Volume Type Distributed
by Dominique Deschênes
Hi Everyone,
I would like to use Distrbuted Volume type but the volume type is Gray out. I can only use the replicate type.
It's normal ?
3 ovirt Servers 4.4.1-2020080418
Can I configure a replicate volume for the engine domain and Distributed for the data domain?
Thank you
Dominique Deschênes
Ingénieur chargé de projets, Responsable TI
816, boulevard Guimond, Longueuil J4G 1T5
450 670-8383 x105 450 670-2259
4 years, 3 months
Failed to connect to the hypervisor
by Eugène Ngontang
Hi,
I'm facing a strange issue with ovirt host.
I can't list nodes status running virsh, vdsdm seems bad.
I can't even delete the hosted engine, nor ping it, but I can still access
my infra vm inside it[image: 😉]
My outputs :
> [root@moe ~]# /usr/sbin/ovirt-hosted-engine-cleanup
> This will de-configure the host to run ovirt-hosted-engine-setup from
> scratch.
> Caution, this operation should be used with care.
> Are you sure you want to proceed? [y/n]
> y
> -=== Destroy hosted-engine VM ===-
> You must run deploy first
> setlocale: No such file or directory
> error: failed to connect to the hypervisor
> error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No
> such file or directory
> -=== Stop HA services ===-
> -=== Shutdown sanlock ===-
> shutdown force 1 wait 0
> shutdown done -111
> -=== Disconnecting the hosted-engine storage domain ===-
> You must run deploy first
> -=== De-configure VDSM networks ===-
> ovirtmgmt
> ovirtmgmt
> A previously configured management bridge has been found on the system,
> this will try to de-configure it. Under certain circumstances you can loose
> network connection.
> Caution, this operation should be used with care.
> Are you sure you want to proceed? [y/n]
> y
> -=== Stop other services ===-
> -=== De-configure external daemons ===-
> -=== Removing configuration files ===-
> ? /etc/init/libvirtd.conf already missing
> ? /etc/libvirt/nwfilter/vdsm-no-mac-spoofing.xml already missing
> ? /etc/ovirt-hosted-engine/answers.conf already missing
> ? /etc/ovirt-hosted-engine/hosted-engine.conf already missing
> ? /etc/vdsm/vdsm.conf already missing
> ? /etc/pki/vdsm/*/*.pem already missing
> ? /etc/pki/CA/cacert.pem already missing
> ? /etc/pki/libvirt/*.pem already missing
> ? /etc/pki/libvirt/private/*.pem already missing
> ? /etc/pki/ovirt-vmconsole/*.pem already missing
> ? /var/cache/libvirt/* already missing
> ? /var/run/ovirt-hosted-engine-ha/* already missing
> [root@moe ~]# ping 192.168.33.143
> PING 192.168.33.143 (192.168.33.143) 56(84) bytes of data.
> 64 bytes from 192.168.33.143: icmp_seq=1 ttl=64 time=0.132 ms
> 64 bytes from 192.168.33.143: icmp_seq=2 ttl=64 time=0.082 ms
> 64 bytes from 192.168.33.143: icmp_seq=3 ttl=64 time=0.072 ms
> 64 bytes from 192.168.33.143: icmp_seq=4 ttl=64 time=0.083 ms
> 64 bytes from 192.168.33.143: icmp_seq=5 ttl=64 time=0.075 ms
> 64 bytes from 192.168.33.143: icmp_seq=6 ttl=64 time=0.082 ms
> ^C
> --- 192.168.33.143 ping statistics ---
> 6 packets transmitted, 6 received, 0% packet loss, time 4999ms
> rtt min/avg/max/mdev = 0.072/0.087/0.132/0.022 ms
> [root@moe ~]# nodectl check
> Status: WARN
> Bootloader ... OK
> Layer boot entries ... OK
> Valid boot entries ... OK
> Mount points ... OK
> Separate /var ... OK
> Discard is used ... OK
> Basic storage ... OK
> Initialized VG ... OK
> Initialized Thin Pool ... OK
> Initialized LVs ... OK
> Thin storage ... OK
> Checking available space in thinpool ... OK
> Checking thinpool auto-extend ... OK
> vdsmd ... BAD
> [root@moe ~]# virsh -r list
> setlocale: No such file or directory
> error: failed to connect to the hypervisor
> error: Failed to connect socket to '/var/run/libvirt/libvirt-sock-ro': No
> such file or directory
> [root@moe ~]#
Have you guys ever faced this issue?
How can I access VM inside my virtual data center while the VM Manager is
broken?
Any solution to work around this please?
Regards,
Eugène NG
--
LesCDN <http://lescdn.com>
engontang(a)lescdn.com
------------------------------------------------------------
*Aux hommes il faut un chef, et au*
* chef il faut des hommes!L'habit ne fait pas le moine, mais lorsqu'on te
voit on te juge!*
4 years, 3 months
Compatibilty issue
by carl langlois
Hi,
I have upgraded ovirt to 4.3 and now I have some vm that I can start
because of the cluster compatibility version. Those VM where in save state
when I updated the cluster compatibility version. Now they are in a down
state but if i try to run it I get this message.
Cannot run VM. The Custom Compatibility Version of VM vmfpgatest (4.2) is
not supported in Data Center compatibility version 4.3.
any suggestions?
Regards
Carl
4 years, 4 months
TroubleshootingoVirt Node deploy FQDN not reachable
by David White
In a recent thread, Roberto mentioned seeing the error message "FQDN Not Reachable" when trying to deploy oVirt Node 4.4.1, but was able to get past that error when using ovirt-node-ng-installer-4.4.2-2020080612.el8.iso.
I experienced the same problems on oVirt Node install 4.4.1, so I tried the latest release of 4.4.2. When that failed, I went back and installed from the exact same image as Roberto said worked on the 4.4.2 branch: ovirt-node-ng-installer-4.4.2-2020080612.el8.iso
Unfortunately, that's still not working for me - so that tells me I'm probably doing something wrong.
Given the following facts:
[root@dev1-centos ~]# hostname
dev1-centos.office.barredowlweb.com
[root@dev1-centos ~]# host dev1-centos.office.barredowlweb.com
dev1-centos.office.barredowlweb.com has address 192.168.2.96
I am trying to install oVirt using the Hyperconverged Gluster Wizard for a Single Node.
In the "Host1" box, I enter the full hostname: dev1-centos.office.barredowlweb.com
And that's when I get the FQDN error message.
Am I missing something here?
Sent with ProtonMail Secure Email.
4 years, 4 months
Is the Hosted Engine setup finished + Can't connect vdsm storage
by Bielej SRE
Hi,
We have 6 node oVirt setup with Compatibility version 4.3 running on CentOS 7.6.1810
Recently We have found out some very interesting log entries on a few of our nodes.
/var/log/ovirt-hosted-engine-ha/broker.log:
MainThread::INFO::2020-08-27 12:51:50,279::storage_backends::345::ovirt_hosted_engine_ha.lib.storage_backends::(connect) Connecting the storage
MainThread::INFO::2020-08-27 12:51:50,280::storage_server::349::ovirt_hosted_engine_ha.lib.storage_server.StorageServer::(connect_storage_server) Connecting storage server
MainThread::warning::2020-08-27 12:51:50,284::storage_broker::97::ovirt_hosted_engine_ha.broker.storage_broker.StorageBroker::(__init__) Can't connect vdsm storage: 'NoneType' object has no attribute 'startswith'
/var/log/messages
Aug 27 12:52:11 ildeco25 vdsm[6909]: ERROR failed to retrieve Hosted Engine HA score '[Errno 2] No such file or directory'Is the Hosted Engine setup finished?
We have inherited that setup from the previous team but I'm fairly certain the the Hosted Engine setup is finished.
Also, this line is not present on all hosts.
Should We worry about ovirt-ha-broker service not running on some hosts?
host24 Active: inactive (dead)
host25 Active: failed (Result: start-limit) since Thu 2020-08-27 12:56:13 CEST; 2s ago
host26 Active: active (running) since Sun 2020-08-23 22:55:01 CEST; 3 days ago
host27 Active: inactive (dead)
host28 Active: failed (Result: start-limit) since Thu 2020-08-27 12:56:18 CEST; 4s ago
host29 Active: inactive (dead)
Currently the hosted engine VM is running on host26.
I'd be very grateful for any help.
Kind regards,
Michal Bielejewski
4 years, 4 months
Impossible to install Windows VMs on 4.4.1
by fgarat＠gmail.com
Hi,
I'm having problem after I upgraded to 4.4.1 with Windows machines.
The installation sees no disk. Even IDE disk doesn't get detected and installation won't move forward no matter what driver i use for the disk.
Any one else having this issue?.
Regards,
Facundo
4 years, 4 months
Host has no default route
by Wesley Stewart
I am trying to add a host to a single host cluster. Everything has gone
pretty well so far, except when the host gets to the end of the
installation process, I see an exclamation mark indicating "Host has no
default route".
The installation "finishes" and the host goes into a non-responsive state.
I am not really sure where to check. I get a:
host *name* installation has failed. Network error during communication
with host.
Running 4.3.6
Thanks!
4 years, 4 months
[ANN] oVirt 4.4.2 Fifth Release Candidate is now available for testing
by Lev Veyde
oVirt 4.4.2 Fifth Release Candidate is now available for testing
The oVirt Project is pleased to announce the availability of oVirt 4.4.2
Fifth Release Candidate for testing, as of August 27th, 2020.
This update is the second in a series of stabilization updates to the 4.4
series.
Important notes before you try it
Please note this is a pre-release build.
The oVirt Project makes no guarantees as to its suitability or usefulness.
This pre-release must not be used in production.
Installation instructions
For installation instructions and additional information please refer to:
https://ovirt.org/documentation/
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 8.2 or newer
* CentOS Linux (or similar) 8.2 or newer
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 8.2 or newer
* CentOS Linux (or similar) 8.2 or newer
* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)
See the release notes [1] for installation instructions and a list of new
features and bugs fixed.
Notes:
- oVirt Appliance is already available for CentOS Linux 8
- oVirt Node NG is already available for CentOS Linux 8
Additional Resources:
* Read more about the oVirt 4.4.2 release highlights:
http://www.ovirt.org/release/4.4.2/
* Get more oVirt project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.4.2/
[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/
--
Lev Veyde
Senior Software Engineer, RHCE | RHCVA | MCITP
Red Hat Israel
<https://www.redhat.com>
lev(a)redhat.com | lveyde(a)redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
4 years, 4 months
LDAP/AD issue
by kim.kargaard＠noroff.no
Hi all,
We have had our ovirt instance connected to our internal AD for users to log into the VM portal for the last year, linked to studentdomene.noroff.no. This has been working without any problems. We had it set up and the DNS server had a forward record to the DC's. All good.
Then, of course, the institution decided to introduce student emails and they decided to add the domain stud.noroff.no for student emails and made this the primary domain in the AD. The problem is that when this is changed, students can no longer log into the engine. I have of course changed the ldap settings and added a forward record on the DNS to the new domain. However, it seems that the domain is studentdomene.noroff.no, but with an added UPN suffix with stud.noroff.no
When students try to log in, with the config changes, they get this error in the browser:
server_error: An error occurred while attempting to query DNS in order to retrieve SRV records with name '_ldap._tcp.stud.noroff.no': NameNotFoundException(DNS name not found [response code 3]), ldapSDKVersion=4.0.7, revision=b28fb50058dfe2864171df2448ad2ad2b4c2ad58
Any ideas on how to solve this issue?
My config looks like this:
sudo cat /etc/ovirt-engine/aaa/Students.properties
[sudo] password for noroffadmin:
include = <ad.properties>
vars.domain = studentdomene.noroff.no
vars.user = CN=ovirt auth,CN=Users,DC=stud,DC=noroff,DC=no
vars.password = PASSWORD
pool.default.auth.simple.bindDN = ${global:vars.user}
pool.default.auth.simple.password = ${global:vars.password}
pool.default.serverset.type = srvrecord
pool.default.serverset.srvrecord.domain = ${global:vars.domain}
my forward on the DNS server looks like this:
sudo cat /etc/named/named.conf.local
[sudo] password for noroffadmin:
zone "platform.noroff.no"{
type master;
file "/etc/named/zones/db.platform.noroff.no"; # zone file path
};
zone "stud.noroff.no" {
type forward;
forward only;
forwarders { 172.24.111.20; 172.27.111.20; 172.21.111.20; 172.16.111.20; };
};
zone "studentdomene.noroff.no" {
type forward;
forward only;
forwarders { 172.24.111.20; 172.27.111.20; 172.21.111.20; 172.16.111.20; };
};
zone "122.16.172.in-addr.arpa" {
type master;
file "/etc/named/zones/db.122.16.172"; # 172.16.122.0/24 subnet
};
Any pointers would be greatly appreciated :)
Kim
4 years, 4 months
