- Users - oVirt List Archives

4.2.3 -- No Snapshot Restore on GUI?
by mrnervus＠gmail.com 12 May '18

12 May '18

Struggling to identify where on the GUI I can navigate to in order to perform a snapshot restore. Is this functionality not available anymore?

1 0

Is PostgreSQL 9.5 required now as of oVirt 4.2?
by Lacey Powers 12 May '18

12 May '18

Hi All, I have a setup of oVirt on 4.1 that has been working brilliantly for over a year, serving the production workloads at my dayjob without complaint. Originally, I had set it up with a custom PostgreSQL version, 9.6, from the PGDG repositories, since the suggested 9.2 was already quite old, and it allowed me to keep consistent versions of PostgreSQL across all the infrastructure I have. Now that I am trying to upgrade to oVirt 4.2, when I run engine-setup per the directions in the release notes documentation, engine-setup insists on PostgreSQL 9.5 from Software Collections, comparing the postgresql versions and then aborting. I don't see a way to tell it that I have a different running version of PostgreSQL that's greater than 9.5 already. Does this mean that no other versions than 9.5 are supported, and I need to downgrade and use the Software Collections version exclusively? Or is there a custom setting that I am missing that will enable me to continue using the 9.6 install I already have. Thank you for your time. Best, Lacey

2 2

Hosted Engine dependency issue
by Peter Harman 12 May '18

12 May '18

Hello, I am new to Ovirt (and linux) , I successfully installed a working hosted engine twice but am now running into a dependency issue. I keep getting the below message: Error: Package: cockpit-storaged-160-1.el7.centos.noarch (extras) Requires: storaged-iscsi >= 2.1.1 Available: storaged-iscsi-2.5.2-2.el7.x86_64 (ovirt-4.2-centos-ovirt42) storaged-iscsi = 2.5.2-2.el7 Available: storaged-iscsi-2.5.2-4.el7.x86_64 (extras) storaged-iscsi = 2.5.2-4.el7 Error: Package: cockpit-storaged-160-1.el7.centos.noarch (extras) Requires: storaged >= 2.1.1 Available: storaged-2.5.2-2.el7.x86_64 (ovirt-4.2-centos-ovirt42) storaged = 2.5.2-2.el7 Available: storaged-2.5.2-4.el7.x86_64 (extras) storaged = 2.5.2-4.el7 Error: Package: cockpit-storaged-160-1.el7.centos.noarch (extras) Requires: storaged-lvm2 >= 2.1.1 Available: storaged-lvm2-2.5.2-2.el7.x86_64 (ovirt-4.2-centos-ovirt42) storaged-lvm2 = 2.5.2-2.el7 Available: storaged-lvm2-2.5.2-4.el7.x86_64 (extras) storaged-lvm2 = 2.5.2-4.el7 I wiped the machine and tried again with no luck. Does anybody know what I am doing wrong? Peter Harman - Systems and Safety Cordinator | Homeyer Precision Manufacturing [Description: C:\Users\gruether\AppData\Local\Temp\Temp1_Homeyer Logo (2).zip\Homeyer Logo\Homeyer Logo.jpg] 16051 State Hwy 47, Marthasville, MO 63357| E pharman(a)homeyertool.com |<mailto:pharman@homeyertool.com%20%7C> P 636.433.2244 | F 636.433.5257

2 1

ONN v4.2.3 Hosted Engine Deployment - Auto addition of Gluster Hosts
by glenn.farmer＠netfortris.com 12 May '18

12 May '18

The new Ovirt Node installation script in v4.2.3 automatically adds the gluster hosts after initial hosted engine setup. This caused major problems as I had used different FQDNs on a different VLAN to initially setup my gluster nodes [to isolate storage traffic] - but then put them onto the "ovirtmgmt" network. Because they were gluster nodes - I could not remove them from the ovirtmgmt network to re-install on the proper management VLAN. I recommend removing the auto-installation of the other gluster nodes - or at least provide an option to decline the automatic addition of the other nodes.

2 1

unable to upgrade Centos 7.5 due to ovirt package dependencies
by Vineet Khandpur 11 May '18

11 May '18

Hello. Attempting to upgrade our ovirt hypervisors, getting the following error: --> Finished Dependency Resolution Error: Package: cockpit-storaged-160-1.el7.centos.noarch (@extras) Requires: storaged-iscsi >= 2.1.1 Removing: storaged-iscsi-2.5.2-4.el7.x86_64 (@extras) storaged-iscsi = 2.5.2-4.el7 Obsoleted By: udisks2-iscsi-2.7.3-6.el7.x86_64 (base) Not found Available: storaged-iscsi-2.5.2-2.el7.x86_64 (ovirt-4.2-centos-ovirt42) storaged-iscsi = 2.5.2-2.el7 Error: Package: cockpit-storaged-160-1.el7.centos.noarch (@extras) Requires: storaged-lvm2 >= 2.1.1 Removing: storaged-lvm2-2.5.2-4.el7.x86_64 (@extras) storaged-lvm2 = 2.5.2-4.el7 Obsoleted By: udisks2-lvm2-2.7.3-6.el7.x86_64 (base) Not found Available: storaged-lvm2-2.5.2-2.el7.x86_64 (ovirt-4.2-centos-ovirt42) storaged-lvm2 = 2.5.2-2.el7 Error: Package: cockpit-storaged-160-1.el7.centos.noarch (@extras) Requires: storaged >= 2.1.1 Removing: storaged-2.5.2-4.el7.x86_64 (@extras) storaged = 2.5.2-4.el7 Obsoleted By: udisks2-2.7.3-6.el7.x86_64 (base) Not found Available: storaged-2.5.2-2.el7.x86_64 (ovirt-4.2-centos-ovirt42) storaged = 2.5.2-2.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Would like to avoid using the --skip-broken option. Does the dependency for the various storaged packages need to be updated to instead require udisks2? Thanks. vk -------------------------------- Vineet Khandpur UNIX System Administrator Information Technology Services University of Alberta Libraries +1-780-492-4718

1 0

gluster dispersed volume provisioning
by josip＠section7.eu 11 May '18

11 May '18

Hi, have a quick question regarding ovirt UI and provisioning of gluster volumes. I've found an old thread - https://lists.ovirt.org/pipermail/users/2015-February/064602.html - where it's said that creating dispersed volumes is not supported but that it will be in the next release. Is there any update on when will it be supported? Thanks

2 1

ovirt 4.1 repo
by Alex K 11 May '18

11 May '18

Hi all, I have the following issue with repo of 4.1 version: I am doing: yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm yum update then I get: http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/repodata/repom…: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. To address this issue please refer to the below wiki article I know that 4.2 is released and stable but I cannot go to it if upgrade of all production servers is not planned. Can't I use still 4.1? Thanx, Alex

2 1

strange issue: vm lost info on disk
by Juan Pablo 11 May '18

11 May '18

Hi! , Im strugled about an ongoing problem: after migrating a vm's disk from an iscsi domain to a nfs and ovirt reporting the migration was successful, I see there's no data 'inside' the vm's disk. we never had this issues with ovirt so Im stranged about the root cause and if theres a chance of recovering the information. can you please help me out troubleshooting this one? I would really appreciate it =) running ovirt 4.2.1 here! thanks in advance, JP

2 1

CentOS 7.5.1804 is now officially available
by Sandro Bonazzola 11 May '18

11 May '18

FYI, CentOS 7.5.1804 is now officially available. See announce here: https://lists.centos.org/pipermail/centos-announce/2018-May/022829.html Users: I suggest to upgrade in order to get latest features, fixes and security fixes. Just a note for ppc64le users, there's a known bug with libguestfs requiring qemu-kvm-ma instead of qemu-kvm that may cause upgrade issues. This should be fixed in next update which should land in CentOS in ~2 weeks. If you are still on 4.1, please change your centos repos to point to http://mirror.centos.org/centos/7.4.1708/ instead of http://mirror.centos.org/centos/7. Then please update to latest 4.1 and then to oVirt 4.2 + CentOS 7.5 as soon as you can. Devel: please cross check your jenkins jobs, especially those having to do something with 4.1 since CentOS 7.5 is not supporting oVirt 4.1 anymore. See above. Infra: please schedule a mass update of oVirt infrastructure to CentOS 7.5 + oVirt 4.2.3 ASAP. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

5 17

hosted engine with openvswitch
by Sverker Abrahamsson 11 May '18

11 May '18

Hi I have a problem with running hosted engine with openvswitch. I have one cluster where the ovirt engine runs on the host, there it works and when starting a vm the interface definition looks like this: <interface type="bridge"> <address bus="0x00" domain="0x0000" function="0x0" slot="0x03" type="pci" /> <mac address="00:1a:4a:16:01:51" /> <model type="virtio" /> <source bridge="vdsmbr_2XMhqdgD" /> <virtualport type="openvswitch" /> <filterref filter="vdsm-no-mac-spoofing" /> </interface> The xml for that vm as fetched from vdsm does not contain virtualport tag nor does it use the correct bridge, it looks like this: <interface type="bridge"> <model type="virtio"/> <link state="up"/> <source bridge="ovirtmgmt"/> <address bus="0x00" domain="0x0000" function="0x0" slot="0x03" type="pci"/> <mac address="00:1a:4a:16:01:51"/> <filterref filter="vdsm-no-mac-spoofing"/> <bandwidth/> </interface> I.e. somewhere the definition is modified to contain the correct data to work with openvswitch On the other cluster where I try to run hosted engine I don't get the above behaviour. When the engine vm starts the interface settings are not modified to use the bridge in openvswitch, with the result that the vm fails to start: <interface type="bridge"> <model type="virtio"/> <link state="up"/> <source bridge="ovirtmgmt"/> <alias name="ua-430d692e-6ef0-4529-8af0-b37a53a11564"/> <address bus="0x00" domain="0x0000" function="0x0" slot="0x03" type="pci"/> <mac address="00:16:3e:0e:39:42"/> <filterref filter="vdsm-no-mac-spoofing"/> <bandwidth/> </interface> Last login: Thu May 10 16:23:48 2018 from 172.27.1.32 [root@h2 ~]# ovs-vsctl show dfcf7463-ce51-4115-9a3a-ecab9efa8146 Bridge "vdsmbr_H91hH5sG" Port "vdsmbr_H91hH5sG" Interface "vdsmbr_H91hH5sG" type: internal Port ovirtmgmt Interface ovirtmgmt type: internal Port "dummy0" Interface "dummy0" ovs_version: "2.9.0" I assumed first there is a hook that make the needed change, but the only hooks I can find that mentions openvswitch are ovirt_provider_ovn_hook and 50_openstacknet but both those would set the source bridge to br-int and not look up the dynamic name of the bridge as created by vdsm. One special thing about the host where I try to run hosted engine is that the there is a dummy port since otherwise I couldn't get vdsm to create the bridge, but that shouldn't affect changing the interface definition for the vm. Where should I look next?

3 3