- Users - oVirt List Archives

Hosted Engine VM - CPU and Memory Sizing
by paul.christian.suba＠cevalogistics.com 25 Jul '19

25 Jul '19

Hi, Is there a recommended CPU and memory size for the Hosted Engine VM? We have what started as a 4 node physical cluster lab with 4 vms that has now grown to 44vms. The dashboard is slow to load information and the HE VM is consistently seen with 99% CPU with the breakdown below. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 12076 postgres 20 0 506516 276172 143772 R 99.3 1.7 206:17.15 postmaster 10337 postgres 20 0 484756 254156 144000 R 99.0 1.6 179:52.35 postmaster 38603 postgres 20 0 500068 267836 143992 S 70.1 1.6 528:04.13 postmaster 49217 postgres 20 0 468736 235484 143624 S 19.3 1.4 41:57.55 postmaster 5569 ovirt 20 0 6430912 2.3g 6368 S 1.3 14.5 894:20.75 java We used the default 4 CPU and 16 GB RAM. This is oVirt 4.3.1. I am curious to find out as well if the postgres processes using 99% CPU is normal?

2 1

ovirt-engine-appliance ova
by jingjie.jiang＠oracle.com 25 Jul '19

25 Jul '19

Hi, Can someone tell me how to generate ovirt-engine-appliance ova file in ovirt-engine-appliance-4.3-20190610.1.el7.x86_64.rpm? I tried to import ovirt-engine-appliance ova(ovirt-engine-appliance-4.3-20190610.1.el7.ova) from ovirt-engine, but I got error as following: Failed to load VM configuration from OVA file: /var/tmp/ovirt-engine-appliance-4.2-20190121.1.el7.ova I guess ovirt-engine-appliance-4.2-20190121.1.el7.ova has more than CentOS7.6. Thanks, Jingjie

5 7

Re: major network changes
by Strahil 25 Jul '19

25 Jul '19

According to another post in the mailing list, the Engine Hosts (that has ovirt-ha-agent/ovirt-ha-broker running) is checking http://{fqdn}/ovirt-engine/services/health As the IP is changed, I think you need to check the URL before and after thr mifgration. Best Regards, Strahil NikolovOn Jul 23, 2019 16:41, Derek Atkins <derek(a)ihtfp.com> wrote: > > Hi, > > If I understand it correctly, the HE Hosts try to ping (or SSH, or > otherwise reach) the Engine host. If it reaches it, then it passes the > liveness check. If it cannot reach it, then it fails. So to me this error > means that there is some configuration, somewhere, that is trying to reach > the engine on the old address (which fails when the engine has the new > address). > > I do not know where in the *host* configuration this data lives, so I > cannot suggest where you need to change it. > > Can 10.16.248.x reach 10.8.236.x and vice-versa? > > Maybe multi-home the engine on both networks for now until you figure it out? > > -derek > > On Tue, July 23, 2019 9:13 am, carl langlois wrote: > > Hi, > > > > We have managed to stabilize the DNS udpate in out network. Now the > > current > > situation is. > > I have 3 hosts that can run the engine (hosted-engine). > > They were all in the 10.8.236.x. Now i have moved one of them in the > > 10.16.248.x. > > > > If i boot the engine on one of the host that is in the 10.8.236.x the > > engine is going up with status "good". I can access the engine UI. I can > > see all my hosts even the one in the 10.16.248.x network. > > > > But if i boot the engine on the hosted-engine host that was switch to the > > 10.16.248.x the engine is booting. I can ssh to it but the status is > > always > > " fail for liveliness check". > > The main difference is that when i boot on the host that is in the > > 10.16.248.x network the engine gets a address in the 248.x network. > > > > On the engine i have this in the > > /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log > > 019-07-23 > > 09:05:30|MFzehi|YYTDiS|jTq2w8|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 > > the engine.log seems okey. > > > > So i need to understand what this " liveliness check" do(or try to do) so > > i > > can investigate why the engine status is not becoming good. > > > > The initial deployment was done in the 10.8.236.x network. Maybe is as > > something to do with that. > > > > Thanks & Regards > > > > Carl > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 8:53 AM Miguel Duarte de Mora Barroso < > > mdbarroso(a)redhat.com> wrote: > > > >> On Thu, Jul 18, 2019 at 2:50 PM Miguel Duarte de Mora Barroso > >> <mdbarroso(a)redhat.com> wrote: > >> > > >> > On Thu, Jul 18, 2019 at 1:57 PM carl langlois <crl.langlois(a)gmail.com> > >> wrote: > >> > > > >> > > Hi Miguel, > >> > > > >> > > I have managed to change the config for the ovn-controler. > >> > > with those commands > >> > > ovs-vsctl set Open_vSwitch . external-ids:ovn-remote=ssl: > >> 10.16.248.74:6642 > >> > > ovs-vsctl set Open_vSwitch . external-ids:ovn-encap-ip=10.16.248.65 > >> > > and restating the services > >> > > >> > Yes, that's what the script is supposed to do, check [0]. > >> > > >> > Not sure why running vdsm-tool didn't work for you. > >> > > >> > > > >> > > But even with this i still have the "fail for liveliness check" when > >> starting the ovirt engine. But one thing i notice with our new network > >> is > >> that the reverse DNS does not work(IP -> hostname). The forward is > >> working > >> fine. I am trying to see with our IT why it is not working. > >> > > >> > Do you guys use OVN? If not, you could disable the provider, install > >> > the hosted-engine VM, then, if needed, re-add / re-activate it . > >> > >> I'm assuming it fails for the same reason you've stated initially - > >> i.e. ovn-controller is involved; if it is not, disregard this msg :) > >> > > >> > [0] - > >> https://github.com/oVirt/ovirt-provider-ovn/blob/master/driver/scripts/setu… > >> > > >> > > > >> > > Regards. > >> > > Carl > >>

4 6

Active-Passive DR: mutual for different storage domains possible?
by Gianluca Cecchi 25 Jul '19

25 Jul '19

Hello, suppose I want to implement Active-Passive DR between 2 sites. Sites are SiteA and SiteB. I have 2 storage domains SD1 and SD2, that I can configure so that SD1 is active in storage array installed in SiteA with replica in SiteB and SD2 the reverse. I have 4 hosts: host1 and host2 in SiteA and host3 and host4 in SiteB. I would like to optimize compute resources and workload so that: oVirt env OV1 with ovmgr1 in SiteA (external engine) is composed by host1 and host2 and configured with SD1 oVirt env OV2 with ovmgr2 in SiteB (external engine) is composed by host3 and host4 and configured with SD2. Can I use OV2 as DR for OV1 for VMs installed on SD1 and at the same time OV1 as DR for OV2 for VMs installed on SD2? Thanks in advance, Gianluca Cecchi

2 5

Failed Installation
by Marcello Gentile 25 Jul '19

25 Jul '19

I’m installing a self-hosted engine on CentOS7.6 using cockpit. Keep getting this error [ INFO ] TASK [ovirt.hosted_engine_setup : Wait for the host to be up] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Check host status] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The host has been set in non_operational status, please check engine logs, fix accordingly and re-deploy.\n"} [ INFO ] TASK [ovirt.hosted_engine_setup : Fetch logs from the engine VM] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set destination directory path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Create destination directory] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Find the local appliance image] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Set local_vm_disk_path] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Give the vm time to flush dirty buffers] [ INFO ] ok: [localhost -> localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Copy engine logs] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks] [ INFO ] ok: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove local vm dir] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Remove temporary entry in /etc/hosts for the local VM] [ INFO ] changed: [localhost] [ INFO ] TASK [ovirt.hosted_engine_setup : Notify the user about a failure] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n”} The logs don’t tell me much or at least the ones I’m checking Any help would be greatly appreciated Thanks

2 1

iSCSI-based storages won't login to the portals with all IPs on reboot
by nicolas＠devels.es 25 Jul '19

25 Jul '19

Hi, We're running oVirt 4.3.2. Currently, we have one storage backend (cabinet) with two controllers, each of them with 2 network interfaces (4 network interfaces in total). When we added the Storage Domain, we discovered the target for each of the 4 IPs and marked the LUN so it would be added with 4 different IPs. When we put a host on maintenance, all the paths are deactivated, and when we activate it back it discovers all the 4 paths for the storage backend. However, if we reboot the host, on activation it only activates one path. We can see this running 'multipath -ll'. We can manually activate the rest of the paths using this command for each of the IPs: # iscsiadm --mode discovery --type sendtargets --portal 10.X.X.X --login However, we wonder why oVirt wouldn't log into each of the IPs upon a boot. Is there something we're missing? Can this be fixed manually? Currently we're running a script on boot that will issue the command above for each of the IPs of the cabinet. Thanks for any help!

2 1

template permissions not inherited (4.3.4)
by Timmi 24 Jul '19

24 Jul '19

Hi oVirt List, I have just a quick question if I should open a ticket for this or if I'm doing something wrong. I created a new VM template with specific permissions in addition to the system wide permissions. If I create a new VM with the template I notices that only system permissions are copied to the permission of the new VM. Is this the intended behavior? I was somehow under the impression that the permission from the template should have been copied to the newly created VM. Tested with Version 4.3.4.3-1.el7 Best regards Christoph

4 6

if hosted engine corrupted
by Crazy Ayansh 24 Jul '19

24 Jul '19

Hi All, What is the way if self hosted engine corrupted in any environment and we need to setup it from scratch however on the new engine we need the same hosts and virtual machine without loosing data. Thanks Shashakn

2 1

reinstallation information
by nikkognt＠gmail.com 24 Jul '19

24 Jul '19

Hi, after a blackout one host of my ovirt not working properly. I tried to Reinstall it but ends with the following error "Failed to install Host ov1. Failed to execute stage 'Closing up': Failed to start service 'vdsmd'." I tried to start manually but it not start . Now, I would like to reinstall from iso ovirt node. After I put the host is in maintenance must I remove host from the cluster (Hosts -> host1 -> Remove) or I can reinstall without remove it? If I remore it from the cluster the network configurations I lose them or not? My ovirt version is oVirt Engine Version: 4.1.9.1-1.el7.centos.

2 6

Re: Storage domain 'Inactive' but still functional
by Strahil 24 Jul '19

24 Jul '19

I forgot to mention that LVM config has to be modified in order to 'inform' local LVM stack to rely on clvmd/dlm for locking purposes. Yet, this brings abother layer of complexity which I prefer to avoid , thus I use HA-LVM on my pacemaker clusters. @Martin, Check the link from Benny and if possible check if the 2 cases are related. Best Regards, Strahil NikolovOn Jul 24, 2019 11:07, Benny Zlotnik <bzlotnik(a)redhat.com> wrote: > > We have seen something similar in the past and patches were posted to deal with this issue, but it's still in progress[1] > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1553133 > > On Mon, Jul 22, 2019 at 8:07 PM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> I have a theory... But after all without any proof it will remain theory. >> >> The storage volumes are just VGs over a shared storage.The SPM host is supposed to be the only one that is working with the LVM metadata, but I have observed that when someone is executing a simple LVM command (for example -lvs, vgs or pvs ) while another one is going on on another host - your metadata can corrupt, due to lack of clvmd. >> >> As a protection, I could offer you to try the following solution: >> 1. Create new iSCSI lun >> 2. Share it to all nodes and create the storage domain. Set it to maintenance. >> 3. Start dlm & clvmd services on all hosts >> 4. Convert the VG of your shared storage domain to have a 'cluster'-ed flag: >> vgchange -c y mynewVG >> 5. Check the lvs of that VG. >> 6. Activate the storage domain. >> >> Of course test it on a test cluster before inplementing it on Prod. >> This is one of the approaches used in Linux HA clusters in order to avoid LVM metadata corruption. >> >> Best Regards, >> Strahil Nikolov >> >> On Jul 22, 2019 15:46, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl> wrote: >>> >>> Hi, >>> >>> Op 22-7-2019 om 14:30 schreef Strahil: >>>> >>>> If you can give directions (some kind of history) , the dev might try to reproduce this type of issue. >>>> >>>> If it is reproduceable - a fix can be provided. >>>> >>>> Based on my experience, if something as used as Linux LVM gets broken, the case is way hard to reproduce. >>> >>> >>> Yes, I'd think so too, especially since this activity (online moving of disk images) is done all the time, mostly without problems. In this case, there was a lot of activity on all storage domains, because I'm moving all my storage (> 10TB in 185 disk images) to a new storage platform. During the online move of one the images, the metadata checksum became corrupted and the storage domain went offline. >>> >>> Of course, I could dig up the engine logs and vdsm logs of when it happened, but that would be some work and I'm not very confident that the actual cause would be in there. >>> >>> If any oVirt devs are interested in the logs, I'll provide them, but otherwise I think I'll just see it as an incident and move on. >>> >>> Best regards, >>> Martijn. >>> >>> >>> >>> >>> On Jul 22, 2019 10:17, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl> wrote: >>>>> >>>>> Hi, >>>>> >>>>> Thanks for the tips! I didn't know about 'pvmove', thanks. >>>>> >>>>> In the mean time, I managed to get it fixed by restoring the VG metadata on the iSCSI server, so on the underlying Zvol directly, rather than via the iSCSI session on the oVirt host. That allowed me to perform the restore without bringing all VMs down, which was important to me, because if I had to shut down VMs, I was sure I wouldn't be able to restart them before the storage domain was back online. >>>>> >>>>> Of course this is a more a Linux problem than an oVirt problem, but oVirt did cause it ;-) >>>>> >>>>> Thanks, >>>>> Martijn. >>>>> >>>>> >>>>> >>>>> Op 19-7-2019 om 19:06 schreef Strahil Nikolov: >>>>>> >>>>>> Hi Martin, >>>>>> >>>>>> First check what went wrong with the VG -as it could be something simple. >>>>>> vgcfgbackup -f VGname will create a file which you can use to compare current metadata with a previous version. >>>>>> >>>>>> If you have Linux boxes - you can add disks from another storage an

1 0

Re: Storage domain 'Inactive' but still functional
by Martijn Grendelman 24 Jul '19

24 Jul '19

Op 24-7-2019 om 10:07 schreef Benny Zlotnik: We have seen something similar in the past and patches were posted to deal with this issue, but it's still in progress[1] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1553133 That's some interesting reading, and it sure looks like the problem I had. Thanks! Best regards, Martijn. On Mon, Jul 22, 2019 at 8:07 PM Strahil <hunter86_bg(a)yahoo.com<mailto:hunter86_bg@yahoo.com>> wrote: I have a theory... But after all without any proof it will remain theory. The storage volumes are just VGs over a shared storage.The SPM host is supposed to be the only one that is working with the LVM metadata, but I have observed that when someone is executing a simple LVM command (for example -lvs, vgs or pvs ) while another one is going on on another host - your metadata can corrupt, due to lack of clvmd. As a protection, I could offer you to try the following solution: 1. Create new iSCSI lun 2. Share it to all nodes and create the storage domain. Set it to maintenance. 3. Start dlm & clvmd services on all hosts 4. Convert the VG of your shared storage domain to have a 'cluster'-ed flag: vgchange -c y mynewVG 5. Check the lvs of that VG. 6. Activate the storage domain. Of course test it on a test cluster before inplementing it on Prod. This is one of the approaches used in Linux HA clusters in order to avoid LVM metadata corruption. Best Regards, Strahil Nikolov On Jul 22, 2019 15:46, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl<mailto:Martijn.Grendelman@isaac.nl>> wrote: Hi, Op 22-7-2019 om 14:30 schreef Strahil: If you can give directions (some kind of history) , the dev might try to reproduce this type of issue. If it is reproduceable - a fix can be provided. Based on my experience, if something as used as Linux LVM gets broken, the case is way hard to reproduce. Yes, I'd think so too, especially since this activity (online moving of disk images) is done all the time, mostly without problems. In this case, there was a lot of activity on all storage domains, because I'm moving all my storage (> 10TB in 185 disk images) to a new storage platform. During the online move of one the images, the metadata checksum became corrupted and the storage domain went offline. Of course, I could dig up the engine logs and vdsm logs of when it happened, but that would be some work and I'm not very confident that the actual cause would be in there. If any oVirt devs are interested in the logs, I'll provide them, but otherwise I think I'll just see it as an incident and move on. Best regards, Martijn. On Jul 22, 2019 10:17, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl><mailto:Martijn.Grendelman@isaac.nl> wrote: Hi, Thanks for the tips! I didn't know about 'pvmove', thanks. In the mean time, I managed to get it fixed by restoring the VG metadata on the iSCSI server, so on the underlying Zvol directly, rather than via the iSCSI session on the oVirt host. That allowed me to perform the restore without bringing all VMs down, which was important to me, because if I had to shut down VMs, I was sure I wouldn't be able to restart them before the storage domain was back online. Of course this is a more a Linux problem than an oVirt problem, but oVirt did cause it ;-) Thanks, Martijn. Op 19-7-2019 om 19:06 schreef Strahil Nikolov: Hi Martin, First check what went wrong with the VG -as it could be something simple. vgcfgbackup -f VGname will create a file which you can use to compare current metadata with a previous version. If you have Linux boxes - you can add disks from another storage and then pvmove the data inside the VM. Of course , you will need to reinstall grub on the new OS disk , or you won't be able to boot afterwards. If possible, try with a test VM before proceeding with important ones. Backing up the VMs is very important , because working on LVM metada _______________________________________________ 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/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/37UDAWDXON3UR… -- Met vriendelijke groet, Kind regards, [Martijn]<mailto:martijn.grendelman@isaac.nl> Martijn Grendelman Infrastructure Architect T: +31 (0)40 264 94 44 [ISAAC]<https://www.isaac.nl> ISAAC Marconilaan 16 5621 AA Eindhoven The Netherlands T: +31 (0)40 290 89 79 www.isaac.nl<https://www.isaac.nl> [ISAAC #1 Again!]<https://www.isaac.nl/nl/over-ons/nieuws/isaac-news/ISAAC-voor-tweede-keer-n…> Dit e-mail bericht is alleen bestemd voor de geadresseerde(n). Indien dit bericht niet voor u is bedoeld wordt u verzocht de afzender hiervan op de hoogte te stellen door het bericht te retourneren en de inhoud niet te gebruiken. Aan dit bericht kunnen geen rechten worden ontleend.

1 0

Re: Storage domain 'Inactive' but still functional
by Strahil 24 Jul '19

24 Jul '19

I have a theory... But after all without any proof it will remain theory. The storage volumes are just VGs over a shared storage.The SPM host is supposed to be the only one that is working with the LVM metadata, but I have observed that when someone is executing a simple LVM command (for example -lvs, vgs or pvs ) while another one is going on on another host - your metadata can corrupt, due to lack of clvmd. As a protection, I could offer you to try the following solution: 1. Create new iSCSI lun 2. Share it to all nodes and create the storage domain. Set it to maintenance. 3. Start dlm & clvmd services on all hosts 4. Convert the VG of your shared storage domain to have a 'cluster'-ed flag: vgchange -c y mynewVG 5. Check the lvs of that VG. 6. Activate the storage domain. Of course test it on a test cluster before inplementing it on Prod. This is one of the approaches used in Linux HA clusters in order to avoid LVM metadata corruption. Best Regards, Strahil NikolovOn Jul 22, 2019 15:46, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl> wrote: > > Hi, > > Op 22-7-2019 om 14:30 schreef Strahil: >> >> If you can give directions (some kind of history) , the dev might try to reproduce this type of issue. >> >> If it is reproduceable - a fix can be provided. >> >> Based on my experience, if something as used as Linux LVM gets broken, the case is way hard to reproduce. > > > Yes, I'd think so too, especially since this activity (online moving of disk images) is done all the time, mostly without problems. In this case, there was a lot of activity on all storage domains, because I'm moving all my storage (> 10TB in 185 disk images) to a new storage platform. During the online move of one the images, the metadata checksum became corrupted and the storage domain went offline. > > Of course, I could dig up the engine logs and vdsm logs of when it happened, but that would be some work and I'm not very confident that the actual cause would be in there. > > If any oVirt devs are interested in the logs, I'll provide them, but otherwise I think I'll just see it as an incident and move on. > > Best regards, > Martijn. > > > > > On Jul 22, 2019 10:17, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl> wrote: >>> >>> Hi, >>> >>> Thanks for the tips! I didn't know about 'pvmove', thanks. >>> >>> In the mean time, I managed to get it fixed by restoring the VG metadata on the iSCSI server, so on the underlying Zvol directly, rather than via the iSCSI session on the oVirt host. That allowed me to perform the restore without bringing all VMs down, which was important to me, because if I had to shut down VMs, I was sure I wouldn't be able to restart them before the storage domain was back online. >>> >>> Of course this is a more a Linux problem than an oVirt problem, but oVirt did cause it ;-) >>> >>> Thanks, >>> Martijn. >>> >>> >>> >>> Op 19-7-2019 om 19:06 schreef Strahil Nikolov: >>>> >>>> Hi Martin, >>>> >>>> First check what went wrong with the VG -as it could be something simple. >>>> vgcfgbackup -f VGname will create a file which you can use to compare current metadata with a previous version. >>>> >>>> If you have Linux boxes - you can add disks from another storage and then pvmove the data inside the VM. Of course , you will need to reinstall grub on the new OS disk , or you won't be able to boot afterwards. >>>> If possible, try with a test VM before proceeding with important ones. >>>> >>>> Backing up the VMs is very important , because working on LVM metada

2 1

USB turns off and wont come alive
by Darin Schmidt 24 Jul '19

24 Jul '19

I have 2 usb controllers installed via a riser card plugged into a M.2 slot. (Like those used for mining with GPU's). Everything works great for a long time, then my Windows 10 VM freezes and I lose all USB activity. LSPCI still sees the devices: 0a:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller 0b:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller 43:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller 44:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller I assume a and b are the same physical card as its supposed to have 2 channels each, same with 44 and 43. I tried for both 44 and 43 echo "1" > /sys/bus/pci/devices/0000\:43\:00.0/remove echo "1" > /sys/bus/pci/rescan echo "1" > /sys/bus/pci/devices/0000\:43\:00.0/reset This did not work. I cannot determine if its just the VM thats no longer seeing/using the hardware or if its the hardware itself. I wonder if its a power state thing as well? Nothing I plug into the card seems to be recognized. Any Suggestions? rebooting the VM doesnt help either. It appears the hardware is functioning, but anything you plug into it isnt being detected.

2 1

Import VM from ovirt-exported ova
by david.paning＠gmx.ch 24 Jul '19

24 Jul '19

Hello, i installed a new oVirt 4.3.4 from scratch and am attempting to restore the VMs which ran perfectly fine on my last oVirt 4.2.8, where i exported the VM to the export domain and also as an OVA file. Importing the export domain fails, which i plan to debug later. But importing the OVA file via the Administration Portal also fails with Error ID: 1153 Message: Failed to import the VM to Data Center, Cluster. The VM name is still recognised by the import routine, which tells me the file is readable... Now my questions: Is there any option to try the same from CLI, hoping to get better clues for what is going on? Are there specific log options which could give some clues? Would it be better in general to import the VM from an export-storage domain instead of using a OVA export? Any hint would highly appreciated. Best

3 2

Re: major network changes
by Strahil 23 Jul '19

23 Jul '19

Hi Carl, I think there is another thread here related to the migration to another network. As far as I know, the check liveliness try's to access the ovirt's health page. Does the new engine's ip has A/PTR record setup? Also, check the engine logs, once the HostedEngine VM is up and running. Best Regards, Strahil NikolovOn Jul 23, 2019 16:13, carl langlois <crl.langlois(a)gmail.com> wrote: > > Hi, > > We have managed to stabilize the DNS udpate in out network. Now the current situation is. > I have 3 hosts that can run the engine (hosted-engine). > They were all in the 10.8.236.x. Now i have moved one of them in the 10.16.248.x. > > If i boot the engine on one of the host that is in the 10.8.236.x the engine is going up with status "good". I can access the engine UI. I can see all my hosts even the one in the 10.16.248.x network. > > But if i boot the engine on the hosted-engine host that was switch to the 10.16.248.x the engine is booting. I can ssh to it but the status is always " fail for liveliness check". > The main difference is that when i boot on the host that is in the 10.16.248.x network the engine gets a address in the 248.x network. > > On the engine i have this in the /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log > 019-07-23 09:05:30|MFzehi|YYTDiS|jTq2w8|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 > the engine.log seems okey. > > So i need to understand what this " liveliness check" do(or try to do) so i can investigate why the engine status is not becoming good. > > The initial deployment was done in the 10.8.236.x network. Maybe is as something to do with that. > > Thanks & Regards > > Carl > > > > > > > > > > > > > > > > > > > On Thu, Jul 18, 2019 at 8:53 AM Miguel Duarte de Mora Barroso <mdbarroso(a)redhat.com> wrote: >> >> On Thu, Jul 18, 2019 at 2:50 PM Miguel Duarte de Mora Barroso >> <mdbarroso(a)redhat.com> wrote: >> > >> > On Thu, Jul 18, 2019 at 1:57 PM carl langlois <crl.langlois(a)gmail.com> wrote: >> > > >> > > Hi Miguel, >> > > >> > > I have managed to change the config for the ovn-controler. >> > > with those commands >> > > ovs-vsctl set Open_vSwitch . external-ids:ovn-remote=ssl:10.16.248.74:6642 >> > > ovs-vsctl set Open_vSwitch . external-ids:ovn-encap-ip=10.16.248.65 >> > > and restating the services >> > >> > Yes, that's what the script is supposed to do, check [0]. >> > >> > Not sure why running vdsm-tool didn't work for you. >> > >> > > >> > > But even with this i still have the "fail for liveliness check" when starting the ovirt engine. But one thing i notice with our new network is that the reverse DNS does not work(IP -> hostname). The forward is working fine. I am trying to see with our IT why it is not working. >> > >> > Do you guys use OVN? If not, you could disable the provider, install >> > the hosted-engine VM, then, if needed, re-add / re-activate it . >> >> I'm assuming it fails for the same reason you've stated initially - >> i.e. ovn-controller is involved; if it is not, disregard this msg :) >> > >> > [0] - https://github.com/oVirt/ovirt-provider-ovn/blob/master/driver/scripts/setu… >> > >> > > >> > > Regards. >> > > Carl >> > > >> > > On Thu, Jul 18, 2019 at 4:03 AM Miguel Duarte de Mora Barroso <mdbarroso(a)redhat.com> wrote: >> > >> >> > >> On Wed, Jul 17, 2019 at 7:07 PM carl langlois <crl.langlois(a)gmail.com> wrote: >> > >> > >> > >> > Hi >> > >> > Here is the output of the command >> > >> > >> > >> > [root@ovhost1 ~]# vdsm-tool --vvverbose ovn-config 10.16.248.74 ovirtmgmt >> > >> > MainThread::DEBUG::2019-07-17 13:02:52,

1 0

Stuck in "Finalizing" disk upload phase
by Vrgotic, Marko 23 Jul '19

23 Jul '19

Dear oVIrt, I initiated upload of qcow2 disk image for Centos 6.5: It reached finalizing phase and than started throwing following errors: 2019-07-17 14:40:51,480Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-86) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Finalizing successful transfer for Upload disk 'av-07-centos-65-base' (disk id: '3452459d-aec6-430e-9509-1d9ca815b2d8', image id: 'b44659a9-607a-4eeb-a255-99532fd4fce4') 2019-07-17 14:40:51,480Z WARN [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-86) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Failed to stop image transfer session. Ticket does not exist for image '3452459d-aec6-430e-9509-1d9ca815b2d8' 2019-07-17 14:41:01,572Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Finalizing successful transfer for Upload disk 'av-07-centos-65-base' (disk id: '3452459d-aec6-430e-9509-1d9ca815b2d8', image id: 'b44659a9-607a-4eeb-a255-99532fd4fce4') 2019-07-17 14:41:01,574Z WARN [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-19) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Failed to stop image transfer session. Ticket does not exist for image '3452459d-aec6-430e-9509-1d9ca815b2d8' 2019-07-17 14:41:11,690Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-7) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Finalizing successful transfer for Upload disk 'av-07-centos-65-base' (disk id: '3452459d-aec6-430e-9509-1d9ca815b2d8', image id: 'b44659a9-607a-4eeb-a255-99532fd4fce4') 2019-07-17 14:41:11,690Z WARN [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-7) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Failed to stop image transfer session. Ticket does not exist for image '3452459d-aec6-430e-9509-1d9ca815b2d8' 2019-07-17 14:41:21,781Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Finalizing successful transfer for Upload disk 'av-07-centos-65-base' (disk id: '3452459d-aec6-430e-9509-1d9ca815b2d8', image id: 'b44659a9-607a-4eeb-a255-99532fd4fce4') 2019-07-17 14:41:21,782Z WARN [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [a43180ec-afc7-429e-9f30-9e851eaf7ce7] Failed to stop image transfer session. Ticket does not exist for image '3452459d-aec6-430e-9509-1d9ca815b2d8' I can not cancel it, can not stop it, not via UI not via force option using ovirt_disk module. Help! oVIrt 4.3.4.3-1 version running with CentOS 7.6 Hosts. Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic ActiveVideo

3 17

major network changes
by carl langlois 23 Jul '19

23 Jul '19

Hi We are in a process of changing our network connection. Our current network is using 10.8.256.x and we will change to 10.16.248.x. We have a HA ovirt cluster (around 10 nodes) currently configure on the 10.8.256.x. So my question is is it possible to relocate the ovirt cluster to the 10.16.248.x. We have tried to move everything to the new network without success. All the node seem to boot up properly, our gluster storage also work properly. When we try to start the hosted-engine it goes up but fail the liveliness check. We have notice in the /var/log/openvswitch/ovn-controller.log that he is triying to connect to the hold ip address of the hosted-engine vm. 019-07-16T18:41:29.483Z|01992|reconnect|INFO|ssl:10.8.236.244:6642: waiting 8 seconds before reconnect 2019-07-16T18:41:37.489Z|01993|reconnect|INFO|ssl:10.8.236.244:6642: connecting... 2019-07-16T18:41:45.497Z|01994|reconnect|INFO|ssl:10.8.236.244:6642: connection attempt timed out So my question is were is the 10.8.236.244 come from. The routing table for one of our host look like this estination Gateway Genmask Flags Metric Ref Use Iface default gateway 0.0.0.0 UG 0 0 0 ovirtmgmt 10.16.248.0 0.0.0.0 255.255.255.0 U 0 0 0 ovirtmgmt link-local 0.0.0.0 255.255.0.0 U 1002 0 0 eno1 link-local 0.0.0.0 255.255.0.0 U 1003 0 0 eno2 link-local 0.0.0.0 255.255.0.0 U 1025 0 0 ovirtmgmt Any help would be really appreciated. Regards Carl

3 12

Attach the snapshot to the backup virtual machine and activate the disk
by smidhunraj＠gmail.com 23 Jul '19

23 Jul '19

This is the doubt regarding to the rest api <https://ovirt.org/documentation/admin-guide/chap-Backups_and_Migration.html…> Can you please tell me what would be the response of the api request of step 4 ((will it be a success or a error)) ===================================================================== Attach the snapshot to the backup virtual machine and activate the disk: POST /api/vms/22222222-2222-2222-2222-222222222222/disks/ HTTP/1.1 Accept: application/xml Content-type: application/xml <disk id="11111111-1111-1111-1111-111111111111"> <snapshot id="11111111-1111-1111-1111-111111111111"/> <active>true</active> </disk> ============================================================================================== if we are setting up a bare VM without any backup mechanism in it and try to attach a vm to it.

1 0

Re: ovirt-engine-appliance ova
by Strahil 23 Jul '19

23 Jul '19

It looks like a kickstart error. Maybe a parameter in the kickstart is missing ? Best Regards, Strahil NikolovOn Jul 23, 2019 09:08, Yedidyah Bar David <didi(a)redhat.com> wrote: > > On Mon, Jul 22, 2019 at 11:53 PM Jingjie Jiang <jingjie.jiang(a)oracle.com> wrote: >> >> Hi David, > > > (Actually it's "Yedidyah" or "Didi") > >> >> Thanks for your info. >> >> Please check my reply inline. >> >> >> -Jingjie >> >> On 7/16/19 3:55 AM, Yedidyah Bar David wrote: >>> >>> On Thu, Jul 11, 2019 at 10:46 PM <jingjie.jiang(a)oracle.com> wrote: >>> >>>> Hi, >>>> >>>> Can someone tell me how to generate ovirt-engine-appliance ova file in ovirt-engine-appliance-4.3-20190610.1.el7.x86_64.rpm? >>>> >>> You might want to check the project's source code: >>> >>> >>> >>> https://github.com/ovirt/ovirt-appliance/ >>> >>> >>> >>> Or study the logs of a CI build of it: >>> >>> >>> >>> https://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x8… >>> >>> >>> >>> I never tried building it myself locally, though. >> >> I tried to build after checked out the source code from https://github.com/ovirt/ovirt-appliance/, >> >> but the build failed. >> >> # make >> livemedia-creator --make-disk --ram=2048 --vcpus=4 --iso=boot.iso --ks=ovirt-engine-appliance.ks --qcow2 --image-name=ovirt-engine-appliance.qcow2 >> 2019-07-22 12:34:00,095: livemedia-creator 19.7.19-1 >> 2019-07-22 12:34:00,154: disk_size = 51GiB >> 2019-07-22 12:34:00,154: disk_img = /var/tmp/ovirt-engine-appliance.qcow2 >> 2019-07-22 12:34:00,154: install_log = /root/ovirt/ovirt-appliance/engine-appliance/virt-install.log >> mount: /dev/loop0 is write-protected, mounting read-only >> Formatting '/var/tmp/ovirt-engine-appliance.qcow2', fmt=qcow2 size=54760833024 encryption=off cluster_size=65536 lazy_refcounts=off >> 2019-07-22 12:34:10,195: Running virt-install. >> >> Starting install... >> Retrieving file vmlinuz... | 6.3 MB 00:00 >> Retrieving file initrd.img... | 50 MB 00:00 >> Domain installation still in progress. You can reconnect to >> the console to complete the installation process. >> ...... >> 2019-07-22 12:35:15,281: Installation error detected. See logfile. >> 2019-07-22 12:35:15,283: Shutting down LiveOS-27f2dc2b-4b30-4eb1-adcd-b5ab50fdbf55 >> Domain LiveOS-27f2dc2b-4b30-4eb1-adcd-b5ab50fdbf55 destroyed >> >> Domain LiveOS-27f2dc2b-4b30-4eb1-adcd-b5ab50fdbf55 has been undefined >> >> 2019-07-22 12:35:15,599: unmounting the iso >> 2019-07-22 12:35:20,612: Install failed: virt_install failed >> 2019-07-22 12:35:20,613: Removing bad disk image >> 2019-07-22 12:35:20,613: virt_install failed >> make: *** [ovirt-engine-appliance.qcow2] Error 1 >> >> In the log I found the error as following from virt-install.log: >> >> 16:35:07,472 ERR anaconda:CmdlineError: The following mandatory spokes are not completed:#012Installation source#012Software selection >> 16:35:07,472 DEBUG anaconda:running handleException >> 16:35:07,473 CRIT anaconda:Traceback (most recent call last):#012#012 File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/simpleline/base.py", line 352, in _mainloop#012 prompt = last_screen.prompt(self._screens[-1][1])#012#012 File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/tui/hubs/summary.py", line 107, in prompt#012 raise CmdlineError(errtxt)#012#012CmdlineError: The following mandatory spokes are not completed:#012Installation source#012Software selection >> 16:35:08,020 DEBUG anaconda:Gtk cannot be initialized >> 16:35:08,020 DEBUG anaconda:In the main thread, running exception handler >> 16:35:08,386 NOTICE multipathd:zram0: add path (uevent) >> 16:35:08,386 NOTICE multipathd:zram0: spurious uevent, path already in pathvec >> 16:35:08,386 NOTICE multipathd:zram0: HDIO_GETGEO failed with 25 >> 16:35:08,386 ERR multipathd:zram0: failed to get path uid >> 16:35:08,388 ERR multipathd:uevent trigger error >> >> Can you help me to fix the issue? > > > Sorry, I never tried to build it myself, nor have experience with livemedia-creator. As I wrote above, I suggest to compare your output/result with that of oVirt CI. Otherwise, I'd probably start debugging by searching the net for the error messages you received. > > Good luck and best regards, > >> >> >>>> I tried to import ovirt-engine-appliance ova(ovirt-engine-appliance-4.3-20190610.1.el7.ova) from ovirt-engine, but I got error as following: >>>> >>>> Failed to load VM configuration from OVA file: /var/tmp/ovirt-engine-appliance-4.2-20190121.1.el7.ova >>>> >>> No idea why this failed. >>> >>> >>> >>>> I guess ovirt-engine-appliance-4.2-20190121.1.el7.ova has more than CentOS7.6. >>>> >>> It has CentOS + oVirt engine. >>> >>> >>> >>> The only major use for it is by hosted-engine --deploy. In theory you >>> >>> can try importing it elsewhere, but I do not recall reports about >>> >>> people that tried this and whether it works. >>> >>> >>> >>> Best regards, >>> > > > -- > Didi

1 0

guest agent w10
by suporte＠logicworks.pt 22 Jul '19

22 Jul '19

Hello, I installed Qemu guest agent 7.4.5 on windows 10. The service is running, but I cannot see the IP address or the FQDN on the engine. I'm running oVirt 4.3.4.3-1.el7 Am I forgetting something? Thanks -- Jose Ferradeira http://www.logicworks.pt

2 2

Request for clarification of logline
by Vrgotic, Marko 22 Jul '19

22 Jul '19

Dear oVirt, I was not able to find out meaning behind following WARN message: WARN [org.ovirt.engine.core.vdsbroker.libvirt.VmDevicesConverter] (EE-ManagedThreadFactory-engineScheduled-Thread-50) [] unmanaged disk with path '/var/run/vdsm/payload/0687ad1a-4827-48d9-8629-b29a000df280.760410382a41ff5e6b1ee9365856517e.img' is ignored Will somebody be so kind to clarify the actual meaning of it or point me in right direction of cause? I can provide more information if required. Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic ActiveVideo

3 4

Cinderlib managed block storage, ceph jewel
by mathias.schwenke＠uni-dortmund.de 22 Jul '19

22 Jul '19

Hi. I tried to use manged block storage to connect our oVirt cluster (Version 4.3.4.3-1.el7) to our ceph storage ( version 10.2.11). I used the instructions from https://ovirt.org/develop/release-management/features/storage/cinderlib-int… At the moment, in the ovirt administration portal I can create and delete ceph volumes (ovirt disks) and attach them to virtual machines. If I try to launch a vm with connected ceph block storage volume, starting fails: 2019-07-16 19:39:09,251+02 WARN [org.ovirt.engine.core.vdsbroker.vdsbroker.AttachManagedBlockStorageVolumeVDSCommand] (default task-53) [7cada945] Unexpected return value: Status [code=926, message=Managed Volume Helper failed.: ('Error executing helper: Command [\'/usr/libexec/vdsm/managedvolume-helper\', \'attach\'] failed with rc=1 out=\'\' err=\'oslo.privsep.daemon: Running privsep helper: [\\\'sudo\\\', \\\'privsep-helper\\\', \\\'--privsep_context\\\', \\\'os_brick.privileged.default\\\', \\\'--privsep_sock_path\\\', \\\'/tmp/tmpB6ZBAs/privsep.sock\\\']\\noslo.privsep.daemon: Spawned new privsep daemon via rootwrap\\noslo.privsep.daemon: privsep daemon starting\\noslo.privsep.daemon: privsep process running with uid/gid: 0/0\\noslo.privsep.daemon: privsep process running with capabilities (eff/prm/inh): CAP_SYS_ADMIN/CAP_SYS_ADMIN/none\\noslo.privsep.daemon: privsep daemon running as pid 112531\\nTraceback (most recent call last):\\n File "/usr/libexec/vdsm/managedvolume-help er", line 154, in <module>\\n sys.exit(main(sys.argv[1:]))\\n File "/usr/libexec/vdsm/managedvolume-helper", line 77, in main\\n args.command(args)\\n File "/usr/libexec/vdsm/managedvolume-helper", line 137, in attach\\n attachment = conn.connect_volume(conn_info[\\\'data\\\'])\\n File "/usr/lib/python2.7/site-packages/vdsm/storage/nos_brick.py", line 96, in connect_volume\\n run_as_root=True)\\n File "/usr/lib/python2.7/site-packages/os_brick/executor.py", line 52, in _execute\\n result = self.__execute(*args, **kwargs)\\n File "/usr/lib/python2.7/site-packages/os_brick/privileged/rootwrap.py", line 169, in execute\\n return execute_root(*cmd, **kwargs)\\n File "/usr/lib/python2.7/site-packages/oslo_privsep/priv_context.py", line 205, in _wrap\\n return self.channel.remote_call(name, args, kwargs)\\n File "/usr/lib/python2.7/site-packages/oslo_privsep/daemon.py", line 202, in remote_call\\n raise exc_type(*result[2])\\noslo_concurrency.processutils.Pr ocessExecutionError: Unexpected error while running command.\\nCommand: rbd map volume-a57dbd5c-2f66-460f-b37f-5f7dfa95d254 --pool ovirt-volumes --conf /tmp/brickrbd_TLMTkR --id ovirtcinderlib --mon_host 192.168.61.1:6789 --mon_host 192.168.61.2:6789 --mon_host 192.168.61.3:6789\\nExit code: 6\\nStdout: u\\\'RBD image feature set mismatch. You can disable features unsupported by the kernel with "rbd feature disable".\\\\nIn some cases useful info is found in syslog - try "dmesg | tail" or so.\\\\n\\\'\\nStderr: u\\\'rbd: sysfs write failed\\\\nrbd: map failed: (6) No such device or address\\\\n\\\'\\n\'',)] 2019-07-16 19:39:09,251+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.AttachManagedBlockStorageVolumeVDSCommand] (default task-53) [7cada945] Failed in 'AttachManagedBlockStorageVolumeVDS' method After disconnecting the disk, I can delete it (the volume disappears from ceph), but the disks stays in my oVirt administration portal as cinderlib means the disk ist still connected: 2019-07-16 19:42:53,551+02 INFO [org.ovirt.engine.core.bll.storage.disk.RemoveDiskCommand] (EE-ManagedThreadFactory-engine-Thread-487362) [887b4d11-302f-4f8d-a3f9-7443a80a47ba] Running command: RemoveDiskCommand internal: false. Entities affected : ID: a57dbd5c-2f66-460f-b37f-5f7dfa95d254 Type: DiskAction group DELETE_DISK with role type USER 2019-07-16 19:42:53,559+02 INFO [org.ovirt.engine.core.bll.storage.disk.managedblock.RemoveManagedBlockStorageDiskCommand] (EE-ManagedThreadFactory-commandCoordinator-Thread-8) [] Running command: RemoveManagedBlockStorageDiskCommand internal: true. 2019-07-16 19:42:56,240+02 ERROR [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor] (EE-ManagedThreadFactory-commandCoordinator-Thread-8) [] cinderlib execution failed DBReferenceError: (psycopg2.IntegrityError) update or delete on table "volumes" violates foreign key constraint "volume_attachment_volume_id_fkey" on table "volume_attachment" 2019-07-16 19:42:55,958 - cinderlib-client - INFO - Deleting volume 'a57dbd5c-2f66-460f-b37f-5f7dfa95d254' [887b4d11-302f-4f8d-a3f9-7443a80a47ba] 2019-07-16 19:42:56,099 - cinderlib-client - ERROR - Failure occurred when trying to run command 'delete_volume': (psycopg2.IntegrityError) update or delete on table "volumes" violates foreign key constraint "volume_attachment_volume_id_fkey" on table "volume_attachment" DETAIL: Key (id)=(a57dbd5c-2f66-460f-b37f-5f7dfa95d254) is still referenced from table "volume_attachment". [SQL: 'DELETE FROM volumes WHERE volumes.deleted = false AND volumes.id = %(id_1)s'] [parameters: {'id_1': u'a57dbd5c-2f66-460f-b37f-5f7dfa95d254'}] [887b4d11-302f-4f8d-a3f9-7443a80a47ba] How are your experiences with oVirt, cinderlib and ceph? Should it work?

3 3

Change vDisk ID
by Николаев Алексей 22 Jul '19

22 Jul '19

1 0

Re: Storage domain 'Inactive' but still functional
by Strahil 22 Jul '19

22 Jul '19

If you can give directions (some kind of history) , the dev might try to reproduce this type of issue. If it is reproduceable - a fix can be provided. Based on my experience, if something as used as Linux LVM gets broken, the case is way hard to reproduce. Best Regards, Strahil NikolovOn Jul 22, 2019 10:17, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl> wrote: > > Hi, > > Thanks for the tips! I didn't know about 'pvmove', thanks. > > In the mean time, I managed to get it fixed by restoring the VG metadata on the iSCSI server, so on the underlying Zvol directly, rather than via the iSCSI session on the oVirt host. That allowed me to perform the restore without bringing all VMs down, which was important to me, because if I had to shut down VMs, I was sure I wouldn't be able to restart them before the storage domain was back online. > > Of course this is a more a Linux problem than an oVirt problem, but oVirt did cause it ;-) > > Thanks, > Martijn. > > > > Op 19-7-2019 om 19:06 schreef Strahil Nikolov: >> >> Hi Martin, >> >> First check what went wrong with the VG -as it could be something simple. >> vgcfgbackup -f VGname will create a file which you can use to compare current metadata with a previous version. >> >> If you have Linux boxes - you can add disks from another storage and then pvmove the data inside the VM. Of course , you will need to reinstall grub on the new OS disk , or you won't be able to boot afterwards. >> If possible, try with a test VM before proceeding with important ones. >> >> Backing up the VMs is very important , because working on LVM metadata is quite risky. >> Last time I had such an issue , I was working on clustered LVs which got their PVs "Missing". For me , restore from VG backup fixed the issue - but that might not be always the case. >> >> Just get the vgcfgbackup's output and compare with diff or vimdiff and check what is different. >> >> Sadly, I think that this is more a Linux problem , than an oVirt problem. >> >> Best Regards, >> Strahil Nikolov >> >> В четвъртък, 18 юли 2019 г., 18:51:32 ч. Гринуич+3, Martijn Grendelman <Martijn.Grendelman(a)isaac.nl> написа: >> >> >> Hi! >> >> Thanks. Like I wrote, I have metadata backups from /etc/lvm/backup and -/archive, and I also have the current metadata as it exis

1 0

LiveStoreageMigration failed
by Christoph Köhler 22 Jul '19

22 Jul '19

Hello, I try to migrate a disk of a running vm from gluster 3.12.15 to gluster 3.12.15 but it fails. libGfApi set to true by engine-config. ° taking a snapshot first, is working. Then at engine-log: 2019-07-18 09:29:13,932+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskStartVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Failed in 'VmReplicateDiskStartVDS' method 2019-07-18 09:29:13,936+02 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovvirt07 command VmReplicateDiskStartVDS failed: Drive replication error 2019-07-18 09:29:13,936+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskStartVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskStartVDSCommand' return value 'StatusOnlyReturn [status=Status [code=55, message=Drive replication error]]' 2019-07-18 09:29:13,936+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskStartVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] HostName = ovvirt07 2019-07-18 09:29:13,937+02 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskStartVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Command 'VmReplicateDiskStartVDSCommand(HostName = ovvirt07, VmReplicateDiskParameters:{hostId='3a7bf85c-e92d-4559-908e-5eed2f5608d4', vmId='3b79d0c0-47e9-47c3-8511-980a8cfe147c', storagePoolId='00000001-0001-0001-0001-000000000311', srcStorageDomainId='e54d835a-d8a5-44ae-8e17-fcba1c54e46f', targetStorageDomainId='4dabb6d6-4be5-458c-811d-6d5e87699640', imageGroupId='d2964ff9-10f7-4b92-8327-d68f3cfd5b50', imageId='62656632-8984-4b7e-8be1-fd2547ca0f98'})' execution failed: VDSGenericException: VDSErrorException: Failed to VmReplicateDiskStartVDS, error = Drive replication error, code = 55 2019-07-18 09:29:13,937+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.VmReplicateDiskStartVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] FINISH, VmReplicateDiskStartVDSCommand, return: , log id: 5b2afb0b 2019-07-18 09:29:13,937+02 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Failed VmReplicateDiskStart (Disk 'd2964ff9-10f7-4b92-8327-d68f3cfd5b50' , VM '3b79d0c0-47e9-47c3-8511-980a8cfe147c') 2019-07-18 09:29:13,938+02 ERROR [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Command 'LiveMigrateDisk' id: '8174c74c-8ab0-49fa-abfc-44d8b7c691e0' with children [03672b60-443b-47ba-834c-ac306d7129d0, 562522fc-6691-47fe-93bf-ef2c45e85676] failed when attempting to perform the next operation, marking as 'ACTIVE' 2019-07-18 09:29:13,938+02 ERROR [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] EngineException: Drive replication error (Failed with error replicaErr and code 55): org.ovirt.engine.core.common.errors.EngineException: EngineException: Drive replication error (Failed with error replicaErr and code 55) at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.replicateDiskStart(LiveMigrateDiskCommand.java:526) [bll.jar:] at org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand.performNextOperation(LiveMigrateDiskCommand.java:233) [bll.jar:] at org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback.childCommandsExecutionEnded(SerialChildCommandsExecutionCallback.java:32) [bll.jar:] at org.ovirt.engine.core.bll.ChildCommandsCallbackBase.doPolling(ChildCommandsCallbackBase.java:77) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethodsImpl(CommandCallbacksPoller.java:175) [bll.jar:] at org.ovirt.engine.core.bll.tasks.CommandCallbacksPoller.invokeCallbackMethods(CommandCallbacksPoller.java:109) [bll.jar:] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_212] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [rt.jar:1.8.0_212] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383) [javax.enterprise.concurrent-1.0.jar:] at org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534) [javax.enterprise.concurrent-1.0.jar:] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_212] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_212] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_212] at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) [javax.enterprise.concurrent-1.0.jar:] at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:78) 2019-07-18 09:29:13,938+02 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-84) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Command 'LiveMigrateDisk' id: '8174c74c-8ab0-49fa-abfc-44d8b7c691e0' child commands '[03672b60-443b-47ba-834c-ac306d7129d0, 562522fc-6691-47fe-93bf-ef2c45e85676]' executions were completed, status 'FAILED' 2019-07-18 09:29:15,019+02 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Ending command 'org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand' with failure. 2019-07-18 09:29:15,019+02 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [c957e011-37e0-43aa-abe7-9bb633c38c5f] Failed during live storage migration of disk 'd2964ff9-10f7-4b92-8327-d68f3cfd5b50' of vm '3b79d0c0-47e9-47c3-8511-980a8cfe147c', attempting to end replication before deleting the target disk // LiveStorageMigration on gluster - should that work at all? Has someone tried it? Greetings! Christoph Köhler

4 5