November 2020 - Users - Ovirt List Archives

by Nicolás

Hi, We're running oVirt 4.3.8 and even if this is a problem we've had since a lot of time (I would say since 4.0.x), I decided to look for help in case anything can be done. Our environment is heavily used by users in our University (about 3000 users), and currently our oVirt infrastructure has 1928 virtual machines, being 882 of them currently running. We have a separate physical machine for the manager node, and the problem is that this machine is very, very, very slow, despite it has (from my point of view) enough physical resources to run efficiently. By slow I mean even the SSH access to it takes about 10 seconds, not just the admin/user portals. Any operation takes enough time to make the experience not comfortable to our users (enter the VM portal, start a VM, open a console...). Node machine's parameters are: 18GB of RAM memory 1 processor with 12CPUs 300GB SCSI Disk, local storage. No Storage Domain is stored in this node machine. Currently, most consuming processes are: 28802 ovirt 20 0 3302876 1,5g 25988 S 1,0 8,7 22:46.36 ovirt-engine -server -XX:+TieredCompilation -Xms1024M -Xmx1024M -Xss1M -Djava.aw+ 28701 ovirt 20 0 5465432 807704 13140 S 5,9 4,4 3:15.53 ovirt-engine-dwhd -Dorg.ovirt.engine.dwh.settings=/tmp/tmp8wtnTA/settings.proper+ # free -m total used free shared buff/cache available Mem: 17886 6669 2734 255 8482 10625 Swap: 6143 1002 5141 There are also a lot of postgresql processes: postgres 2186 0.0 0.0 261812 4136 ? Ss jun05 37:39 /opt/rh/rh-postgresql10/root/usr/bin/postmaster -D /var/opt/rh/rh-postgresql10/lib/pgsql/data postgres 3176 0.0 0.0 216084 656 ? Ss jun05 0:00 postgres: logger process postgres 3290 0.0 0.2 262204 37476 ? Ss jun05 77:31 postgres: checkpointer process postgres 3291 0.3 0.2 262052 36960 ? Ss jun05 754:02 postgres: writer process postgres 3292 0.0 0.0 261812 1988 ? Ss jun05 100:51 postgres: wal writer process postgres 3293 0.0 0.2 262380 36748 ? Ss jun05 21:58 postgres: autovacuum launcher process postgres 3294 0.1 0.0 219216 1412 ? Ds jun05 335:41 postgres: stats collector process postgres 3295 0.0 0.0 262220 1460 ? Ss jun05 0:11 postgres: bgworker: logical replication launcher postgres 3393 0.0 0.2 265792 40452 ? Ss jun05 15:36 postgres: engine engine ::1(51664) idle postgres 6105 0.3 0.0 271532 15976 ? Ds 13:01 0:00 postgres: autovacuum worker process ovirt_engine_history postgres 6216 0.2 0.0 263864 11440 ? Ss 13:02 0:00 postgres: autovacuum worker process engine postgres 6245 0.0 0.0 262888 6212 ? Ss 13:02 0:00 postgres: engine engine 127.0.0.1(42400) idle postgres 6246 0.0 0.0 262844 3256 ? Ss 13:02 0:00 postgres: autovacuum worker process template1 postgres 18815 0.0 0.0 262912 5852 ? Ss nov01 0:00 postgres: django django 127.0.0.1(59564) idle postgres 23148 0.0 0.2 266052 43024 ? Ss oct28 9:01 postgres: engine engine 127.0.0.1(59714) idle postgres 23149 0.0 0.0 262980 6820 ? Ss oct28 0:00 postgres: engine engine 127.0.0.1(59716) idle postgres 28784 0.0 0.0 262816 3492 ? Ss 12:02 0:00 postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39470) idle postgres 28785 0.0 0.0 262816 3496 ? Ss 12:02 0:00 postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39472) idle postgres 28921 0.8 0.7 375152 146452 ? Ss 12:03 0:30 postgres: engine engine 127.0.0.1(39484) idle postgres 29007 3.3 0.7 369348 142184 ? Ds 12:03 1:58 postgres: engine engine 127.0.0.1(39498) SELECT postgres 29009 5.0 0.3 294736 72776 ? Ss 12:03 2:58 postgres: ovirt_engine_history ovirt_engine_history 127.0.0.1(39500) idle postgres 29048 0.0 0.0 263664 12176 ? Ss 12:03 0:00 postgres: engine engine 127.0.0.1(39530) idle postgres 29064 0.6 0.8 384936 157852 ? Ss 12:03 0:24 postgres: engine engine 127.0.0.1(39532) idle postgres 29065 1.2 0.7 358944 137028 ? Ss 12:03 0:43 postgres: engine engine 127.0.0.1(39534) idle postgres 29066 1.9 0.7 355800 132800 ? Ss 12:03 1:08 postgres: engine engine 127.0.0.1(39536) idle postgres 29067 1.0 0.7 370688 140504 ? Ss 12:03 0:37 postgres: engine engine 127.0.0.1(39538) idle postgres 29068 1.7 0.7 360984 139584 ? Ss 12:03 1:02 postgres: engine engine 127.0.0.1(39540) idle postgres 29069 1.3 0.7 358140 136268 ? Ss 12:03 0:48 postgres: engine engine 127.0.0.1(39542) idle postgres 29070 3.7 0.7 372064 141724 ? Ss 12:03 2:13 postgres: engine engine 127.0.0.1(39544) idle postgres 29071 0.8 0.6 337224 114132 ? Ss 12:03 0:31 postgres: engine engine 127.0.0.1(39546) idle postgres 29072 0.5 0.6 336616 114276 ? Ss 12:03 0:18 postgres: engine engine 127.0.0.1(39548) idle postgres 29073 1.7 0.7 357872 134540 ? Ss 12:03 1:02 postgres: engine engine 127.0.0.1(39550) idle postgres 29139 3.5 0.7 361244 134176 ? Ss 12:03 2:07 postgres: engine engine 127.0.0.1(39572) idle postgres 29140 3.0 0.7 367884 138372 ? Ss 12:03 1:46 postgres: engine engine 127.0.0.1(39570) idle postgres 29141 1.0 0.9 391984 169204 ? Ss 12:03 0:38 postgres: engine engine 127.0.0.1(39574) idle postgres 29142 1.3 0.7 358820 136140 ? Ss 12:03 0:48 postgres: engine engine 127.0.0.1(39576) idle postgres 29143 1.6 0.8 385000 156592 ? Ss 12:03 0:58 postgres: engine engine 127.0.0.1(39578) idle postgres 29144 3.6 0.9 403740 174552 ? Ss 12:03 2:09 postgres: engine engine 127.0.0.1(39580) idle postgres 29145 3.4 0.7 355800 128876 ? Ss 12:03 2:01 postgres: engine engine 127.0.0.1(39582) idle postgres 29146 1.8 0.8 380884 157828 ? Ss 12:03 1:06 postgres: engine engine 127.0.0.1(39586) idle postgres 29147 3.5 0.6 353228 123200 ? Ss 12:03 2:05 postgres: engine engine 127.0.0.1(39584) idle postgres 29148 0.9 0.8 383452 156268 ? Ss 12:03 0:34 postgres: engine engine 127.0.0.1(39588) idle postgres 29149 1.3 0.7 365552 139612 ? Ss 12:03 0:47 postgres: engine engine 127.0.0.1(39590) idle postgres 29150 1.2 0.7 363448 136564 ? Ss 12:03 0:43 postgres: engine engine 127.0.0.1(39592) SELECT postgres 29151 1.4 0.7 365940 139184 ? Ss 12:03 0:51 postgres: engine engine 127.0.0.1(39594) idle postgres 29152 1.2 0.7 358328 134268 ? Ss 12:03 0:44 postgres: engine engine 127.0.0.1(39596) idle postgres 29402 1.3 0.7 362044 139812 ? Ss 12:04 0:47 postgres: engine engine 127.0.0.1(39698) idle postgres 29403 2.1 0.8 377760 154556 ? Ss 12:04 1:15 postgres: engine engine 127.0.0.1(39700) idle postgres 29404 2.2 0.7 369160 144600 ? Ss 12:04 1:18 postgres: engine engine 127.0.0.1(39702) idle postgres 32230 0.1 0.5 336252 101912 ? Ss 12:19 0:04 postgres: engine engine 127.0.0.1(40564) idle postgres 32232 3.4 0.6 357644 127732 ? Ss 12:19 1:29 postgres: engine engine 127.0.0.1(40566) idle postgres 32234 0.0 0.1 270924 19836 ? Ss 12:19 0:00 postgres: engine engine 127.0.0.1(40568) idle Actually, I'm not really sure why is this machine so slow. In terms of RAM memory and CPU, it still has a bunch of free resources. Could someone help track this down and point some advices on how to optimize the user experience in this case? Thanks!

4 years, 5 months

2
1
0 / 0

easy way to migrate to new engine

by jb

Hello everybody! At the moment I have here a standalone engine and two nodes. Storage type is NFS. Now I want to setup a 3 node self hosted cluster with Glusterfs and import my VMs from the old engine. I know, there is a guide for migration from standalone to self-hosted engine, but there is so many changes (new Subnet/DNS names, different type of storage, new CPU type) that I would like to skip this migration guide. Is there a different way to migrate my VMs? Mounting my old storage and moving the disks to the Gluster would be nice, but I guess I can not just mount a storage with existing VM images. Best regards Jonathan

4 years, 5 months

3
2
0 / 0

Re: Problem with Cluster-wise BIOS Settings in oVirt 4.4

by Vladislav S

PLEASE HELP I changed the type in the cluster and now my hosted-engine machine won't start!. There are no backups. How can I manually change the parameters of the machine from under the roof so that it starts and I can restore ovirt to work Error in logs: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port

4 years, 5 months

2
1
0 / 0

Root Password Reset

by ilirdaka＠live.com

Hello! I'm new to oVirt, one of my customers has a 2 node (cluster) of oVirt but has no password access to it! Is there any way to reset that password? Best regards, Ilir

4 years, 5 months

3
4
0 / 0

Async release for oVirt 4.4.3

by Sandro Bonazzola

On November 16th the oVirt project released an async update to the following packages: - ovirt-ansible-collection-1.2.2-1 - ovirt-engine-4.4.3.12 - ovirt-engine-sdk 4.4.7 Fixing the following bugs: - [BZ 1884599 <https://bugzilla.redhat.com/1884599>] - Hosted-engine deploy is failing with error "Unable to access credentials /etc/pki/vdsm/libvirt-vnc/ca-cert.pem" - [BZ 1894111 <https://bugzilla.redhat.com/1894111>] - After host upgrade from 4.4.2 to 4.4.3 there are still packages left to upgrade - [BZ 1894758 <https://bugzilla.redhat.com/1894758>] - [DR] Remote data sync to the secondary site never completes - Support enum URL parameters in Python SDK -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

4 years, 5 months

1
0
0 / 0

Migrate old storage domains to new oVirt

by Joris Dobbelsteen

Hi All, I still have a single-node (all-in-one) oVirt 3.5 setup that has worked great and uses a local storage domain. I’m migrating to oVirt 4.4 hosted setup as I need to replace disks. However, since this is a single node setup, making the migration a bit tricker than usual. My plan is to move the physical disks over, mount the old local storage domains and use them in oVirt 4.4. E.g. to move the images. Is this still possible with old domains? Or is there something special that should be taken care of? Since the original domains are local is this something to take care of? E.g. can hosted engine setup be running on a “local” datacentre? Best regards, Joris Dobbelsteen

4 years, 5 months

1
0
0 / 0

oVirt Node Crash

by Anton Louw

Hi Everybody, I have built a new host which has been running fine for the last couple of days. I noticed today that the host crashed, but it is not giving me a reason as to why. It happened at 13:45 today, but I have given time before that on the logs as well. Is there something I am missing here? Thanks Anton Louw Cloud Engineer: Storage and Virtualization ______________________________________ D: 087 805 1572 | M: N/A A: Rutherford Estate, 1 Scott Street, Waverley, Johannesburg anton.louw(a)voxtelecom.co.za www.vox.co.za

4 years, 5 months

2
3
0 / 0

Backporting of Fixes

by Gillingham, Eric J (US 393D)

I'm still running on oVirt 4.3 due to some hardware that will require some extra effort to move to 4.4 we're not quite ready to do yet, and am currently hitting what I believe to be https://bugzilla.redhat.com/show_bug.cgi?id=1820998 which is fixed in 4.4. I'm wondering if there's a process to request a backport, or should I just open a new bug against 4.3? Thank You - Eric

4 years, 5 months

2
1
0 / 0

oVirt 4.4 vnic profile to substitute vdsm mac spoof hook

by Gianluca Cecchi

Hello, I have an Openstack Queens environment that is composed by VMs inside oVirt. Initially this oVirt environment was on 4.3 and on director I had to set vdsm mac spoof to be able to give dhcp address to the overcloud nodes. I tried something at that time with vnic profiles but I was not able to have it work as expected, so I used the hook. Now I have migrated this same environment to 4.4.2 and I see that vdsm mac spoof is no more an option: https://bugzilla.redhat.com/show_bug.cgi?id=1703840 I tried some combinations of vnic profiles on director vnic but it seems not to work as a dhcpserver as before. I see DHCPDISCOVER from overcloud node in director messages (while before I saw DHCPREQUEST), I see the DHCPOFFER from director, but I don't see the DHCPACK from the overcloud node... On director I have the br-ctlplane vswitch using its interface eth1: ovs-vsctl show . . . Bridge br-ctlplane Controller "tcp:127.0.0.1:6633" is_connected: true fail_mode: secure Port br-ctlplane Interface br-ctlplane type: internal Port "eth1" Interface "eth1" Port phy-br-ctlplane Interface phy-br-ctlplane type: patch options: {peer=int-br-ctlplane} ovs_version: "2.11.0" [root@director ~]# ovs-ofctl show br-ctlplane OFPT_FEATURES_REPLY (xid=0x2): dpid:0000566f3d480014 n_tables:254, n_buffers:0 capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst 1(eth1): addr:56:6f:3d:48:00:13 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max 2(phy-br-ctlplane): addr:76:76:8b:08:d4:2f config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max LOCAL(br-ctlplane): addr:56:6f:3d:48:00:14 config: 0 state: 0 speed: 0 Mbps now, 0 Mbps max OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 [root@director ~]# [root@director ~]# ip addr show dev br-ctlplane 6: br-ctlplane: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 56:6f:3d:48:00:14 brd ff:ff:ff:ff:ff:ff inet 172.23.0.220/24 brd 172.23.0.255 scope global br-ctlplane valid_lft forever preferred_lft forever inet 172.23.0.222/32 scope global br-ctlplane valid_lft forever preferred_lft forever inet 172.23.0.221/32 scope global br-ctlplane valid_lft forever preferred_lft forever inet6 fe80::546f:3dff:fe48:14/64 scope link valid_lft forever preferred_lft forever [root@director ~]# The eth1 interface is configured in oVirt on vlan23. The overcloud nodes have one vnic on vlan 23. I have two dnsmasq processes on director, for ironic and for overcloud nodes: nobody 1527 1 0 Nov14 ? 00:00:00 /sbin/dnsmasq --conf-file=/etc/ironic-inspector/dnsmasq.conf nobody 3288 1 0 Nov14 ? 00:00:00 dnsmasq --no-hosts --no-resolv --pid-file=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/host --addn-hosts=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/addn_hosts --dhcp-optsfile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/opts --dhcp-leasefile=/var/lib/neutron/dhcp/22a5739b-acb6-4400-8247-080a66895f1a/leases --dhcp-match=set:ipxe,175 --local-service --bind-dynamic --dhcp-range=set:subnet-d48e002b-f269-4ed5-a96e-9aeba0b119b9,172.23.0.0,static,255.255.255.0,86400s --dhcp-option-force=option:mtu,1500 --dhcp-lease-max=256 --conf-file=/etc/dnsmasq-ironic.conf --domain=localdomain In messages of director when booting the overcloud node: Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPDISCOVER(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c Nov 15 00:42:45 director dnsmasq-dhcp[1527]: 3792136019 DHCPDISCOVER(br-ctlplane) 56:6f:3d:48:00:3c ignored Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPOFFER(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c Nov 15 00:42:45 director dnsmasq-dhcp[3288]: DHCPOFFER(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c In oVirt 4.3 with the same setup and VDSM MAC spoof hook configured I saw this inside messages of director when booting the overcloud nodes: Oct 18 04:50:05 director dnsmasq-dhcp[3230]: DHCPREQUEST(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c Oct 18 04:50:05 director dnsmasq-dhcp[3230]: DHCPACK(tap9fdd5920-62) 172.23.0.232 56:6f:3d:48:00:3c host-172-23-0-232 Questions: what is the filter to give to have it work? is it dynamic the effect at runtime for a running VM to edit its vnic and change its profile? is it dynamic for running VMs that for a vNIC with a certain profile if I go in Networks --> vNIC Profiles --> Edit vNIC Profile and change its network filter value? Thanks for any insight. Gianluca

4 years, 5 months

1
2
0 / 0

Failed to add new host to oVirt 4.4.3.11-1.el8

by Winfried de Heiden

Hi all, Adding a brand new installed oVirt node to oVirt 4.4.3.11-1.el8 fails; engine.log will tell: 2020-11-13 10:05:40,777+01 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-5) [80e3f255-f8b9-4d5f-9be2-ebb59fec28db] EVENT_ID: VDS_ANSIBLE_INSTALL_STARTED(560), Ansible host-deploy playbook execution has started on host Bigvirt. 2020-11-13 10:05:40,784+01 ERROR [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engine-Thread-5) [80e3f255-f8b9-4d5f-9be2-ebb59fec28db] Exception: Failed to read the runner-service response. Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: org.apache.http.conn.EofSensorInputStream@6cc9953a; line: 1, column: 2] 2020-11-13 10:05:40,785+01 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-5) [80e3f255-f8b9-4d5f-9be2-ebb59fec28db] Host installation failed for host 'df87842f-0852-4a3a-898b-2b724b068199', 'Bigvirt': Failed to execute Ansible host-deploy role: Failed to read the runner-service response. Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') Anyone got a clue? Winfried

4 years, 5 months

3
2
0 / 0

Re: Network profile filtering

by Dominik Holler

On Fri, Nov 13, 2020 at 4:19 PM Pascal DeMilly <Pascal(a)butterflyit.com> wrote: > Thank you > > That is exactly what I was looking for. Any chance it could be back > ported to 4.3. Maybe list the rules and I could use rest API to add it to > my court install > On ovirt-4.3 there is only *Bug 1009608* <https://bugzilla.redhat.com/show_bug.cgi?id=1009608> - [RFE] Limit east-west traffic of VMs with network filter The isolated ports cannot be backported to oVirt 4.3, because the isolated ports require a new feature from CentOS 8 kernel and CentOS 8.3 libvirt. > > I'm not eager to move yet to 4.4 since I'm reading on this list lot of > people have issue migrating and I have 20 hosts running currently > > Are you aware that you could upgrade oVirt Engine and go on with the oVirt 4.3 hosts? This way you could have some new CentOS 8 based oVirt-4.4 hosts which use the new features, and leave the other hosts on CentOS 7 based oVirt 4.3 . > > > Get Outlook for Android <https://aka.ms/ghei36> > > ------------------------------ > *From:* Dominik Holler <dholler(a)redhat.com> > *Sent:* Friday, November 13, 2020 6:21:56 AM > *To:* Pascal DeMilly <Pascal(a)butterflyit.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Network profile filtering > > > > On Fri, Nov 13, 2020 at 5:13 AM <pascal(a)butterflyit.com> wrote: > > I am using ovirt 4.3. I am in need to isolate all my VM from each other > (without using VLAN) except to a virtual gateway which is also the DHCP > server. > > Basically only allowing traffic from 1 MAC address to another MAC address. > Everything else should be filter out by ovirt filtering subsystem > > How will I go about that? I can see in network profile the ability to set > different filter but can't find a way to create new filter. > > > Does the Doc Text of > *Bug 1009608* <https://bugzilla.redhat.com/show_bug.cgi?id=1009608> - [RFE] > Limit east-west traffic of VMs with network filter > https://bugzilla.redhat.com/show_bug.cgi?id=1009608 > explain the configuration of the filter? > > Please note that there will be isolated ports > > https://www.ovirt.org/develop/release-management/features/network/isolate... > available in ovirt-4.4.3 on CentOS 8.3 , which might address your scenario > even better. > > > > Thanks for your help > > Pascal > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/QIYX2SA7TBE... > >

4 years, 5 months

2
1
0 / 0

Fail to upgrade cluster from 4.3 to 4.4

by Gianluca Cecchi

Hello, my environment was oVirt 4.3.10 with an external engine and 3 hosts. I have updated to 4.4.3 the whole infra, but know if I go and update the cluster to 4.4 I get the message in this window: https://drive.google.com/file/d/1hfs4FC8uZ-EjiCzQyitA3945U0Knnz2m/view?us... What is the reason for it? My Cluster is with Cluster CPU Type: "Intel Westmere IBRS SSBD Family" The signalled 'hostmaster' VM is a powered off VM used in the past to test nested virtualization and in "Virtual Machines" page aside it I see an exclamation mark with "The VM CPU doesn't match the Cluster Cpu Type" The VM is set as custom, optimized for Server Custom Chipset/Firmware Type "Cluster default (i440FX Chipset with BIOS)" Custom Emulated Machine (in grey): "Cluster default(pc-i440fx-rhel7.6.0)" Custom CPU (in grey): "Cluster default(Intel Westmere IBRS SSBD Family)" What I'm expected to change? Thanks, Gianluca

4 years, 5 months

1
1
0 / 0

Terraform provider build

by Muhsin Tawafig

Hi Trying to test terraform ovirt provider keep getting failure on pulling modules ( on centos 7 & 8 ) #make ==> Checking that code complies with gofmt requirements... go install go: github.com/hashicorp/go-getter@v1.4.2-0.20200106182914-9813cbd4eb02: Get "https://proxy.golang.org/github.com/hashicorp/go-getter/@v/v1.4.2-0.20200...": net/http: TLS handshake timeout make: *** [build] Error 1 Any help is appretiated

4 years, 5 months

2
1
0 / 0

Network profile filtering

by pascal＠butterflyit.com

I am using ovirt 4.3. I am in need to isolate all my VM from each other (without using VLAN) except to a virtual gateway which is also the DHCP server. Basically only allowing traffic from 1 MAC address to another MAC address. Everything else should be filter out by ovirt filtering subsystem How will I go about that? I can see in network profile the ability to set different filter but can't find a way to create new filter. Thanks for your help Pascal

4 years, 5 months

3
2
0 / 0

ovirt glusterfs

by garcialiang.anne＠gmail.com

Hello, I try use Gluster deploymont. I've the message error: failed: [llrovirttest02.in2p3.fr] (item={u'path': u'/gluster_bricks/engine', u'vgname': u'gluster_vg_sdb', u'lvname': u'gluster_lv_engine'}) => {"ansible_loop_var": "item", "changed": false, "item": {"lvname": "gluster_lv_engine", "path": "/gluster_bricks/engine", "vgname": "gluster_vg_sdb"}, "msg": "SELinux is disabled on this host."} Could you help me ? Thanks, Anne Garcia

4 years, 5 months

2
1
1 / 0

Unable to attach VLAN-based logical networks to a bond oVirt 4.4

by simon＠justconnect.ie

When attempting to add a VLAN to a bonded interface (Broadcom NICs) in oVirt Management portal the process fails as per: https://bugzilla.redhat.com/show_bug.cgi?id=1860479 This issue has rendered mu upgrade to 4.4 useless. Does anyone have a patched kernel to resolve this please? Regards Shimme

4 years, 5 months

2
1
0 / 0

Ballooning disabled when creating a VmPool

by Nicolás

Hi, We're using oVirt 4.3.8 along with ovirt-engine-sdk-python (4.4.1) to handle our pools. Pools are based on a template which has ballooning enabled. However, when deploying a VmPool based on that template, has the "Ballooning enabled" field disabled, uneditable and an icon which states: "The field is not attached to any instance type" (screenshot attached). We're handling a big number of VMs based on pools (> 1500), and we think this should be enabled. However, I don't see a field in the types.VmPool definition that allows that. Is that even doable? Our Python code is similar to this: newpool = types.VmPool(name='test', cluster=cl, template=t, max_user_vms=1, size=1, type=types.VmPoolType.MANUAL) vmpool_serv.add(newpool) * cl is a types.Cluster instance with ballooning_enabled=True * t is a types.Template instance with Ballooning enabled. Thanks. Nico

4 years, 5 months

2
4
0 / 0

Old and new hardware mix

by nick＠creativitysoftware.net

Hi All, I've just joined the mailing list as my organisation needs a new virtualisation solution. VMware is prohibitively expensive for a small company like ours and of all the opensource solutions, oVirt looks like the best fit for our needs. Our existing virtual infrastructure is primarily made up of an old vSphere 5 cluster (expired license on old and out of warranty hardware) and a couple of newer standalone (free) ESXi servers. Both the cluster and the standalones have shared NFS storage so I can move VMs around. I want to take a couple of older (2014ish) servers which will serve as the management host and one compute node initially. Then, I'd like to migrate VMs from one vSphere host at a time to the newly created oVirt cluster and convert the now empty vSphere ESXi hosts into oVirt compute nodes as I go. Firstly - Would new compute host hardware (2020) work in a (2014) based ovirt cluster? If so Would I be able to take advantage of the more advanced features of ovirt like live migration etc.. with a mix of new and old hardware Thanks

4 years, 5 months

3
5
0 / 0

Re: sshd_config AuthorizedKeysFile

by Strahil Nikolov

What happens when you change the default, but also add a "Match" directive overriding that option for the engine ? Best Regards, Strahil Nikolov В четвъртък, 12 ноември 2020 г., 10:01:12 Гринуич+2, Angus Clarke <angus(a)charworth.com> написа: Hello Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys.HTH Angus _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UMJ4Y622RAL...

4 years, 5 months

1
0
0 / 0

rhv 4.3.11 but not ovirt 4.3.11

by Gianluca Cecchi

Hello, I see that a 4.3.11 version is available for downstream RHV but not for upstream oVirt. Will it be released for oVirt too? Are there only security fixes inside or also bug fixes (like the few lines one related to export as OVA)? Thanks, Gianluca

4 years, 5 months

3
3
0 / 0

oVrit 4.3.10 on CentOS 7.9

by Christoph Timm

Hi list, I want to update my oVirt installation to 4.3.10 on the weekend to get ready to move to 4.4 by end of December. Would it be OK to update to oVirt 4.3.10 on CentOS 7.9 which was release today? Best regards Christoph

4 years, 5 months

1
0
0 / 0

Engine update error from 4.4.2 to 4.4.3

by Gianluca Cecchi

Hello, is this still the correct command during updates through minor releases in 4.4.x? yum update ovirt\*setup\* Because my standalone external engine is now at level ovirt-engine-4.4.2.6-1.el8.noarch with [root@ovmgr1 ~]# yum repolist repo id repo name AppStream CentOS-8 - AppStream BaseOS CentOS-8 - Base PowerTools CentOS-8 - PowerTools extras CentOS-8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-advanced-virtualization Advanced Virtualization packages for x86_64 ovirt-4.4-centos-gluster7 CentOS-8 - Gluster 7 ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo for ovsdbapp owned by mdbarroso ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22 Copr repo for NetworkManager-1.22 owned by networkmanager ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2 Copr repo for nmstate-stable owned by nmstate ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL [root@ovmgr1 ~]# yum repolist repo id repo name AppStream CentOS-8 - AppStream BaseOS CentOS-8 - Base PowerTools CentOS-8 - PowerTools extras CentOS-8 - Extras ovirt-4.4 Latest oVirt 4.4 Release ovirt-4.4-advanced-virtualization Advanced Virtualization packages for x86_64 ovirt-4.4-centos-gluster7 CentOS-8 - Gluster 7 ovirt-4.4-centos-opstools CentOS-8 - OpsTools - collectd ovirt-4.4-centos-ovirt44 CentOS-8 - oVirt 4.4 ovirt-4.4-copr:copr.fedorainfracloud.org:mdbarroso:ovsdbapp Copr repo for ovsdbapp owned by mdbarroso ovirt-4.4-copr:copr.fedorainfracloud.org:networkmanager:NetworkManager-1.22 Copr repo for NetworkManager-1.22 owned by networkmanager ovirt-4.4-copr:copr.fedorainfracloud.org:nmstate:nmstate-0.2 Copr repo for nmstate-stable owned by nmstate ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible Copr repo for gluster-ansible owned by sac ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection Copr repo for EL8_collection owned by sbonazzo ovirt-4.4-epel Extra Packages for Enterprise Linux 8 - x86_64 ovirt-4.4-virtio-win-latest virtio-win builds roughly matching what will be shipped in upcoming RHEL [root@ovmgr1 ~]# - /etc/yum.repos.d/ovirt-4.4.repo [ovirt-4.4] name=Latest oVirt 4.4 Release #baseurl=https://resources.ovirt.org/pub/ovirt-4.4/rpm/el$releasever/ mirrorlist= https://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.4-el$releasever enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-ovirt-4.4 But if I run the command above I get: [root@ovmgr1 ~]# yum update ovirt\*setup\* Last metadata expiration check: 0:39:59 ago on Wed 11 Nov 2020 09:02:05 AM CET. Error: Problem 1: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 2: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-disaster-recovery-1.3.0-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 3: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-cinderlib-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-cinderlib-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-engine-setup-1.2.4-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 4: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-imageio-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 5: package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.3.11-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine = 4.4.3.11-1.el8, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-image-template-1.2.2-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 6: problem with installed package ovirt-engine-4.4.2.6-1.el8.noarch - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-infra-1.2.2-1.el8.noarch Problem 7: problem with installed package ovirt-engine-ui-extensions-1.2.3-1.el8.noarch - package ovirt-engine-ui-extensions-1.2.3-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.2-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-manageiq-1.2.1-1.el8.noarch Problem 8: problem with installed package ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.11-1.el8.noarch requires ovirt-engine >= 4.4.0, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.10-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.10-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.3-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.3-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.4-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.4-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.5-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.5-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.6-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.6-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.7-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.7-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.8-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.8-1.el8, but none of the providers can be installed - package ovirt-engine-setup-plugin-ovirt-engine-4.4.3.9-1.el8.noarch requires ovirt-engine-setup-plugin-ovirt-engine-common = 4.4.3.9-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.2.6-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.10-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.3-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.4-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.5-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.6-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.7-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.8-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - cannot install both ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.9-1.el8.noarch and ovirt-engine-setup-plugin-ovirt-engine-common-4.4.3.11-1.el8.noarch - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-engine-setup-plugin-ovirt-engine-common-4.4.2.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-repositories-1.2.5-1.el8.noarch - package ovirt-engine-4.4.0.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.1-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.2-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.1.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.10-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.11-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.3-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.8-1.el8.noarch is filtered out by exclude filtering - package ovirt-engine-4.4.3.9-1.el8.noarch is filtered out by exclude filtering Problem 9: problem with installed package ovirt-engine-webadmin-portal-4.4.2.6-1.el8.noarch - package ovirt-engine-webadmin-portal-4.4.2.6-1.el8.noarch requires ovirt-engine = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-roles-1.2.3-1.el8.noarch Problem 10: problem with installed package ovirt-engine-tools-4.4.2.6-1.el8.noarch - package ovirt-engine-tools-4.4.2.6-1.el8.noarch requires ovirt-engine = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-shutdown-env-1.1.0-1.el8.noarch Problem 11: problem with installed package ovirt-engine-restapi-4.4.2.6-1.el8.noarch - package ovirt-engine-restapi-4.4.2.6-1.el8.noarch requires ovirt-engine = 4.4.2.6-1.el8, but none of the providers can be installed - package ovirt-engine-4.4.2.6-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-roles provided by ovirt-ansible-roles-1.2.3-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-vm-infra-1.2.3-1.el8.noarch (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) [root@ovmgr1 ~]# Thanks, Gianluca

4 years, 5 months

4
12
0 / 0

[ANN] oVirt 4.4.4 First Release Candidate is now available for testing

by Lev Veyde

oVirt 4.4.4 First Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.4 First Release Candidate for testing, as of November 12th, 2020. This update is the fourth in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA or later should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.4 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.4 (redeploy in case of already being on 4.4.4). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. 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.4 release highlights: http://www.ovirt.org/release/4.4.4/ * 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.4/ [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, 5 months

1
0
0 / 0

Re: sshd_config AuthorizedKeysFile

by Yedidyah Bar David

On Thu, Nov 12, 2020 at 11:44 AM Angus Clarke <angus(a)charworth.com> wrote: > > Righto > > For sure the ssh-copy-id is not happy either - in 20something years I've never used this before, I've always just manipulated files. > > I did start raising a bug ... missed some field, had to click back and lost all the previously inputted information - I forgot about this ... > > > Overall, tracing the issue is the thing that took too long, there was some message in the hosted-engine-deployment logs (one of the logs from the engine VM itself) which said something like "check you ssh host keys" (sorry, I've lost that information now) - it would have been useful to see it say something about editing the file /root/.ssh/authorized_keys on the KVM host prior to this. > > I didn't spend too long debugging the kvm-add-host-to-cluster issue - I didn't find too much in the way of obvious errors in logs on the 2nd KVM host for that either; rather - having just realised and resolved the hosted-engine deployment issue - I guessed the same response to the add-kvm-host to cluster issue which resolved that too. > > So maybe a bit of extra logging on the matter would be a great way forwards, or with such few use cases (am I really the only one to manipulate AuthorizedKeysFile? - wow!) then no action at all might be appropriate. If you still have the logs, please file a bug and attach them, and perhaps point out what you'd expect there that is missing (or just let us look at them, and if we decide that the information there is enough, we'll ask you, after finding the most relevant line). Generally speaking, and assuming your only problem was in "Add host to engine" flow (specifically also during hosted-engine deploy), you should find these logs in the _engine_ machine, in /var/log/ovirt-engine (and subdirs). The deploy process also tries to copy these logs to the _host_, under /var/log/ovirt-hosted-engine-setup, and this part was enhanced somewhat in 4.4.3 (see https://bugzilla.redhat.com/1844965 ). Best regards, > > Cheers > Angus > > # ls .ssh > ls: cannot access .ssh: No such file or directory > # ssh-copy-id server2 > > /usr/bin/ssh-copy-id: ERROR: failed to open ID file '/root/.pub': No such file or directory > (to install the contents of '/root/.pub' anyway, look at the -f option) > > ________________________________ > From: Martin Perina <mperina(a)redhat.com> > Sent: 12 November 2020 09:43 > To: Angus Clarke <angus(a)charworth.com> > Cc: users(a)ovirt.org <users(a)ovirt.org>; Dana Elfassy <delfassy(a)redhat.com>; Yedidyah Bar David <didi(a)redhat.com> > Subject: Re: [ovirt-users] sshd_config AuthorizedKeysFile > > Hi, > > could you please try if ssh-copy-id works with your non-standard sshd configuration? Because last time I've checked I haven't noticed that behavior and keys were always added to $HOME/.ssh/authorized_keys > > So feel free to create a bug for that, but up until now you are the first user using this non-standard configuration ... > > Regards, > Martin > > On Thu, Nov 12, 2020 at 9:00 AM Angus Clarke <angus(a)charworth.com> wrote: > > Hello > > Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 > > In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. > > > The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. > > Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. > > > Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys. > > HTH > Angus > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/UMJ4Y622RAL... > > > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. -- Didi

4 years, 5 months

1
0
0 / 0

Re: sshd_config AuthorizedKeysFile

by Martin Perina

Hi, could you please try if ssh-copy-id works with your non-standard sshd configuration? Because last time I've checked I haven't noticed that behavior and keys were always added to $HOME/.ssh/authorized_keys So feel free to create a bug for that, but up until now you are the first user using this non-standard configuration ... Regards, Martin On Thu, Nov 12, 2020 at 9:00 AM Angus Clarke <angus(a)charworth.com> wrote: > Hello > > Sharing for anyone who needs it, this was carried out on OL7, they use > ovirt 4.3 > > In short: both the hosted-engine deployment routine and the host add to > cluster routine distribute public ssh keys to /root/.ssh/authorized_keys > regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both > routines fail if AuthorizedKeysfile is not default. > > > The hosted-engine setup assumes AuthorizedKeysFile to be default > (~/.ssh/authorized_keys) and creates a public key there, instead of > following the sshd_config directive. The setup fails on the back of this. > > Once I commented this out of sshd_config file (assumes default) and > restarted sshd on the KVM host that was running the hosted-engine > deployment, the hosted-engine setup completed successfully. > > > Similarly, I could not deploy a second KVM host to the compute cluster > until I had altered this setting on that 2nd KVM host - presumably that > process has some similar routine that unwittingly writes keys to > ~/.ssh/authorized_keys. > > HTH > Angus > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/UMJ4Y622RAL... > -- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.

4 years, 5 months

2
1
0 / 0

Re: Cluster compatibility version 4.5 on oVirt 4.4

by Christopher Law

I should have pointed out that in my case the hosted engine failed to install. After the Local VM came up the host was marked as non-operational because the cluster (which I had given a custom name via ansible input) was set to compatibility 4.5 and was not changeable. No idea why the cluster was created at 4.5 if that is not supposed to be available yet or marked for some sort of future release. This caused the host to be non-operational with a warning that the “host” needed upgrading, so perhaps it’s a slightly different issue to that faced below. If you have faced this issue though I would appreciated some advice on how to resolve it. I noticed the default cluster was marked as 4.4. My plan is therefore to re-install the hosted engine and use the “Default” datacentre and cluster names and changes these later. From: Christopher Law <chris(a)chrislaw.me> Sent: 12 November 2020 09:21 To: Ritesh Chikatwar <rchikatw(a)redhat.com>; shadow emy <shadow.emy1(a)gmail.com> Cc: users <users(a)ovirt.org> Subject: [ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4 I’ve also faced this issue, which is surprising since I used an ovirt node download for 4.4. How did you resolve it? How can you upgrade to CentOS 8.3 or downgrade the cluster? Thanks, Chris. From: Ritesh Chikatwar <rchikatw(a)redhat.com<mailto:rchikatw@redhat.com>> Sent: 12 November 2020 05:10 To: shadow emy <shadow.emy1(a)gmail.com<mailto:shadow.emy1@gmail.com>> Cc: users <users(a)ovirt.org<mailto:users@ovirt.org>> Subject: [ovirt-users] Re: Cluster compatibility version 4.5 on oVirt 4.4 Hello, To upgrade to cluster 4.5 you need a 8.3 host. I guess still CentOS 8.3 is not available. I am not sure on CentOS 8.3 availability. If it's available please make sure your host is upgraded to 8.3 . On Thu, Nov 12, 2020, 5:38 AM shadow emy <shadow.emy1(a)gmail.com<mailto:shadow.emy1@gmail.com>> wrote: Just to confirm i face similar problem. Yes i saw that warning too : "Upgrade Cluster Compatibility Level" to upgrade the Cluster to version 4.5. Though when i try to do that there are a lot of errors. In GUI : Error while executing action: Cannot change Cluster Compatibility Version to higher version when there are active Hosts with lower version. -Please move Host host1, host2, host3 with lower version to maintenance first. In engine.log : WARN [org.ovirt.engine.core.bll.UpdateClusterCommand] (default task-163) [2c681b74-8666-4f2f-b2e0-6b20e98f417e] Validation of action 'UpdateCluster' failed for user admin@internal-authz. Reasons: VAR__TYPE__CLUSTER,VAR__ACTION__UPDATE,$host host1, host2, host3,CLUSTER_CANNOT_UPDATE_COMPATIBILITY_VERSION_WITH_LOWER_HOSTS I did not find any documentation for 4.5 cluster compatibility, so i like as well to understand why is that option present there. It will be used when ovirt 4.5.x will be released ? _______________________________________________ Users mailing list -- users(a)ovirt.org<mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org<mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3UGQ6HPT2HT...

4 years, 5 months

1
0
0 / 0

Cluster compatibility version 4.5 on oVirt 4.4

by tferic＠swissonline.ch

Hi Today, I upgraded oVirt from 4.3 to 4.4.3. After the upgrade, I upgraded the compatibility from 4.3 to 4.4. I noticed that the cluster config is offering me another upgrade of the compatibility to version 4.5. Up until now, I was under the impression that the compatibility version must match the oVirt version. I am now reluctant to upgrade the compatibility to 4.5, while my oVirt version is still at 4.4 (there is no oVirt 4.5 at this time). Is it safe to upgrade the compatibility in any case, or are there certain circumstances, where we should refrain from upgrading it? I wasn't able to find anything in the documentation. Kind regards Toni Feric

4 years, 5 months

4
3
0 / 0

Re: sshd_config AuthorizedKeysFile

by Yedidyah Bar David

On Thu, Nov 12, 2020 at 10:01 AM Angus Clarke <angus(a)charworth.com> wrote: > > Hello > > Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 > > In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. > > > The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. > > Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. > > > Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys. Thanks for the report. Would you like to open one or two bugs about this? I think it's just bug, though - from searching relevant source - in the code adding a host to the engine. This code is also used during hosted-engine deploy. We also have code there to add lines to this file on the appliance (engine vm image), but I do not believe users will work so hard as to update the image before deploy. So one bug is probably enough. To make sure, please include there all relevant details about how "they" (your customer?) configure their machines - e.g. is it only during their installation (image/PXE/etc.) or also routinely (puppet etc.) I admit I am not sure what the expected behavior should be, though: An admin can run sshd with a custom file. So should we also check that? Perhaps it's enough if we allow the admin to set a custom location also for oVirt, instead of trying to guess. And make sure that the failure error message is clear and unique enough so that people searching the net for it find your bug, so can find how to configure it :-) Best regards, -- Didi

4 years, 5 months

1
0
0 / 0

sshd_config AuthorizedKeysFile

by Angus Clarke

Hello Sharing for anyone who needs it, this was carried out on OL7, they use ovirt 4.3 In short: both the hosted-engine deployment routine and the host add to cluster routine distribute public ssh keys to /root/.ssh/authorized_keys regardless of the AuthorizedKeysFile setting in /etc/ssh/sshd_config. Both routines fail if AuthorizedKeysfile is not default. The hosted-engine setup assumes AuthorizedKeysFile to be default (~/.ssh/authorized_keys) and creates a public key there, instead of following the sshd_config directive. The setup fails on the back of this. Once I commented this out of sshd_config file (assumes default) and restarted sshd on the KVM host that was running the hosted-engine deployment, the hosted-engine setup completed successfully. Similarly, I could not deploy a second KVM host to the compute cluster until I had altered this setting on that 2nd KVM host - presumably that process has some similar routine that unwittingly writes keys to ~/.ssh/authorized_keys. HTH Angus

4 years, 5 months

1
0
0 / 0

Upgrade OVIRT from 3.6 to 4.3

by Miguel Angel Costas

Hi Guys! I need to upgrade from 3.6 to 4.3 and I have a doubt. Do I need to restard VMs for each upgrade (DC Compatibilty 1° 4.0 - 2° 4.1 - 3° 4.2 and 4° 4.3) or can modify the compatibilty from 3.6 to 4.2 and restart the vms in this only step. Best regards

4 years, 5 months

2
1
0 / 0

Adding iscsi issue 4.3

by thilburn＠generalpacific.com

When connecting an iscsi connection from an array I get the following popup "A database error occurred. Please contact your system administrator." I have checked everything and the only device connected right now is the single host in the datacenter. If I check the box " Approve operation" and click Ok it will error out with "A database error occurred. Please contact your system administrator." This is a new volume and no other machine is connected to this LUN or array. Below is from the vdsm log 2020-11-11 10:42:26,087-0800 INFO (jsonrpc/0) [vdsm.api] START getDeviceList(storageType=3, guids=[u'32021001378a6ddad'], checkStatus=True, options={}) from=::ffff:XXXXXX,46208, flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:48) 2020-11-11 10:42:26,650-0800 INFO (jsonrpc/0) [storage.LVM] Overriding read_only mode current=True override=False (lvm:398) 2020-11-11 10:42:26,822-0800 INFO (jsonrpc/0) [vdsm.api] FINISH getDeviceList return={'devList': [{'status': 'used', 'vendorID': 'ETIUSA', 'capacity': '3999688294400', 'fwrev': '10E', 'discard_zeroes_data': 0, 'vgUUID': '', 'pvsize': '', 'pathlist': [{'connection': u'10.87.172.100', 'iqn': u'XXXXXX.XXXXXX.XXXXXX:storage3', 'portal': '0', 'port': '3260', 'initiatorname': u'default'}], 'logicalblocksize': '512', 'discard_max_bytes': 0, 'pathstatus': [{'type': 'iSCSI', 'physdev': 'sdc', 'capacity': '3999688294400', 'state': 'active', 'lun': '0'}], 'devtype': 'iSCSI', 'physicalblocksize': '512', 'pvUUID': '', 'serial': 'SETIUSA_UltraStorRS8IP4_2021001378A6DDAD', 'GUID': '32021001378a6ddad', 'productID': 'UltraStorRS8IP4'}]} from=::ffff:XXXXX,46208, flow_id=d09dbfd6-2256-48ad-8597-b6c581def1fd, task_id=67c17255-3ffb-4e8b-b6d3-a4e40836d12c (api:54) 2020-11-11 10:42:26,823-0800 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getDeviceList succeeded in 0.74 seconds (__init__:312) 2020-11-11 10:42:27,158-0800 INFO (jsonrpc/2) [api.host] START getAllVmStats() from=::1,48480 (api:48) 2020-11-11 10:42:27,159-0800 INFO (jsonrpc/2) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::1,48480 (api:54) 2020-11-11 10:42:27,159-0800 INFO (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2020-11-11 10:42:27,393-0800 INFO (jsonrpc/1) [api.host] START getAllVmStats() from=::ffff:XXXXX,46208 (api:48) 2020-11-11 10:42:27,394-0800 INFO (jsonrpc/1) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:XXXXX,46208 (api:54) 2020-11-11 10:42:27,394-0800 INFO (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2020-11-11 10:43:12,323-0800 INFO (jsonrpc/6) [vdsm.api] START createVG(vgname=u'35e95355-75db-4640-bf99-e576b9ce39aa', devlist=[u'32021001378a6ddad'], force=True, options=None) from=::ffff:XXXXX,46208, flow_id=2c973734, task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:48) 2020-11-11 10:43:12,348-0800 INFO (jsonrpc/6) [storage.LVM] Overriding read_only mode current=True override=False (lvm:398) 2020-11-11 10:43:12,409-0800 INFO (jsonrpc/4) [api.host] START getAllVmStats() from=::ffff:XXXXXX,46208 (api:48) 2020-11-11 10:43:12,410-0800 INFO (jsonrpc/4) [api.host] FINISH getAllVmStats return={'status': {'message': 'Done', 'code': 0}, 'statsList': (suppressed)} from=::ffff:XXXXXXX,46208 (api:54) 2020-11-11 10:43:12,410-0800 INFO (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC call Host.getAllVmStats succeeded in 0.00 seconds (__init__:312) 2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] pvcreate failed with rc=5 (lvm:988) 2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.LVM] [], [' Device /dev/mapper/32021001378a6ddad excluded by a filter.'] (lvm:989) 2020-11-11 10:43:12,520-0800 INFO (jsonrpc/6) [vdsm.api] FINISH createVG error=Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) from=::ffff:XXXXXX,46208, flow_id=2c973734, task_id=91f2ab5b-017a-4c88-aa45-ece3bd920ce0 (api:52) 2020-11-11 10:43:12,520-0800 ERROR (jsonrpc/6) [storage.TaskManager.Task] (Task='91f2ab5b-017a-4c88-aa45-ece3bd920ce0') Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in createVG File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2146, in createVG force=force) File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 1256, in createVG _initpvs(pvs, metadataSize, force) File "/usr/lib/python2.7/site-packages/vdsm/storage/lvm.py", line 990, in _initpvs raise se.PhysDevInitializationError(str(devices)) PhysDevInitializationError: Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) 2020-11-11 10:43:12,520-0800 INFO (jsonrpc/6) [storage.TaskManager.Task] (Task='91f2ab5b-017a-4c88-aa45-ece3bd920ce0') aborting: Task is aborted: 'Failed to initialize physical device: ("[u\'/dev/mapper/32021001378a6ddad\']",)' - code 601 (task:1181) 2020-11-11 10:43:12,521-0800 ERROR (jsonrpc/6) [storage.Dispatcher] FINISH createVG error=Failed to initialize physical device: ("[u'/dev/mapper/32021001378a6ddad']",) (dispatcher:83) 2020-11-11 10:43:12,521-0800 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call LVMVolumeGroup.create failed (error 601) in 0.20 seconds (__init__:312)

4 years, 5 months

1
1
0 / 0

Dependencies failure when upgrading from version 4.4.2 to 4.4.3

by jorgevisentini＠gmail.com

When I update the Engine and Host, many dependencies are missing, as shown by the host error log: Error: Problem 1: package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires ovirt-ansible-engine-setup >= 1.1.9, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-engine-setup provided by ovirt-ansible-engine-setup-1.2.4-1.el8.noarch - cannot install the best update candidate for package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch - cannot install the best update candidate for package ovirt-ansible-engine-setup-1.2.4-1.el8.noarch Problem 2: package ovirt-host-4.4.1-4.el8.x86_64 requires ovirt-hosted-engine-setup, but none of the providers can be installed - package ovirt-hosted-engine-setup-2.4.6-1.el8.noarch requires ovirt-ansible-hosted-engine-setup >= 1.0.34, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-hosted-engine-setup provided by ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch - cannot install the best update candidate for package ovirt-host-4.4.1-4.el8.x86_64 - cannot install the best update candidate for package ovirt-ansible-hosted-engine-setup-1.1.8-1.el8.noarch - package ovirt-ansible-hosted-engine-setup-1.1.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-ansible-hosted-engine-setup-1.1.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-ansible-hosted-engine-setup-1.1.6-1.el8.noarch is filtered out by exclude filtering - package ovirt-ansible-hosted-engine-setup-1.1.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.4-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.5-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.7-1.el8.noarch is filtered out by exclude filtering - package ovirt-hosted-engine-setup-2.4.8-1.el8.noarch is filtered out by exclude filtering (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

4 years, 5 months

3
3
0 / 0

Single Node HCI upgrade procedure from CentOS7/oVirt 4.3 to CentOS8/oVirt 4.4?

by thomas＠hoberg.net

I can hear you saying: "You did understand that single node HCI is just a toy, right?" For me the primary use of a single node HCI is adding some disaster resilience in small server edge type scenarios, where a three node HCI provides the fault tolerance: 3+1 with a bit of distance, warm or even cold stand-by, potentially manual switch and reduced workload in case disaster strikes. Of course, another 3nHCI would be better, but who gets that type of budget, right? What I am trying say: If you want oVirt to gain market share, try to give HCI more love. And while you're at it, try to make expanding from 1nHCI to 3nHCI (and higher counts) a standard operational procedure to allow expanding a disaster stand-by into a production setup, while the original 3nHCI is being rebuilt. For me low-budget HCI is where oVirt has its biggest competitive advantage against vSan and Nutanix, so please don't treat the HCI/gluster variant like an unwanted child any more. In the mean-time OVA imports (from 4.3.10 exports) on my 4.4.2 1nHCI fail again, which I'll report separately.

4 years, 5 months

2
1
0 / 0

Upgrade Problem oVirt engine 4.4.1.8-1.el8 -> 4.4.3

by Andrei Verovski

Hi ! I’m trying to upgrade oVirt engine 4.4.1.8-1.el8 to the latest 4.4.3, running as KVM appliance (not hosted engine). This sequence of commands yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm engine-upgrade-check yum update ovirt\*setup\* Results in a long list of dependency errors, short excerpt below. Looks like something (e.g. repo) is missing. How to fix this? Thanks in advance. ————— LOG ---------- Problem 1: problem with installed package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed Problem 2: package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-engine-ui-extensions >= 1.0.4, but none of the providers can be installed - package ovirt-engine-ui-extensions-1.2.2-1.el8.noarch requires ovirt-ansible-cluster-upgrade >= 1.1.12, but none of the providers can be installed - package ovirt-engine-4.4.1.8-1.el8.noarch requires ovirt-ansible-roles >= 1.2.0, but none of the providers can be installed - package ovirt-ansible-collection-1.2.1-1.el8.noarch obsoletes ovirt-ansible-cluster-upgrade provided by ovirt-ansible-cluster-upgrade-1.2.3-1.el8.noarch

4 years, 5 months

3
3
0 / 0

Cluster with Hosted Engine update BIOS Setting Ovirt 4.4.3

by scrik787＠gmail.com

I changed the type in the cluster and now my hosted-engine machine won't start!. There are no backups. How can I manually change the parameters of the machine from under the roof so that it starts and I can restore ovirt to work Error in logs: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port VDSM.log https://pastebin.com/vsAKy9rX

4 years, 5 months

2
1
0 / 0

Host NonResponsive after migration to oVirt 4.4

by tferic＠swissonline.ch

Hi I am looking for help after my oVirt upgrade failed. I have upgraded from ovirt 4.3 to 4.4 following the instructions here: https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3 <https://www.ovirt.org/documentation/upgrade_guide/#Upgrading_from_4-3> It's a single-host (standalone engine) test environment. I wiped CentOS 7 and reinstalled a fresh CentOS 8. I installed the oVirt 4.4 repo and all the necessary software packets. I used `engine-backup --mode=restore --file=/tmp/ovirt-engine-pre-upgrade.backup --provision-all-databases` from a backup file I created before I started the upgrade. After the restore, I ran `engine-setup`. I did not get any errors during any of these steps on the console. So the upgrade could be considered successful from that perspective. After the upgrade, I login to the ovirt admin portal, and I try to "Activate" my host (was set to "Maintenance" mode before upgrade). The Activation fails with error "NonResponsive" in the GUI. Under the "bell" icon, I find the Event "Host nuc1.feric.ch is non responsive.” In /var/log/ovirt-engine/engine.log, I find the following error: ``` 2020-11-09 23:12:21,080+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesAsyncVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-47) [] Command 'GetCapabilitiesAsyncVDSCommand(HostName = nuc1.feric.ch, VdsIdAndVdsVDSCommandParametersBase:{hostId='d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb', vds=‘Host[nuc1.feric.h,d7c30cc0-ac59-4cf3-a1e7-b9fae9db83fb]'})' execution failed: java.net.ConnectException: Connection refused ``` `systemctl status ovirt-engine` shows that the engine is running. I am able to reboot the host from the oVirt GUI directly. Does anyone have an idea how to proceed? Many thanks Toni

4 years, 5 months

3
7
0 / 0

Clone a VM in the User Portal

by Nicolás

Hi, We're using oVirt 4.3.8, having an organization that intensively uses the User Portal. After upgrading from 4.2, we've noticed that cloning a VM from within the User Portal is not possible anymore. In our case, this feature was heavily used by hundreds of students deploying their VMs. Is this feature in the roadmap yet? If not, do you consider it useful to open a RFE? Thank you. Regards, Nico

4 years, 5 months

3
6
0 / 0

Cannot restore engine from 4.3.9 to 4.4.3

by tferic＠swissonline.ch

Hi I just tried to restore my engine backup taken from release 4.3.9.4 to a newer oVirt installation release 4.4.3.11. The restore process fails with a FATAL error. I was under the impression that backups from all 4.3 versions were supposed to be restorable on 4.4. My installation is a single-box all-in-one (Standalone Engine installed together with oVirt node). # engine-backup --mode=restore --file=/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup --provision-all-databases Start of engine-backup with mode 'restore' scope: all archive file: /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup log file: /var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log Preparing to restore: - Unpacking file '/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup' FATAL: Backup was created by version '4.3.9.4' and can not be restored using the installed version 4.4.3.11 Complete content of the restore log file: 2020-11-11 03:15:00 23143: Start of engine-backup mode restore scope all file /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup 2020-11-11 03:15:00 23143: OUTPUT: Start of engine-backup with mode 'restore' 2020-11-11 03:15:00 23143: OUTPUT: scope: all 2020-11-11 03:15:00 23143: OUTPUT: archive file: /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup 2020-11-11 03:15:00 23143: OUTPUT: log file: /var/log/ovirt-engine-backup/ovirt-engine-restore-20201111031500.log 2020-11-11 03:15:00 23143: OUTPUT: Preparing to restore: 2020-11-11 03:15:01 23143: OUTPUT: - Unpacking file '/exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup' 2020-11-11 03:15:01 23143: Opening tarball /exports/data-t2/backups/ovirt-engine-backup-20201018124037_pre-upgrade.backup to /tmp/engine-backup.UAcLerghwY 2020-11-11 03:15:01 23143: Verifying hash 2020-11-11 03:15:01 23143: Verifying version 2020-11-11 03:15:01 23143: FATAL: Backup was created by version '4.3.9.4' and can not be restored using the installed version 4.4.3.11 regards, Toni Feric

4 years, 5 months

2
1
0 / 0

Problem with Cluster-wise BIOS Settings in oVirt 4.4

by Rodrigo G. López

Hi all, We are running an oVirt 4.4 Hosted Engine as a VM, and after changing the Cluster's BIOS type from Q35 with Legacy BIOS (the default one after installation) to Preexistent, the VM fails with the following error: XML error: The device at PCI address 0000:00:02.0 cannot be plugged into the PCI controller with index='0'. It requires a controller that accepts a pcie-root-port. We need it so that we can run imported VMs from a previous version of oVirt, namely 4.0. Applying the BIOS settings individually works but as an attempt to generalize the settings we decided to apply it to the full cluster. Tell me if you need more data. Cheers, -rodri

4 years, 5 months

4
6
0 / 0

oVirt 4.4.2 MS Windows 10 sysprep floppy

by ozmen62＠hotmail.com

Hi, I've cretated a template which has sysprep. Every document about sysprep says use "Attach Floppy" , but we know this function has been disabled/deprecated So, when i use Run One, attach windows cdrom and put in it definitions (domain name, user credentials etc) , nothing happens. I also have correct properties and sysprep files in engine Just windows boot like it is new machine and ask lots of questions for prepare itself. Would someone please explain this? How can i run sysprep correctly?

4 years, 5 months

4
11
0 / 0

setting routing rules for guests?

by yam yam

Hello everyone! I'm wondering there is any feature like applying routing rules for VM to reach the external network (and vice versa). and I guess it's different according to using external provider(OVN). if not, how to users usually assign floating IP to VM?? Thanks Sincerely,

4 years, 5 months

3
7
0 / 0

Re: Clone a VM in the User Portal

by Arik Hadas

On Tue, Nov 10, 2020 at 10:10 PM tferic(a)swissonline.ch < tferic(a)swissonline.ch> wrote: > Cloning VM's is a core feature of virtualization. > > I remember having cloned VM's back in the 90's with the free VMware > version 0.9. > > My main use case ever since is cloning fully configured production servers > into a testservers, for isolated testing. > > Why would a hypervisor not offer cloning, when it is possible and useful? > > regards, Toni > (Added users(a)ovirt.org back) Sure, it can be handy in some cases - that's why we've implemented it in oVirt and enhance it in 4.4.3 (for running VMs). But I wouldn't expect it to be commonly used via the user portal, that's why I am interested in the use-case. > > On 10.11.20 16:22, Arik Hadas wrote: > > > > On Tue, Nov 10, 2020 at 4:37 PM Nicolás <nicolas(a)devels.es> wrote: > >> Hi Arik, >> >> El 10/11/20 a las 13:21, Arik Hadas escribió: >> >> >> >> On Tue, Nov 10, 2020 at 3:08 PM Nicolás <nicolas(a)devels.es> wrote: >> >>> Hi Sharon, >>> >>> Thanks for the reply! I've opened [1], so hopefully someone will be able >>> to implement it. >>> >>> Regards, >>> >>> Nico >>> >>> [1]: https://github.com/oVirt/ovirt-site/issues/2389 >>> >>> El 10/11/20 a las 11:38, Sharon Gratch escribió: >>> >>> Hi, >>> >>> This feature of cloning a VM was indeed part of the old User Portal and >>> you are right that it's not supported by the newer VM Portal (since oVirt >>> 4.3). >>> It seemed that this wasn't required by VM Portal users (no user >>> complained up till now) and that's why we omitted it and it's not part of >>> our current roadmap to implement it as well. >>> >>> Nevertheless, there is no real reason not to include that ability as >>> part of VM Portal, so you are most welcome to open an issue on >>> https://github.com/oVirt/ovirt-web-ui/issues >>> <https://github.com/oVirt/ovirt-site/issues> >>> and you can push a fix yourself if you have time (or someone else from >>> the community) :-) >>> >>> Thanks! >>> Sharon >>> >>> On Fri, Nov 6, 2020 at 11:06 AM Nicolás <nicolas(a)devels.es> wrote: >>> >>>> Hi, >>>> >>>> We're using oVirt 4.3.8, having an organization that intensively uses >>>> the User Portal. After upgrading from 4.2, we've noticed that cloning a >>>> VM from within the User Portal is not possible anymore. In our case, >>>> this feature was heavily used by hundreds of students deploying their >>>> VMs. >>>> >>> >> Out of curiosity, why cloning a VM and not provisioning the VMs from >> template(s)? >> >> >> >> Most of our students are IT-related, and their professors want to teach >> them the procedure to deploy a VM from scratch. Some other courses surely >> deploy their VMs from a template as they are not that IT oriented and they >> just want to have a working VM instead of building it from scratch. We have >> a lot of casuistry, but in our case about 400~500 students would very >> welcome having back the clone option. >> > > Thanks Nicolás. > I'd say that even for the IT-related students it may make more sense to > provision VMs from templates instead of cloning VMs - > so you want them to deploy VMs from scratch, which means starting with a > VM that is based on the blank template, add disk(s) and other devices, > install and configure the guest and such; and then the students would use > clone-VM to duplicate the VM they just prepared, right? > Why would you want them to clone the VM rather than creating a template > out of this VM and provision further VMs from that template with > thin-provisioned disks? > > >> >> Regards, >> >> Nico >> >> >>>> Is this feature in the roadmap yet? If not, do you consider it useful >>>> to >>>> open a RFE? >>>> >>>> Thank you. >>>> >>>> Regards, >>>> >>>> Nico >>>> _______________________________________________ >>>> Users mailing list -- users(a)ovirt.org >>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/HFMFJRV3AC3... >>>> >>> >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to users-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RUEW52WZUD2... >>> >> >> > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QXPS6FCRT66... > >

4 years, 5 months

1
0
0 / 0

[ANN] oVirt 4.4.3 is now generally available

by Sandro Bonazzola

oVirt 4.4.3 is now generally available The oVirt project is excited to announce the general availability of oVirt 4.4.3 , as of November 10th, 2020. This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics, as compared to oVirt 4.3. Important notes before you install / upgrade Please note that oVirt 4.4 only supports clusters and data centers with compatibility version 4.2 and above. If clusters or data centers are running with an older compatibility version, you need to upgrade them to at least 4.2 (4.3 is recommended). Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7 are no longer supported. For example, the megaraid_sas driver is removed. If you use Enterprise Linux 8 hosts you can try to provide the necessary drivers for the deprecated hardware using the DUD method (See the users’ mailing list thread on this at https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXE... ) Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. What’s new in oVirt 4.4.3 Release? This update is the third in a series of stabilization updates to the 4.4 series. This release is available now on x86_64 architecture for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: - Red Hat Enterprise Linux 8.2 / 8.3 - CentOS Linux (or similar) 8.2 - CentOS Stream (tech preview) Please note that this release introduces cluster compatibility level 4.5 which is supported only with Red Hat Enterprise Linux 8.3 or equivalent. oVirt Node and Appliance have been updated, including: - oVirt 4.4.3: https://www.ovirt.org/release/4.4.3/ - Ansible 2.9.15: https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v... - Glusterfs 7.8: https://docs.gluster.org/en/latest/release-notes/7.8/ 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 will be available soon for CentOS Linux 8 Additional resources: - Read more about the oVirt 4.4.3 release highlights: https://www.ovirt.org/release/4.4.3/ - 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] https://www.ovirt.org/release/4.4.3/ <https://www.ovirt.org/release/4.4.3/> [2] https://resources.ovirt.org/pub/ovirt-4.4/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

4 years, 5 months

1
0
0 / 0

VM's gone to unknown state

by hjadavalluva＠ukaachen.de

Hello, I have an issue with ovirt 4.3 console. The exact issue is, except hosted engine, all other VM's gone to unknown state. I wonder what's the problem is? And how bring back the VM's to normal state. I can see that nothing is enable (for instance, acktivate option, maintaiance option, etc). Can anyone guide me please in this? Thanks in advance! Best Regards, Hariharan

4 years, 5 months

3
9
0 / 0

Re: LiveStorageMigration fail

by Christoph Köhler

yes, the output is: -[ RECORD 1 ]---------+------------------------------------- image_guid | 77af2f70-f3e3-4e69-a062-b0dd9970e9e3 creation_date | 2019-05-23 10:08:39+02 size | 348966092800 it_guid | 00000000-0000-0000-0000-000000000000 parentid | 00000000-0000-0000-0000-000000000000 imagestatus | 1 lastmodified | 2020-11-09 15:39:56.22+01 vm_snapshot_id | edade1d1-05ce-46a4-9929-984e5ad3e025 volume_type | 2 volume_format | 4 image_group_id | 02240cf3-65b6-487c-b5af-c266a1dd18f8 _create_date | 2018-01-11 17:31:50.075047+01 _update_date | 2020-11-09 15:41:01.008245+01 active | t volume_classification | 1 qcow_compat | 2 On 09.11.20 17:23, Benny Zlotnik wrote: > Can you share the output of: > $ psql -U engine -d engine -c "\x on" -c "SELECT * FROM images where > image_group_id = '02240cf3-65b6-487c-b5af-c266a1dd18f8';" > > On Mon, Nov 9, 2020 at 5:18 PM Christoph Köhler > <koehler(a)luis.uni-hannover.de <mailto:koehler@luis.uni-hannover.de>> wrote: > > yes sure, here they are: > > On 09.11.20 15:30, Benny Zlotnik wrote: > > Can you send me the full logs with the failure (vdsm+engine)? > > > > On Mon, Nov 9, 2020 at 4:26 PM Christoph Köhler > > <koehler(a)luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de> > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de>>> wrote: > > > > engine runs with 4.3.10.4-1 > > and yes, the message is persistently the same, so I cannot > migrate this > > disk. > > > > > > > > On 09.11.20 15:10, Benny Zlotnik wrote: > > > Which version are you using? > > > Did this happen more than once for the same disk? > > > A similar bug was fixed in 4.3.10.1[1] > > > There is another bug with a similar symptom which occurs very > > rarely and > > > we were unable to reproduce it > > > > > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1758048 > > > > > > On Mon, Nov 9, 2020 at 3:57 PM Christoph Köhler > > > <koehler(a)luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de> > > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de>> > > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de> > > <mailto:koehler@luis.uni-hannover.de > <mailto:koehler@luis.uni-hannover.de>>>> wrote: > > > > > > Hello experts, > > > > > > perhaps someone has an idea about that error. It appears > when > > in try to > > > migrate a disk to another storage, and this live. > Generally it > > works > > > good but - this is the log snippet: > > > > > > HSMGetAllTasksStatusesVDS failed: Error during > destination image > > > manipulation: > u"image=02240cf3-65b6-487c-b5af-c266a1dd18f8, dest > > > domain=3c4fbbfe-6796-4007-87ab-d7f205b7fae3: msg=Invalid > > parameter: > > > 'capacity=134217728000'" > > > > > > Surely the is enough space on the target domain for this > operation > > > (~4TB). > > > > > > Any ideas..? > > > > > > Greetings from > > > Chris > > > _______________________________________________ > > > Users mailing list -- users(a)ovirt.org > <mailto:users@ovirt.org> <mailto:users@ovirt.org > <mailto:users@ovirt.org>> > > <mailto:users@ovirt.org <mailto:users@ovirt.org> > <mailto:users@ovirt.org <mailto:users@ovirt.org>>> > > > To unsubscribe send an email to users-leave(a)ovirt.org > <mailto:users-leave@ovirt.org> > > <mailto:users-leave@ovirt.org <mailto:users-leave@ovirt.org>> > > > <mailto:users-leave@ovirt.org > <mailto:users-leave@ovirt.org> <mailto:users-leave@ovirt.org > <mailto:users-leave@ovirt.org>>> > > > Privacy Statement: https://www.ovirt.org/privacy-policy.html > > > oVirt Code of Conduct: > > > https://www.ovirt.org/community/about/community-guidelines/ > > > List Archives: > > > > > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/6KT5HQXEFB477O7GW5KP4BJJUR5YBL6Q/ > > > > > >

4 years, 5 months

1
0
0 / 0

The Master data domain can't be activated

by Miguel Angel Costas

Hi all!! I had a terrible problem with my blade and I lost the 2 nodes. I have installed a new server as a node ( ovirt-node-iso-3.6-0.999.201608311021.el7.centos.iso) but for any reason the data domain don't start. It the same node version. The ovirt manager is 3.6.7 If I create a new datacenter I can attach a lv from the same lun with the problem.. Someone could help me.. I have been working to solve the problem fron the saturday.. Thanks!

4 years, 5 months

2
3
0 / 0

Cannot access ovirt engine

by suporte＠logicworks.pt

Hi, I was installing a VM and than I notice that cannot access the CD, after this could not access the engine anymore. The ovirt-engine service is running. But I have this error in the engine log: 2020-11-09 13:49:16,356Z ERROR [org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataServlet.CacheUpdate.Inventory] (EE-ManagedThreadFactory-default-Thread-5) [] Could not update the Inventory Cache: Error while running SQL query: org.ovirt.engine.ui.frontend.server.dashboard.DashboardDataException: Error while running SQL query ovirt-engine-dwh.log 2020-11-09 13:57:21|Yd4P7G|GUQ4i7|NlyWRj|OVIRT_ENGINE_DWH|SampleTimeKeepingJob|Default|5|tWarn|tWarn_1|Can not sample data, oVirt Engine is not updating the statistics. Please check your oVirt Engine status.|9704 ovirt-engine-4.3.4.3-1.el7.noarch ovirt-engine-dwh-setup-4.3.8-1.el7.noarch Any idea? Thanks -- Jose Ferradeira http://www.logicworks.pt

4 years, 5 months

2
4
0 / 0

Change compatibility level for data center/cluster, what exactly we are changing?

by Patrick Chiang

Hi all, From the procedure I learned at the last phase of upgrade, we should change compatibility level for data center/cluster, respectively. But may I know what exactly the settings we are changing - a config in a database or in a file? Actually my question is, are these changes can lead to any service downtime for "guest VM" or "Storage domain", "hypervisors"? Because lately my RHV 4.2 suffered a few network disconnections and that causes hosts to be fenced forcefully. I hope I can collect more info here to prepare for 4.2->4.3 upgrade. Thanks, Patrick Chiang

4 years, 5 months

1
0
0 / 0

LiveStorageMigration fail

by Christoph Köhler

Hello experts, perhaps someone has an idea about that error. It appears when in try to migrate a disk to another storage, and this live. Generally it works good but - this is the log snippet: HSMGetAllTasksStatusesVDS failed: Error during destination image manipulation: u"image=02240cf3-65b6-487c-b5af-c266a1dd18f8, dest domain=3c4fbbfe-6796-4007-87ab-d7f205b7fae3: msg=Invalid parameter: 'capacity=134217728000'" Surely the is enough space on the target domain for this operation (~4TB). Any ideas..? Greetings from Chris

4 years, 5 months

2
1
0 / 0

ovirt guest agent ubuntu 16.04.6 LTS

by suporte＠logicworks.pt

What is the best way to install ovirt guest on Ubuntu 16.04.6? What I did: # apt-get install ovirt-guest-agent I changed value in /etc/ovirt-guest-agent.conf to look like: [virtio] # device = /dev/virtio-ports/com.redhat.rhevm.vdsm device = /dev/virtio-ports/ovirt-guest-agent.0 # systemctl start ovirt-guest-agent Error on the log: OSError: [Errno 13] Permission denied: '/dev/virtio-ports/ovirt-guest-agent.0 Than I set the owner and group # chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0 Than I was able to start the agent # systemctl status ovirt-guest-agent ● ovirt-guest-agent.service - oVirt Guest Agent Loaded: loaded (/lib/systemd/system/ovirt-guest-agent.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-10-31 19:50:03 WET; 9min ago Process: 6531 ExecStartPre=/bin/chown ovirtagent:ovirtagent /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 6527 ExecStartPre=/bin/touch /run/ovirt-guest-agent.pid (code=exited, status=0/SUCCESS) Process: 6524 ExecStartPre=/sbin/modprobe virtio_console (code=exited, status=0/SUCCESS) Main PID: 6537 (python) Tasks: 3 Memory: 68.7M CPU: 5.462s CGroup: /system.slice/ovirt-guest-agent.service └─6537 /usr/bin/python /usr/share/ovirt-guest-agent/ovirt-guest-agent.py Oct 31 19:52:05 alfa.acloud.pt python[6537]: [100B blob data] Oct 31 19:54:06 alfa.acloud.pt python[6537]: [90B blob data] Oct 31 19:54:06 alfa.acloud.pt python[6537]: [155B blob data] Oct 31 19:54:06 alfa.acloud.pt python[6537]: [100B blob data] Oct 31 19:56:06 alfa.acloud.pt python[6537]: [90B blob data] Oct 31 19:56:07 alfa.acloud.pt python[6537]: [155B blob data] Oct 31 19:56:07 alfa.acloud.pt python[6537]: [100B blob data] Oct 31 19:58:07 alfa.acloud.pt python[6537]: [90B blob data] Oct 31 19:58:08 alfa.acloud.pt python[6537]: [155B blob data] Oct 31 19:58:08 alfa.acloud.pt python[6537]: [100B blob data] Everytime I restart the VM I need to set the owner and group # chown ovirtagent:ovirtagent /dev/virtio-ports/ovirt-guest-agent.0 -- Jose Ferradeira http://www.logicworks.pt

4 years, 5 months

4
8
0 / 0

cannot live migrate the hosted engine

by Rob Verduijn

Hello, In my hyperconverged environment I cannot live migrate the hosted engine. However shutting down the hosted engine then starting it on another host works fine. This is the only way to migrate the engine to any of the hosts that are configured for the engine. I can't seem to find anything in the logs and hosted-engine vm-status doesn't tell me anything. Anybody any ideas where to start looking ? Rob

4 years, 5 months

2
3
0 / 0

Issue with ovirt self hosted engine instalaltion 4.4

by hjadavalluva＠ukaachen.de

Hello, Good Day! I'm Hariharan and I'm working as System Administrator in Linux platform for RWTH Uniklink - Germany. Currently I'm managing the Ovirt environment and I'm very new to this domain. Currently I'm facing an issue with Ovirt self hosted engine installation 4.4 in CentOS 8 server. I have an issue when mounting the glusterfs storage to a target machine. Below is the exact issue what I face; Error: "changed": false, "msg": "Error: the target storage domain contains only 11.0GiB of available space while a minimum of 61.0GiB is required If you wish to use the current target storage domain by extending it, make sure it contains nothing before adding it. Note: (gluster storage was installed and configured in Linux work station with adding additional hard disk in one of the two gluster storage linux work station. I used replicated volumes (replica 2) in creating gluster volumes) Hardware detail: device model: Dell R540 Capacity: 240 GB I tried best possibilities to resolve this issue but still I'm facing the same issue. Could you please help me in resolving this issue with your guidance or support.

4 years, 5 months

4
18
0 / 0

Bond creation issue via hosted engine

by Harry O

Hi guys and girls, Every time I try to create a bond with my two onboard intel nic's (any type of bond) via hosted engine, it will fail with the following error "Error while executing action HostSetupNetworks: Unexpected exception", it will still get created on the node but then the engine will get the capabilities out of sync with the node and can't refresh. I will need to delete the bond manually on the node for the engine to be happy again. Anyone knows why? Here is some logs from engine log file: [root@ovirt1-engine ~]# cat /var/log/ovirt-engine/engine.log 2020-11-06 08:29:56,230+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.OvfDataUpdater] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [] Attempting to update VMs/Templates Ovf. 2020-11-06 08:29:56,236+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Before acquiring and wait lock 'EngineLock:{exclusiveLocks='[b150e472-1f45-11eb-8e70-00163e78288d=OVF_UPDATE]', sharedLocks=''}' 2020-11-06 08:29:56,236+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Lock-wait acquired to object 'EngineLock:{exclusiveLocks='[b150e472-1f45-11eb-8e70-00163e78288d=OVF_UPDATE]', sharedLocks=''}' 2020-11-06 08:29:56,237+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Running command: ProcessOvfUpdateForStoragePoolCommand internal: true. Entities affected : ID: b150e472-1f45-11eb-8e70-00163e78288d Type: StoragePool 2020-11-06 08:29:56,242+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Attempting to update VM OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Successfully updated VM OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Attempting to update template OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Successfully updated templates OVFs in Data Center 'Default' 2020-11-06 08:29:56,243+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Attempting to remove unneeded template/vm OVFs in Data Center 'Default' 2020-11-06 08:29:56,245+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Successfully removed unneeded template/vm OVFs in Data Center 'Default' 2020-11-06 08:29:56,245+01 INFO [org.ovirt.engine.core.bll.storage.ovfstore.ProcessOvfUpdateForStoragePoolCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-85) [7094b20b] Lock freed to object 'EngineLock:{exclusiveLocks='[b150e472-1f45-11eb-8e70-00163e78288d=OVF_UPDATE]', sharedLocks=''}' 2020-11-06 08:29:56,284+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] START, GetStorageDeviceListVDSCommand(HostName = ovirtn3.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'}), log id: 59a1c9e 2020-11-06 08:29:56,284+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22514) [] START, GetStorageDeviceListVDSCommand(HostName = ovirtn2.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='a4904c7c-92d7-4e4f-adf7-755f3c17335d'}), log id: 735f6d30 2020-11-06 08:29:57,020+01 WARN [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}] 2020-11-06 08:29:57,020+01 WARN [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}] 2020-11-06 08:29:57,020+01 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Failed in 'GetStorageDeviceListVDS' method 2020-11-06 08:29:57,020+01 WARN [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}] 2020-11-06 08:29:57,057+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-22513) [] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirtn3.5ervers.lan command GetStorageDeviceListVDS failed: Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"} 2020-11-06 08:29:57,057+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Command 'org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand' return value 'StorageDeviceListReturn:{status='Status [code=-32603, message=Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}]'}' 2020-11-06 08:29:57,057+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] HostName = ovirtn3.5ervers.lan 2020-11-06 08:29:57,057+01 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] Command 'GetStorageDeviceListVDSCommand(HostName = ovirtn3.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'})' execution failed: VDSGenericException: VDSErrorException: Failed to GetStorageDeviceListVDS, error = Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}, code = -32603 2020-11-06 08:29:57,057+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22513) [] FINISH, GetStorageDeviceListVDSCommand, return: , log id: 59a1c9e 2020-11-06 08:29:57,057+01 ERROR [org.ovirt.engine.core.bll.gluster.StorageDeviceSyncJob] (EE-ManagedThreadFactory-engine-Thread-22513) [] Exception retriving storage device from vds EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to GetStorageDeviceListVDS, error = Internal JSON-RPC error: {'reason': "'NoneType' object has no attribute 'iface'"}, code = -32603 (Failed with error unexpected and code 16) 2020-11-06 08:29:57,433+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GetStorageDeviceListVDSCommand] (EE-ManagedThreadFactory-engine-Thread-22514) [] FINISH, GetStorageDeviceListVDSCommand, return: [StorageDevice:{id='null', name='ST4000NM0033-9ZM170_Z1Z8JT3C', devUuid='null', fsUuid='null', vdsId='null', description='ST4000NM0033-9ZM (dm-multipath)', devType='ATA', devPath='/dev/mapper/ST4000NM0033-9ZM170_Z1Z8JT3C', fsType='null', mountPoint='null', size='3815447', canCreateBrick='true', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda', devUuid='9TjMR1-Mk1p-fS6M-w6sP-jEfx-FmPe-A2L5iO', fsUuid='null', vdsId='null', description='lvmvg', devType='ATA', devPath='/dev/gluster_vg_sda', fsType='null', mountPoint='null', size='3815444', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_lv_data', devUuid='FuEGn2-BVzA-JDyB-fZPY-BlsU-QYO4-xFVmD0', fsUuid='3d5d228e-ece8-4e59-92ae-c1eb6094e493', vdsId='null', desc ription='lvmthinlv', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_lv_data', fsType='xfs', mountPoint='null', size='51200', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_lv_engine', devUuid='i2p1Ps-Ix6M-hmJG-VFqJ-2zVE-w14m-71j7KW', fsUuid='6280a49f-f49b-49f6-bc92-139834aae959', vdsId='null', description='lvmlv', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_lv_engine', fsType='xfs', mountPoint='null', size='102400', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_lv_vmstore', devUuid='DggrnE-C127-U0la-XoyW-eA2w-LOzk-82UmrT', fsUuid='1349ed39-21ed-418a-a2c9-26e67f403d11', vdsId='null', description='lvmthinlv', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_lv_vmstore', fsType='xfs', mountPoint='null', size='3225600', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='gluster_vg_sda-gluster_thinpool_glu ster_vg_sda', devUuid='x0Sy1g-WRtr-ZODw-J1il-wJcv-MbKM-Hrfcr9', fsUuid='null', vdsId='null', description='lvmthinpool', devType='null', devPath='/dev/mapper/gluster_vg_sda-gluster_thinpool_gluster_vg_sda', fsType='null', mountPoint='null', size='3680660', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sda', devUuid='null', fsUuid='fgvWOq-CB7k-qIjJ-iY15-ljEK-aaFG-CvRLQW', vdsId='null', description='ST4000NM0033-9ZM (disk)', devType='ATA', devPath='/dev/sda', fsType='lvmpv', mountPoint='null', size='3815447', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sdb', devUuid='null', fsUuid='null', vdsId='null', description='ST4000NM0033-9ZM (disk)', devType='ATA', devPath='/dev/sdb', fsType='multipath_member', mountPoint='null', size='3815447', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sdc', devUuid='null', fsUuid='545ca4c8', vdsId='null', description='Ultra Fit (disk)', devType='USB', devPath='/dev/sdc', fsType='disklabel', mountPoint='null', size='14664', canCreateBrick='false', isGlusterBrick='false'}, StorageDevice:{id='null', name='sdc1', devUuid='null', fsUuid='null', vdsId='null', description='partition', devType='USB', devPath='/dev/sdc1', fsType='zfs_member', mountPoint='null', size='14663', canCreateBrick='true', isGlusterBrick='false'}], log id: 735f6d30 2020-11-06 08:30:00,403+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetLldpVDSCommand] (default task-71) [474a11f9-ea66-4fd2-bad3-488ce157d197] START, GetLldpVDSCommand(HostName = ovirtn1.5ervers.lan, GetLldpVDSCommandParameters:{hostId='285fc148-62ed-4243-8106-ed01eff28295'}), log id: 66e6c0c1 2020-11-06 08:30:00,522+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetLldpVDSCommand] (default task-71) [474a11f9-ea66-4fd2-bad3-488ce157d197] FINISH, GetLldpVDSCommand, return: {enp0s29u1u1=LldpInfo:{enabled='false', tlvs='[]'}, eno1=LldpInfo:{enabled='false', tlvs='[]'}, enp9s0=LldpInfo:{enabled='true', tlvs='[]'}}, log id: 66e6c0c1 2020-11-06 08:30:05,665+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] START, GlusterServersListVDSCommand(HostName = ovirtn3.5ervers.lan, VdsIdVDSCommandParametersBase:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'}), log id: 7f602482 2020-11-06 08:30:05,859+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterServersListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] FINISH, GlusterServersListVDSCommand, return: [192.168.4.128/24:CONNECTED, ovirtn2.5ervers.lan:CONNECTED, ovirtn1.5ervers.lan:CONNECTED], log id: 7f602482 2020-11-06 08:30:05,862+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] START, GlusterVolumesListVDSCommand(HostName = ovirtn3.5ervers.lan, GlusterVolumesListVDSParameters:{hostId='4ec53a62-5cf3-479a-baf5-44c5b7624d39'}), log id: 7f8c7e41 2020-11-06 08:30:05,968+01 INFO [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListVDSCommand] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-75) [] FINISH, GlusterVolumesListVDSCommand, return: {95817a31-0623-44ed-a8bc-d2f37af7644d=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@92ac351e, 03874a87-1e23-4e54-8445-159ba27b48fe=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@25915a3c, 90de405f-60f0-401a-8bdf-7203d8db21f3=org.ovirt.engine.core.common.businessentities.gluster.GlusterVolumeEntity@56a4cd2d}, log id: 7f8c7e41 2020-11-06 08:30:07,416+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Before acquiring lock-timeout 'EngineLock:{exclusiveLocks='[HOST_NETWORK285fc148-62ed-4243-8106-ed01eff28295=HOST_NETWORK]', sharedLocks=''}' 2020-11-06 08:30:07,416+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Lock-timeout acquired to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK285fc148-62ed-4243-8106-ed01eff28295=HOST_NETWORK]', sharedLocks=''}' 2020-11-06 08:30:07,464+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Running command: HostSetupNetworksCommand internal: false. Entities affected : ID: 285fc148-62ed-4243-8106-ed01eff28295 Type: VDSAction group CONFIGURE_HOST_NETWORK with role type ADMIN 2020-11-06 08:30:07,464+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Before acquiring lock in order to prevent monitoring for host 'ovirtn1.5ervers.lan' from data-center 'Default' 2020-11-06 08:30:07,464+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Lock acquired, from now a monitoring of host will be skipped for host 'ovirtn1.5ervers.lan' from data-center 'Default' 2020-11-06 08:30:07,466+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] START, HostSetupNetworksVDSCommand(HostName = ovirtn1.5ervers.lan, HostSetupNetworksVdsCommandParameters:{hostId='285fc148-62ed-4243-8106-ed01eff28295', vds='Host[ovirtn1.5ervers.lan,285fc148-62ed-4243-8106-ed01eff28295]', rollbackOnFailure='true', commitOnSuccess='true', connectivityTimeout='120', networks='[]', removedNetworks='[]', bonds='[CreateOrUpdateBond:{id='null', name='bond0', bondingOptions='mode=4 miimon=100 xmit_hash_policy=2', slaves='[eno1, enp9s0]'}]', removedBonds='[]', clusterSwitchType='LEGACY', managementNetworkChanged='false'}), log id: 695498c2 2020-11-06 08:30:07,466+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] FINISH, HostSetupNetworksVDSCommand, return: , log id: 695498c2 2020-11-06 08:30:12,118+01 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}] 2020-11-06 08:30:12,119+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Failed in 'GetCapabilitiesVDS' method 2020-11-06 08:30:12,119+01 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Unexpected return value: Status [code=-32603, message=Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}] 2020-11-06 08:30:12,164+01 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirtn1.5ervers.lan command GetCapabilitiesVDS failed: Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"} 2020-11-06 08:30:12,164+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand' return value 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSInfoReturn@5ccc140e' 2020-11-06 08:30:12,164+01 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] HostName = ovirtn1.5ervers.lan 2020-11-06 08:30:12,164+01 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Command 'GetCapabilitiesVDSCommand(HostName = ovirtn1.5ervers.lan, VdsIdAndVdsVDSCommandParametersBase:{hostId='285fc148-62ed-4243-8106-ed01eff28295', vds='Host[ovirtn1.5ervers.lan,285fc148-62ed-4243-8106-ed01eff28295]'})' execution failed: VDSGenericException: VDSErrorException: Failed to GetCapabilitiesVDS, error = Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}, code = -32603 2020-11-06 08:30:12,165+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Host setup networks finished. Lock released. Monitoring can run now for host 'ovirtn1.5ervers.lan' from data-center 'Default' 2020-11-06 08:30:12,165+01 ERROR [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Command 'org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand' failed: EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to GetCapabilitiesVDS, error = Internal JSON-RPC error: {'reason': "Attempt to call function: <bound method Global.getCapabilities of <vdsm.API.Global object at 0x7faebc45cfd0>> with arguments: () error: 'module' object is not callable"}, code = -32603 (Failed with error unexpected and code 16) 2020-11-06 08:30:12,222+01 INFO [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-71) [335cc174-4ec6-4f32-abf5-00b6ab8a15f4] Lock freed to object 'EngineLock:{exclusiveLocks='[HOST_NETWORK285fc148-62ed-4243-8106-ed01eff28295=HOST_NETWORK]', sharedLocks=''}'

4 years, 5 months

2
10
0 / 0

Issue in importing ISO storage domain in Ovirt 4.3

by hjadavalluva＠ukaachen.de

Hello, I'm managing Ovirt environment 4.3 and I'm very new to this area. The setup was already done by former colleague and right now I'm managing this environment. Recently, one VM's OS got corrupted and I have to re-install the OS in that VM to bring the VM up and running. For doing this, I need to import the ISO domain from gluster storage (this ISO domain is not present in ovirt engine now). While importing the ISO domain, I face the following error; "Error while executing the action: Cannot add memory connection. Memory connection 63566129-bb20-4b11-b5c2-5e943ab94bed already exists" I already searched this "63566129-bb20-4b11-b5c2-5e943ab94bed" image in ovirt server, target server and gluster storage server but I couldn't find it. Could you please help me in resolving this issue? I got stuck badly here. Thanks in advance! Best Regards, Hariharan

4 years, 5 months

1
0
0 / 0

is there a way to run the cockpit playbooks on the cli ?

by Rob Verduijn

Hi, For some reason my browser and network like to produce hiccups during the running of the hyperconverge script and the hosted engine install script. ( My prime suspect is Murphy ) This is a default feature in all browsers on any platform. This is why I try to avoid the use of cockpit for complex matters. ( ie anything more complex than proces listing or the viewing of logs ) On the cockpit host, from what directory with which options and what playbook do I need to use to get the same result. Rob

4 years, 5 months

1
1
0 / 0

Fence Agent in Virtual Environment

by jb

Hello, I would like to build a hyperconverged gluster with hosted engine in a virtual environment, on Fedora 33 with KVM. The setup is for testing purposes, specially for test upgrades before running them on the real physical Servers. But I want to have the setup as close as possible to the real environment, so the only thing is missing is a fence agent. Is there a way to simulate power management in a virtual environment? Jonathan

4 years, 5 months

3
4
0 / 0

Re: Fence Agent in Virtual Environment

by Jonathan Baecker

Am 05.11.20 um 19:19 schrieb Strahil Nikolov: > You need to enable HA for the VM. Yes this I know and I had this on. When I set the host in maintenance mode, the VM was moving to another host, but not when I kill the host. > About the XVM , I think that you first need to install it on all hosts and then check in UI, if you can find that fence agent in "Power Management". Thanks, I will try this! Best Regard Jonathan > > Best Regards, > Strahil Nikolov > > > > > > > В четвъртък, 5 ноември 2020 г., 18:41:40 Гринуич+2, jb <jonbae77(a)gmail.com> написа: > > > > > > Yes I know, is just a guest... I wanted to test what is happen with a > VM, when I kill it's host. After that, I have not seen that the VM is > moving to another host. > > So I thought maybe ovirt needs the power management for that. > > I have read about fence_xvm, but I don't know how to configure oVirt > with that. > > > > Am 05.11.20 um 17:11 schrieb Strahil Nikolov: >> This is just a guess , but you might be able to install fence_xvm on all Virtualized Hosts . >> >> Best Regards, >> Strahil Nikolov >> >> >> >> >> >> >> В четвъртък, 5 ноември 2020 г., 16:00:40 Гринуич+2, jb <jonbae77(a)gmail.com> написа: >> >> >> >> >> >> Hello, >> >> I would like to build a hyperconverged gluster with hosted engine in a >> virtual environment, on Fedora 33 with KVM. >> >> The setup is for testing purposes, specially for test upgrades before >> running them on the real physical Servers. But I want to have the setup >> as close as possible to the real environment, so the only thing is >> missing is a fence agent. >> >> Is there a way to simulate power management in a virtual environment? >> >> >> Jonathan >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/V5SHGKNLTK2...

4 years, 5 months

1
0
0 / 0

configuration of hyperconverged setup with ssd cache for slow drives

by Rob Verduijn

Hello, After a serious struggle I finally managed to get ovirt-hosted engine with the hyperconverged setup to work. However I did not manage to get the ssd cache option for my slow sata drives to work. The installation script complained about mismatching block sizes. Is there a way to make the cockpit hyperconverged installation handle this ? Rob fdisk -l /dev/sda Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes fdisk -l /dev/mapper/gluster_vg_sdc-gluster_lv_data Disk /dev/mapper/gluster_vg_sdc-gluster_lv_data: 4.9 TiB, 5368709120000 bytes, 1310720000 sectors Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 1310720 bytes / 2621440 bytes

4 years, 5 months

2
1
0 / 0

[ANN] oVirt 4.4.3 Eighth Release Candidate is now available for testing

by Lev Veyde

oVirt 4.4.3 Eighth Release Candidate is now available for testing The oVirt Project is pleased to announce the availability of oVirt 4.4.3 Eighth Release Candidate for testing, as of November 5th, 2020. This update is the third in a series of stabilization updates to the 4.4 series. How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1 Note: Upgrading from 4.4.2 GA should not require re-doing these steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These are only required to be done once. Due to Bug 1837864 <https://bugzilla.redhat.com/show_bug.cgi?id=1837864> - Host enter emergency mode after upgrading to latest build If you have your root file system on a multipath device on your hosts you should be aware that after upgrading from 4.4.1 to 4.4.3 you may get your host entering emergency mode. In order to prevent this be sure to upgrade oVirt Engine first, then on your hosts: 1. Remove the current lvm filter while still on 4.4.1, or in emergency mode (if rebooted). 2. Reboot. 3. Upgrade to 4.4.3 (redeploy in case of already being on 4.4.3). 4. Run vdsm-tool config-lvm-filter to confirm there is a new filter in place. 5. Only if not using oVirt Node: - run "dracut --force --add multipath” to rebuild initramfs with the correct filter configuration 6. Reboot. Documentation - If you want to try oVirt as quickly as possible, follow the instructions on the Download <https://ovirt.org/download/> page. - For complete installation, administration, and usage instructions, see the oVirt Documentation <https://ovirt.org/documentation/>. - For upgrading from a previous version, see the oVirt Upgrade Guide <https://ovirt.org/documentation/upgrade_guide/>. - For a general overview of oVirt, see About oVirt <https://ovirt.org/community/about.html>. 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. You can hit: Problem: cannot install the best update candidate for package ovirt-engine-metrics-1.4.1.1-1.el8.noarch - nothing provides rhel-system-roles >= 1.0-19 needed by ovirt-engine-metrics-1.4.2-1.el8.noarch in order to get rhel-system-roles >= 1.0-19 you need https://buildlogs.centos.org/centos/8/virt/x86_64/ovirt-44/ repo since that package can be promoted to release only at 4.4.3 GA. 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.3 release highlights: http://www.ovirt.org/release/4.4.3/ * 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.3/ [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, 5 months

1
0
0 / 0

回复:[ovirt-devel] Re: Host's status how to change to UP when I execute Management--> Active command

by 李伏琼

thanks very much --------------原始邮件-------------- 发件人："Liran Rotenberg "<lrotenbe(a)redhat.com>; 发送时间：2020年11月5日(星期四) 晚上11:52 收件人："lifuqiong(a)sunyainfo.com" <lifuqiong(a)sunyainfo.com>; 抄送："users "<users(a)ovirt.org>;"devel "<devel(a)ovirt.org>; 主题：[ovirt-devel] Re: Host's status how to change to UP when I execute Management--> Active command ----------------------------------- Hi,The engine will monitor that host. Once it's reachable and we can get information from it the status will change accordingly. Please check out the HostMonitoring class. On Thu, Nov 5, 2020 at 11:57 AM lifuqiong(a)sunyainfo.com <lifuqiong(a)sunyainfo.com> wrote: Hi,      I checkout ovirt-engine's code with branch 4.2;  When execute Host's Management --> Active  command,  ovirt engine just set vds's status to "Unassigned" but how the vds's status changed to "UP" in ovirt-engine?  The code in ActiveVdsCommand.executeCommand() as follows: protected void executeCommand() {         final VDS vds = getVds();         try (EngineLock monitoringLock = acquireMonitorLock("Activate host")) {             executionHandler.updateSpecificActionJobCompleted(vds.getId(), ActionType.MaintenanceVds, false);             setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded());             if (getSucceeded()) {                 TransactionSupport.executeInNewTransaction(() -> {                     // set network to operational / non-operational                     List<Network> networks = networkDao.getAllForCluster(vds.getClusterId());                     networkClusterHelper.setStatus(vds.getClusterId(), networks);                     return null;                 });                 // Start glusterd service on the node, which would haven been stopped due to maintenance                 if (vds.getClusterSupportsGlusterService()) {                     runVdsCommand(VDSCommandType.ManageGlusterService,                             new GlusterServiceVDSParameters(vds.getId(), Arrays.asList("glusterd"), "restart"));                     // starting vdo service                     GlusterStatus isRunning = glusterUtil.isVDORunning(vds.getId());                     switch (isRunning) {                     case DOWN:                         log.info("VDO service is down in host : '{}' with id '{}', starting VDO service",                                 vds.getHostName(),                                 vds.getId());                         startVDOService(vds);                         break;                     case UP:                         log.info("VDO service is up in host : '{}' with id '{}', skipping starting of VDO service",                                 vds.getHostName(),                                 vds.getId());                            break;                     case UNKNOWN:                         log.info("VDO service is not installed host : '{}' with id '{}', ignoring to start VDO service",                                 vds.getHostName(),                                 vds.getId());                         break;                     }                 }             }         }     } Your Sincerely Mark Lee _______________________________________________ Devel mailing list -- devel(a)ovirt.org To unsubscribe send an email to devel-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/36745S77NLH...

4 years, 5 months

1
0
0 / 0

Re: [ovirt-devel] Host's status how to change to UP when I execute Management--> Active command

by Liran Rotenberg

Hi, The engine will monitor that host. Once it's reachable and we can get information from it the status will change accordingly. Please check out the HostMonitoring class. On Thu, Nov 5, 2020 at 11:57 AM lifuqiong(a)sunyainfo.com < lifuqiong(a)sunyainfo.com> wrote: > > Hi, > I checkout ovirt-engine's code with branch 4.2; When execute Host's > Management --> Active command, ovirt engine just set vds's status to > "Unassigned" but how the vds's status changed to "UP" in ovirt-engine? The > code in ActiveVdsCommand.executeCommand() as follows: > protected void executeCommand() { > > final VDS vds = getVds(); > try (EngineLock monitoringLock = acquireMonitorLock("Activate > host")) { > executionHandler.updateSpecificActionJobCompleted(vds.getId(), > ActionType.MaintenanceVds, false); > > setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded()); > > if (getSucceeded()) { > TransactionSupport.executeInNewTransaction(() -> { > // set network to operational / non-operational > List<Network> networks = > networkDao.getAllForCluster(vds.getClusterId()); > networkClusterHelper.setStatus(vds.getClusterId(), > networks); > return null; > }); > > // Start glusterd service on the node, which would haven > been stopped due to maintenance > if (vds.getClusterSupportsGlusterService()) { > runVdsCommand(VDSCommandType.ManageGlusterService, > new GlusterServiceVDSParameters(vds.getId(), > Arrays.asList("glusterd"), "restart")); > // starting vdo service > GlusterStatus isRunning = > glusterUtil.isVDORunning(vds.getId()); > switch (isRunning) { > case DOWN: > log.info("VDO service is down in host : '{}' with > id '{}', starting VDO service", > vds.getHostName(), > vds.getId()); > startVDOService(vds); > break; > case UP: > log.info("VDO service is up in host : '{}' with > id '{}', skipping starting of VDO service", > vds.getHostName(), > vds.getId()); > break; > case UNKNOWN: > log.info("VDO service is not installed host : > '{}' with id '{}', ignoring to start VDO service", > vds.getHostName(), > vds.getId()); > break; > } > > } > } > } > } > > > Your Sincerely > Mark Lee > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/36745S77NLH... >

4 years, 5 months

1
0
0 / 0

Affinity Group Graceful Migration

by thilburn＠generalpacific.com

Hello, I'm trying to get an Affinity Group setup that will gracefully remove VMs from a Host. Below is what I've tried but the VMs will not migrate off. oVirt 4.3 Priority: 1 VM Affinity Rule: Disabled Host Affinity Rule: Negative ( Soft ) Virtual Machines: Select a VM ( My understanding is this would mean all VMs? ) Hosts: Host: <Name of host> Also, is this right place to ask for help on this?

4 years, 5 months

2
1
0 / 0

Coffee Lake CPU

by jb

Hello, sorry there comes many questions today from me! I plan a new cluster setup, and for that I bought ASUS Barebone with Intel Xeon E-2246G CPUs. Sadly I pay not enough attention to the system requirements from oVirt and now I say that theCoffee Lake-ER architecture is not in the supported CPU list from oVirt. Is there any downsides with using a Coffee Lake CPU? Jonathan

4 years, 5 months

1
0
0 / 0

locked disk making it impossible to remove vm

by igor.lustosa＠hybriddc.com.br

I have a vm that has two disks one active and another disabling when trying to migrate the disk to another storage the task was in a loop creating several snapshots, I turned off the VM and the loop stopped and after several hours the task disappeared and the VM disk was left blocking making it impossible to be deleted and when trying to delete the vm it does not exclude from the following message locked disk making it impossible to remove vm How can I solve this?

4 years, 5 months

2
3
0 / 0

VM Struck in Shutdown Mode

by Andrei Verovski

Hi, I have oVirt 4.4 engine and v4.2 nodes. On one node newly created VM struck in shutdown mode (with green round recycle icon) - I can’t anything, neither power off neither shutdown, both operation fail (with no explanation). This VM have no value whatsoever, but I can’t delete it either. Restarted oVirt engine, all same. Process list (on node) clearly shows absence of this VM as KVM process. VM is down. How to reset its status in oVirt? Thanks in advance. Andrei

4 years, 5 months

2
3
0 / 0

enabling BaseOS repo in oVirt Node 4.4

by jb

Hello everybody, is it a problem to enable the BaseOS on a oVirt Node? I ask, because I would like to install nano 😁... I could just disable it again, after installation, but what can happen when it stays enabled? Jonathan

4 years, 5 months

1
0
0 / 0

Host's status how to change to UP when I execute Management--> Active command

by lifuqiong＠sunyainfo.com

Hi, I checkout ovirt-engine's code with branch 4.2; When execute Host's Management --> Active command, ovirt engine just set vds's status to "Unassigned" but how the vds's status changed to "UP" in ovirt-engine? The code in ActiveVdsCommand.executeCommand() as follows: protected void executeCommand() { final VDS vds = getVds(); try (EngineLock monitoringLock = acquireMonitorLock("Activate host")) { executionHandler.updateSpecificActionJobCompleted(vds.getId(), ActionType.MaintenanceVds, false); setSucceeded(setVdsStatus(VDSStatus.Unassigned).getSucceeded()); if (getSucceeded()) { TransactionSupport.executeInNewTransaction(() -> { // set network to operational / non-operational List<Network> networks = networkDao.getAllForCluster(vds.getClusterId()); networkClusterHelper.setStatus(vds.getClusterId(), networks); return null; }); // Start glusterd service on the node, which would haven been stopped due to maintenance if (vds.getClusterSupportsGlusterService()) { runVdsCommand(VDSCommandType.ManageGlusterService, new GlusterServiceVDSParameters(vds.getId(), Arrays.asList("glusterd"), "restart")); // starting vdo service GlusterStatus isRunning = glusterUtil.isVDORunning(vds.getId()); switch (isRunning) { case DOWN: log.info("VDO service is down in host : '{}' with id '{}', starting VDO service", vds.getHostName(), vds.getId()); startVDOService(vds); break; case UP: log.info("VDO service is up in host : '{}' with id '{}', skipping starting of VDO service", vds.getHostName(), vds.getId()); break; case UNKNOWN: log.info("VDO service is not installed host : '{}' with id '{}', ignoring to start VDO service", vds.getHostName(), vds.getId()); break; } } } } } Your Sincerely Mark Lee

4 years, 5 months

1
0
0 / 0

20+ Fresh Installs Failing in 20+ days [newbie & frustrated]

by info＠worldhostess.com

I have no idea if it is Hardware or Software. It crashed every time after it starts with the storage setup Error in ovirt-hosted-engine-setup-ansilble-setup-final_clean [FAILED] DESTROYED LOCAL STORAGE-POOL HTTPS --- "certificate invalid" The system is very unstable and impossible to do anything remotely ONLY accessible on local terminal. This is my hardware SuperMicro X11SSF-M Intel Xeon E3-1230 16 GB ECC RAM 2 x 1 TB Micron 1300 SSD Key Features X11SSM-F specifications Single socket H4 (LGA 1151) supports IntelR XeonR processor E3-1200 v6/v5, IntelR 7th/6th Gen. CoreT i3 series, IntelR CeleronR and IntelR PentiumR IntelR C236 chipset Up to 64GB Unbuffered ECC UDIMM DDR4 2400MHz; 4 DIMM slots Expansion slots: 1 PCI-E 3.0 x8 (in x16), 1 PCI-E 3.0 x8, 2 PCI-E 3.0 x4 (in x8) Dual GbE LAN with IntelR i210-AT 8 SATA3 (6Gbps) via C236; RAID 0, 1, 5, 10 I/O: 1 VGA, 2 COM, 2 SuperDOM, and TPM header 5 USB 3.0 (2 rear, 2 via header(s), 1 Type A), 6 USB 2.0 (2 rear, 4 via header(s)) Integrated IPMI 2.0 and KVM with Dedicated LAN Yours Sincerely, Henni

4 years, 5 months

6
38
0 / 0

lose my server ovirt-engine in network

by garcialiang.anne＠gmail.com

Hello, I installed my ovirt-engine during 1 month. I can connect with ssh or website. Yesterday, I rebooted my server ovirt-engine. But I can't connect it with ssh. My server lost in network. I can login with the machine, but I can't ping with network. Is there the problem with network setting ? Could you help me, please? Thanks, Anne Garcia

4 years, 5 months

1
0
0 / 0

Removal of dpdk

by Ales Musil

Hello, we have decided to remove dpdk in the upcoming version of oVirt namely 4.4.4. Let us know if there are any concerns about this. Thank you. Regards, Ales Musil -- Ales Musil Software Engineer - RHV Network Red Hat EMEA <https://www.redhat.com> amusil(a)redhat.com IM: amusil <https://red.ht/sig>

4 years, 5 months

4
6
0 / 0

Requesting for a help in resolving ovirt self hosted engine installation issue

by Jadavalluvar Sethuraman, Hariharan

Hello, Good Day! I'm Hariharan and I'm working as System Administrator in Linux platform for RWTH Uniklink - Germany. Currently I'm managing the Ovirt environment and I'm very new to this domain. Currently I'm facing an issue with Ovirt self hosted engine installation 4.4 in CentOS 8 server. I have an issue when mounting the glusterfs storage to a target machine. Below is the exact issue what I face; Error: "changed": false, "msg": "Error: the target storage domain contains only 22.0GiB of available space while a minimum of 61.0GiB is required If you wish to use the current target storage domain by extending it, make sure it contains nothing before adding it. Note: (gluster storage was installed and configured in Linux work station with adding additional hard disk in one of the two gluster storage linux work station. I used replicated volumes (replica 2) in creating gluster volumes) Hardware detail: device model: Dell R540 Capacity: 240 GB I tried best possibilities to resolve this issue but still I'm facing the same issue. Could you please help me in resolving this issue with your guidance or support. Hariharan Jadavalluvar Sethuraman Systemadministrator der Brain Imaging Facility (BIF) des interdisziplinären Zentrums für klinische Forschung (IZKF) Universitätsklinikum Aachen (AöR) Pauwelsstraße 30 52074 Aachen Tel: +49 241 80-89150 E-Mail: hjadavalluva(a)ukaachen.de<mailto:rrodriguez@ukaachen.de> ________________________________

4 years, 5 months

1
0
0 / 0

Ovirt 4.4 ilo_ssh version HP ILO3. ERROR: Unable to connect/login to fencing device

by melnyksergii＠gmail.com

Dears, I have a 3 nodes with HP blade servers G7 and ILO3. ILO3 with the latest firmware 1.93 from Aug 07 2020. I'm try to migrate from Ovirt 4.3 to 4.4 with Centos 8, but I had a problem with setup ssh ilo fence on this nodes. In Ovirt 4.3 with Centos 7 all is works. When I try to Test fence, I see ERROR: Unable to connect/login to fencing device. When I try to use /usr/sbin/fence_ilo_ssh I see the same error. So, I know where is a problem. The problem in an old ssh security keys HostKeyAlgorithms=+ssh-dss. When I add to /root/.ssh/config some exclude for use HostKeyAlgorithms=+ssh-dss I can connect to ilo over ssh from root with: /usr/sbin/fence_ilo_ssh -a 10.0.11.157 -l user -p passwordh -x -u 22 --login-timeout=10 -o status and see: Status: ON But when I try again setup ilo_ssh fence in Ovirt-engine UI I still have the same ERROR: Unable to connect/login to fencing device. How can I solve this problem in Ovirt? Thanks

4 years, 5 months

1
1
0 / 0

HCI with 5 node quest

by simon＠justconnect.ie

I have a 3 node HCI setup with 2 Replica 3 volumes using nodes 1, 2 & 3 and have added 2 additional Compute nodes to this Cluster. What is stopping me from adding nodes 4 & 5 as Gluster Peers and creating a glusterfs Replica 3 Volume using nodes 3, 4 & 5? Shimme

4 years, 5 months

3
4
0 / 0

ovirt glusterfs

by garcialiang.anne＠gmail.com

Hello, I've some problem with Hyperconverged Configure Gluster storage and oVirt hosted engine. I've the message error: failed: [node2.xxxxx.fr] (item={u'key': u'gluster_vg_sdb', u'value': [{u'vgname': u'gluster_vg_sdb', u'pvname': u'/dev/sdb'}]}) => {"ansible_loop_var": "item", "changed": false, "err": " Device /dev/sdb excluded by a filter.\n", "item": {"key": "gluster_vg_sdb", "value": [{"pvname": "/dev/sdb", "vgname": "gluster_vg_sdb"}]}, "msg": "Creating physical volume '/dev/sdb' failed", "rc": 5} Could you help me for know where is the problem, please? Thanks, Anne Garcia

4 years, 5 months

4
3
0 / 0

POWER9 (ppc64le) Support on oVirt 4.4.1

by Vinícius Ferrão

Hello, I was using oVirt 4.3.10 with IBM AC922 (POWER9 / ppc64le) without any issues. Since I’ve moved to 4.4.1 I can’t add the AC922 machine to the engine anymore, it complains with the following error: The host CPU does not match the Cluster CPU type and is running in degraded mode. It is missing the following CPU flags: model_POWER9, powernv. Any ideia of what’s may be happening? The engine runs on x86_64, and I was using this way on 4.3.10. Machine info: timebase : 512000000 platform : PowerNV model : 8335-GTH machine : PowerNV 8335-GTH firmware : OPAL MMU : Radix Thanks,

4 years, 5 months

3
18
0 / 0

Re: Migrate hosted-engine to new storage domain

by Yedidyah Bar David

On Tue, Nov 3, 2020 at 7:07 AM Matthew.Stier(a)fujitsu.com <Matthew.Stier(a)fujitsu.com> wrote: > > I’ve migrated my iSCSI storage to a new array, and the only thing remaining is to migrate the hosted-engine. > > > > Any directions on how I should proceed. I understand that I will need to back-up the existing, create a new hosted-engine on the new storage, specifying the backup a reference. > > > > I just would like to see a step-by-step, so I know I am doing everything, and in the right order. Generally speaking, you should follow the hosted-engine backup and restore flows/documents. I strongly suggest to test this first on a test machine before production. You can take a backup without downtime. Restore on some machine (can be a VM, with nested-kvm) that has no access to your production storage and hosts (to make sure the restored engine won't start managing them/competing with the production one). See that all looks good. Then plan production... Good luck and best regards, -- Didi

4 years, 5 months

1
0
0 / 0

Migrate hosted-engine to new storage domain

by Matthew.Stier＠fujitsu.com

I've migrated my iSCSI storage to a new array, and the only thing remaining is to migrate the hosted-engine. Any directions on how I should proceed. I understand that I will need to back-up the existing, create a new hosted-engine on the new storage, specifying the backup a reference. I just would like to see a step-by-step, so I know I am doing everything, and in the right order.

4 years, 5 months

1
0
0 / 0

Select host for image upload

by C Williams

Hello, I am having problems selecting the host that I want to use for .iso and other image uploads via the oVirt Web Console. I have 20+ servers of varying speeds. Somehow oVirt keeps wanting to select my oldest and slowest system to use for image uploads. Please Help ! Thank You ! C Williams

4 years, 5 months

2
3
0 / 0

Q: Failed creating snapshot

by Andrei Verovski

Hi, I have oVirt 4.4 with nodes 4.2.8 Attempt to create snapshot failed with: EventID 10802 VDSM node11 command SnapshotVDS failed: Message timeout can be caused by communication issues. Event ID 2022 Add-disk operation failed to complete. However, snapshot is on disk since VM now takes 1200GB instead of 500. Yes snapshot list in VM details is empty. How to recover disk space occupied by unsuccessful snapshot ? I looked at /vmraid/nfs/disks/xxxx-xxxx-xxx/images and there are no distinctive files which I can identify as snapshot. Thanks in advance. Andrei

4 years, 5 months

2
1
0 / 0

ovirt installation with proxy or katello

by Markus Schaufler

Hi, in our environment we need to either specify proxy settings or use foreman/katello repositories. I'd like to test both ways but the installer with the ansible scripts behind don't seem to use the hosts settings. Where do I have to adopt the install scripts and will there be in future a GUI option to specify those things? Can't understand why disconnected environments or environments with proxies aren't better taken into consideration...? Thanks in advance, Markus

4 years, 5 months

1
0
0 / 0

Question about OVN MTU

by Strahil Nikolov

Hello All, I would like to learn more about OVN and especially the maximum MTU that I can use in my environment. Current Setup 4.3.10 Network was created via UI -> MTU Custom -> 8976 -> Create on External Provider -> Connect to Physical Network So my physical connection is MTU 9000 and I have read that Geneve uses 24 bits (maybe that's wrong ?) , thus I have reduced the MTU to 8976. I did some testing on the VMs and ping with payload of '8914' was the maximum I could pass without fragmenting and thus the MTU on the VMs was set to 8942. Did I correctly configure the test network's MTU and am I understanding it correctly that we need extra 34 bits inside the network for encapsulation ? I have checked https://www.ovirt.org/develop/release-management/features/network... but I don't see any refference how to calculate the max MTU. Best Regards, Strahil Nikolov

4 years, 5 months

3
8
0 / 0

different rendering chrome and firefox and corruptions in both

by Gianluca Cecchi

Hello, I'm using Fedora 31 with google-chrome-stable-86.0.4240.111-1.x86_64 firefox-82.0-4.fc31.x86_64 Engine was deployed from a CentOS Linux 8.2 host and then with hosted engine wizard, using the appliance rpm (Package ovirt-engine-appliance.x86_64 4.4-20200916125954.1.el8) Connecting to the same 4.4.2 engine I get: 1) different landing page graphics firefox: https://drive.google.com/file/d/142Ch7qXmmIP9sQQCS1rD75yexX64RmSu/view?us... chrome: https://drive.google.com/file/d/1KPvlNk65ltIBhr8GFdVm-GMtfq1Elt7J/view?us... 2) corruption in several editing pages in firefox, where a sort of top white part seems to compromise the lower part of the window, making impossible to complete. eg in new network I don't see the lower part related to MTU...: https://drive.google.com/file/d/18aQfDbl_9R9oQsTMwebJSiRZHETkUWIc/view?us... 3) in Stotrage --> volumes page if I click on a volume, firefox shows no problem, but chrome gives a gui exception: https://drive.google.com/file/d/1svzQjrGctRMQFvZEpW9zpOlUbv8XXl3Q/view?us... Gianluca

4 years, 5 months

2
1
0 / 0

Discard after Delete

by Joris DEDIEU

Hi list, I forgot to check "Discard after Delete" when creating a new volume. Is there a way (other than to empty the volume) to reclaim free blocks. In https://bugzilla.redhat.com/show_bug.cgi?id=981626 I read about blkdiscard, but as far as I understand it will erase my VMs ... Thanks for your answers Joris

4 years, 5 months

4
4
0 / 0

Training Video or document or training session

by info＠worldhostess.com

Can someone recommend a training video of some kind of step by step document to do the installation and administration for OVirt? Or if someone that wants to do a one on one online training? I would be super excited to do online training. I have been trying many time to install and I am sure I make some mistakes because I can't get OVirt to work properly. I have done numerous installations during the last few weeks. Yours Sincerely, Henni

4 years, 5 months

4
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Users November 2020