- Users - oVirt List Archives

Engine can not support CORS by openidconnect
by du_hongyu＠yeah.net 04 Apr '19

04 Apr '19

hi， I write a openIDconnect client to authentication my web app from ovirt-engine-4.2.0， this is my engine config : [root@engine ~]# engine-config -a |grep CORS CORSSupport: true version: general CORSAllowedOrigins: https://10.110.128.129 version: general CORSAllowDefaultOrigins: true version: general CORSDefaultOriginSuffixes: :9090 version: general but face some error： Access to fetch at 'https://10.110.128.120/ovirt-engine/sso/openid/authorize?response_type=code…' (redirected from 'https://10.110.128.129/console/auth/login') from origin 'https://10.110.128.129' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: Redirect is not allowed for a preflight request. engine log(I add log info ) is: 019-04-04 10:16:52,491+08 INFO [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-4) [] engine=======strippedScope [openid, ovirt-app-portal, ovirt-app-admin, ovirt-app-api, ovirt-ext=token:password-access, ovirt-ext=auth:sequence-priority, ovirt-ext=token:login-on-behalf, ovirt-ext=token-info:authz-search, ovirt-ext=token-info:public-authz-search, ovirt-ext=token-info:validate, ovirt-ext=revoke:revoke-all] 2019-04-04 10:16:52,492+08 INFO [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-4) [] engine=======requestedScope [openid, ovirt-app-admin, ovirt-app-api, ovirt-app-portal, ovirt-ext=auth:sequence-priority, ovirt-ext=revoke:revoke-all, ovirt-ext=token-info:authz-search, ovirt-ext=token-info:public-authz-search, ovirt-ext=token-info:validate, ovirt-ext=token:login-on-behalf, ovirt-ext=token:password-access] and I realize this java source not run, i do not find any log in engine.log backend/manager/modules/utils/src/main/java/org/ovirt/engine/core/utils/servlet/CORSSupportFilter.java Regards Hongyu Du

1 0

How can i do about this?
by yangwei68＠hotmail.com 04 Apr '19

04 Apr '19

It is my question,please look at the picture ; https://share.weiyun.com/5LvNdRx

1 1

Re: Vm status not update after update
by Strahil 03 Apr '19

03 Apr '19

Sadly I couldn't find the e-mail with the fix. As far as I remember , there should be a bug opened for that. Best Regards, Strahil NikolovOn Apr 3, 2019 13:53, Marcelo Leandro <marceloltmm(a)gmail.com> wrote: > > Hi, > > Strahil , can you help me? > > Very thanks, > > Marcelo Leandro > > Em ter, 2 de abr de 2019 10:02, Marcelo Leandro <marceloltmm(a)gmail.com> escreveu: >> >> Sorry, I can't find this. >> >> Em ter, 2 de abr de 2019 às 09:49, Strahil Nikolov <hunter86_bg(a)yahoo.com> escreveu: >>> >>> I think I already met a solution in the mail lists. Can you check and apply the fix mentioned there ? >>> >>> Best Regards, >>> Strahil Nikolov >>> >>> В вторник, 2 април 2019 г., 14:39:10 ч. Гринуич+3, Marcelo Leandro <marceloltmm(a)gmail.com> написа: >>> >>> >>> Hi, After update my hosts to ovirt node 4.3.2 with vdsm version vdsm-4.30.11-1.el7 my vms status not update, if I do anything with vm like shutdown, migrate this status not change , only a restart the vdsm the host that vm is runnig. >>> >>> vdmd status : >>> >>> ERROR Internal server error >>> Traceback (most recent call last): >>> File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request.. >>> >>> Thanks, >>> _______________________________________________ >>> Users mailing list -- users(a)ovirt.org >>> To unsubscribe send an email to

1 0

Problem after pxe booting
by matteo fedeli 03 Apr '19

03 Apr '19

Hi i'm unable to start installation of ovirt node because after PXE server booted the installer stuck on an infinite source installation loading (see this: https://scontent-mxp1-1.xx.fbcdn.net/v/t1.0-9/56380126_1095871103950798_594…) My cfg config: default vesamenu.c32 timeout 200 LABEL oVirt43 MENU LABEL oVirt 4.3 KERNEL vmlinuz APPEND initrd=initrd.img inst.stage2=http://192.168.4.200/oVirt430/ Any ideas? Anaconda docs (https://rhinstaller.github.io/anaconda/boot-options.html?highlight=treeinfo) says that need a .treeinfo , in my case missing... Is for that reason?

1 0

vdsClient in oVirt 4.3
by nicolas＠devels.es 03 Apr '19

03 Apr '19

Hi, In oVirt 4.1 we used this command to set a volume as LEGAL: vdsClient -s <host> setVolumeLegality sdUUID spUUID imgUUID leafUUID LEGAL What would be the equivalent to this command using vdsm-client in oVirt 4.3? Thanks.

3 6

Vm status not update after update
by Marcelo Leandro 03 Apr '19

03 Apr '19

Hi, After update my hosts to ovirt node 4.3.2 with vdsm version vdsm-4.30.11-1.el7 my vms status not update, if I do anything with vm like shutdown, migrate this status not change , only a restart the vdsm the host that vm is runnig. vdmd status : ERROR Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345, in _handle_request.. Thanks,

2 3

Actual size bigger than virtual size
by suporte＠logicworks.pt 03 Apr '19

03 Apr '19

Hi, I have an all in one ovirt 4.2.2 with gluster storage and a couple of windows 2012 VMs. One w2012 is showing actual size 209GiB and Virtual Size 150 GiB on a thin provision disk. The vm shows 30,9 GB of used space. This VM is slower than the others mainly when we reboot the machine it takes around 2 hours. Any idea? Thanks -- Jose Ferradeira http://www.logicworks.pt

3 5

Why/how does oVirt fsync over NFS
by Karli Sjöberg 03 Apr '19

03 Apr '19

Hello! This question arose after the (in my opinion) hasty response from a user that thinks oVirt is bad because it cares about the integrity of your data: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QPVXUFW2U3WGJ… Fine, that's their choice. They can have silent data corruption all they want in case of a power failure or something, it's up to them if they think it's worth it. However, I started wondering why oVirt sync's everything over NFS, I know it does because you can in ZFS turn it off by "zfs set sync=disabled <dataset>" and throughput and everything goes through the roof. The right way is of course to add a SLOG or better yet a mirrored pair but just for a quick test or whatever... But their doesn't seem to be any reason why oVirt should do that, that's why I'm asking. Look, this is from the CentOS 'mount' man page: "defaults Use default options: rw, suid, dev, exec, auto, nouser, and async." So therefore 'sync' should be explicitly set on the mount, right? Wrong! # mount | grep -c sync 0 So why then does it sync? The NFS man page says: "The sync mount option The NFS client treats the sync mount option differently than some other file systems (refer to mount(8) for a description of the generic sync and async mount options). If neither sync nor async is specified (or if the async option is specified), the NFS client delays sending application writes to the server until any of these events occur: Memory pressure forces reclamation of system memory resources. An application flushes file data explicitly with sync(2), msync(2), or fsync(3). An application closes a file with close(2). The file is locked/unlocked via fcntl(2)." So which of these things are happening for the Host to send sync calls to the NFS server? Just curious... /K

1 0

4.2 / 4.3 : Moving the hosted-engine to another storage
by andreas.elvers+ovirtforum＠solutions.work 03 Apr '19

03 Apr '19

Hi friends of oVirt, Roughly 3 years ago a user asked about the options he had to move the hosted engine to some other storage. The answer by Simone Tiraboschi was that it would largely not be possible, because of references in the database to the node the engine was hosted. This information would prevent a successful move of the engine even with backup/restore. The situation seem to have improved, but I'm not sure. So I ask. We have to move our engine away from our older Cluster with NFS Storage backends (engine, volumes, iso-images). The engine should be restored on our new cluster that has a gluster volume available for the engine. Additionally this 3-node cluster is running Guests from a Cinder/Ceph storage Domain. I want to restore the engine on a different cluster to a different storage domain. Reading the documentation at https://www.ovirt.org/documentation/self-hosted/chap-Backing_up_and_Restori… I am wondering whether oVirt Nodes (formerly Node-NG) are capable of restoring an engine at all. Do I need EL-based Nodes? We are currently running on oVirt Nodes. - Andreas

4 6

Re: oVirt Performance (Horrific)
by Strahil 03 Apr '19

03 Apr '19

Hi Drew, What is the host RAM size and what is the setting for VM.dirty_ratio and background ratio on those hosts? What about your iSCSI target? Best Regards, Strahil Nikolov On Mar 11, 2019 23:51, Drew Rash <drew.rash(a)gmail.com> wrote: > > Added the disable:false, removed the gluster, re-added using nfs. Performance still in the low 10's MBps + or - 5 > Ran the showmount -e "" and it displayed the mount. > > Trying right now to re-mount using gluster with a negative-timeout=1 option. > > We converted one of our 4 boxes to FreeNAS, took 4 6TB drives and made a raid iSCSI and connected it to oVirt. Boot windows. ( times 2, did 2 boxes with a 7GB file on each) copied from one to the other and it copied at 600MBps average. But then has weird pauses... I think it's doing some kind of cache..it'll go like 2GB and choke to zero Bps. Then speed up and choke, speed up choke averaging or getting up to 10MBps. Then at 99% it waits 15 seconds with 0 bytes left... > Small files, are instant basically. No complaint there. > So...WAY faster. But suffers from the same thing....just requires writing some more to get to it. a few gigs and then it crawls. > > Seems to be related to if I JUST finished running a test. If I wait a while, I get it it to copy almost 4GB or so before choking. > I made a 3rd windows 10 VM and copied the same file from the 1st to the 2nd (via a windows share and from the 3rd box) And it didn't choke or do any funny business...oddly. Maybe a fluke. Only did that once. > > So....switching to freenas appears to have increased the window size before it runs horribly. But it will still run horrifically if the disk is busy. > > And since we're planning on doing actual work on this... idle disks caching up on some hidden cache feature of oVirt isn't gonna work. We won't be writing gigs of data all over the place...but knowing that this chokes a VM to near death...is scary. > > It looks like for a windows 10 install to operate correctly, it expects at least 15MB/s with less than 1s latency. Otherwise services don't start and weird stuff happens and it runs slower than my dog while pooping out that extra little stringy bit near the end. So we gotta avoid that. > > > > > On Sat, Mar 9, 2019 at 12:44 AM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Hj Drew, >> >> For the test change the gluster parameter nfs.disabled to false. >> Something like gluster volume set volname nfs.dsiable false >> >> Then use shownount -e gluster-node-fqdn >> Note: NFS might not be allowed in the firewall. >> >> Then add this NFS domain (don't forget to remove the gluster storage domain before that) and do your tests. >> >> If it works well, you will have to switch off nfs.disable and deploy NFS Ganesha: >> >> gluster volume reset volname nfs.disable >> >> Best Regards, >> Strahil Nikolov

4 4

HE - engine gluster volume - not mounted
by Leo David 02 Apr '19

02 Apr '19

Hello Everyone, Using 4.3.2 installation, and after running through HyperConverged Setup, at the last stage it fails. It seems that the previously created "engine" volume is not mounted under "/rhev" path, therefore the setup cannot finish the deployment. Any ideea which are the services responsible of mounting the volumes on oVirt Node distribution ? I'm thinking that maybe this particularly one failed to start for some reason... Thank you very much ! -- Best regards, Leo David

4 11

Backup VMs to external USB Disk
by daniel94.oeller＠gmail.com 02 Apr '19

02 Apr '19

Hi all, I'm new in Ovirt and have tested a lot of things how to backup my VMS to a external USB Disk. How have you solved this Problem - have anybody a Tutorial or something similar for me? Thanks for your helps. Daniel

2 3

Fwd: Re: HE - engine gluster volume - not mounted
by Leo David 02 Apr '19

02 Apr '19

---------- Forwarded message --------- From: Leo David <leoalex(a)gmail.com> Date: Tue, Apr 2, 2019, 15:10 Subject: Re: [ovirt-users] Re: HE - engine gluster volume - not mounted To: Sahina Bose <sabose(a)redhat.com> I have deleted everything in the engine gluster mount path, unmounted the engine gluster volume ( not deleted the volume ) , and started the wizard with "Use already configured storage". I have pointed to use this gluster volume, volume gets mounted under the correct path, but installation still fails: [ INFO ] TASK [ovirt.hosted_engine_setup : Activate storage domain] [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[]". HTTP response code is 400. [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[]\". HTTP response code is 400."} On the node's vdsm.log I can continuously see: 2019-04-02 13:02:18,832+0100 INFO (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC call Host.getStats succeeded in 0.03 seconds (__init__:312) 2019-04-02 13:02:19,906+0100 INFO (vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) from=internal, task_id=769c3983-5160-44e4-b1d8-7ab4e41ddd34 (api:48) 2019-04-02 13:02:19,907+0100 INFO (vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': []} from=internal, task_id=769c3983-5160-44e4-b1d8-7ab4e41ddd34 (api:54) 2019-04-02 13:02:19,907+0100 INFO (vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:709) 2019-04-02 13:02:21,737+0100 INFO (periodic/2) [vdsm.api] START repoStats(domains=()) from=internal, task_id=ba12fbc1-0170-41a2-82e6-8ccb05ae9e09 (api:48) 2019-04-02 13:02:21,738+0100 INFO (periodic/2) [vdsm.api] FINISH repoStats return={} from=internal, task_id=ba12fbc1-0170-41a2-82e6-8ccb05ae9e09 (api:54) Should I perform an "engine-cleanup", delete lvms from Cockpit and start it all over ? Did anyone successfully used this particular iso image "ovirt-node-ng-installer-4.3.2-2019031908.el7.iso" for a single node installation ? Thank you ! Leo On Tue, Apr 2, 2019 at 1:45 PM Sahina Bose <sabose(a)redhat.com> wrote: > Is it possible you have not cleared the gluster volume between installs? > > What's the corresponding error in vdsm.log? > > > On Tue, Apr 2, 2019 at 4:07 PM Leo David <leoalex(a)gmail.com> wrote: > > > > And there it is the last lines on the ansible_create_storage_domain log: > > > > 2019-04-02 10:53:49,139+0100 DEBUG var changed: host "localhost" var > "otopi_storage_domain_details" type "<type 'dict'>" value: "{ > > "changed": false, > > "exception": "Traceback (most recent call last):\n File > \"/tmp/ansible_ovirt_storage_domain_payload_6Jxg5v/__main__.py\", line 664, > in main\n storage_domains_module.post_create_check(sd_id)\n File > \"/tmp/ansible_ovirt_storage_domain_payload_6Jxg5v/__main__.py\", line 526, > in post_create_check\n id=storage_domain.id,\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py\", line 3053, in > add\n return self._internal_add(storage_domain, headers, query, wait)\n > File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 232, > in _internal_add\n return future.wait() if wait else future\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 55, in > wait\n return self._code(response)\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 229, in > callback\n self._check_fault(response)\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 132, in > _check_fault\n self._raise_error(response, body)\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 118, in > _raise_error\n raise error\nError: Fault reason is \"Operation Failed\". > Fault detail is \"[]\". HTTP response code is 400.\n", > > "failed": true, > > "msg": "Fault reason is \"Operation Failed\". Fault detail is > \"[]\". HTTP response code is 400." > > }" > > 2019-04-02 10:53:49,141+0100 DEBUG var changed: host "localhost" var > "ansible_play_hosts" type "<type 'list'>" value: "[]" > > 2019-04-02 10:53:49,141+0100 DEBUG var changed: host "localhost" var > "play_hosts" type "<type 'list'>" value: "[]" > > 2019-04-02 10:53:49,142+0100 DEBUG var changed: host "localhost" var > "ansible_play_batch" type "<type 'list'>" value: "[]" > > 2019-04-02 10:53:49,142+0100 ERROR ansible failed {'status': 'FAILED', > 'ansible_type': 'task', 'ansible_task': u'Activate storage domain', > 'ansible_result': u'type: <type \'dict\'>\nstr: {\'_ansible_parsed\': True, > u\'exception\': u\'Traceback (most recent call last):\\n File > "/tmp/ansible_ovirt_storage_domain_payload_6Jxg5v/__main__.py", line 664, > in main\\n storage_domains_module.post_create_check(sd_id)\\n File > "/tmp/ansible_ovirt_storage_domain_payload_6Jxg5v/__main__.py", line 526', > 'task_duration': 9, 'ansible_host': u'localhost', 'ansible_playbook': > u'/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml'} > > 2019-04-02 10:53:49,143+0100 DEBUG ansible on_any args > <ansible.executor.task_result.TaskResult object at 0x7f03fd025e50> kwargs > ignore_errors:None > > 2019-04-02 10:53:49,148+0100 INFO ansible stats { > > "ansible_playbook": > "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml", > > "ansible_playbook_duration": "01:15 Minutes", > > "ansible_result": "type: <type 'dict'>\nstr: {u'localhost': > {'unreachable': 0, 'skipped': 6, 'ok': 23, 'changed': 0, 'failures': 1}}", > > "ansible_type": "finish", > > "status": "FAILED" > > } > > 2019-04-02 10:53:49,149+0100 INFO SUMMARY: > > Duration Task Name > > -------- -------- > > [ < 1 sec ] Execute just a specific set of steps > > [ 00:02 ] Force facts gathering > > [ 00:02 ] Check local VM dir stat > > [ 00:02 ] Obtain SSO token using username/password credentials > > [ 00:02 ] Fetch host facts > > [ 00:01 ] Fetch cluster ID > > [ 00:02 ] Fetch cluster facts > > [ 00:02 ] Fetch Datacenter facts > > [ 00:01 ] Fetch Datacenter ID > > [ 00:01 ] Fetch Datacenter name > > [ 00:02 ] Add glusterfs storage domain > > [ 00:02 ] Get storage domain details > > [ 00:02 ] Find the appliance OVF > > [ 00:02 ] Parse OVF > > [ 00:02 ] Get required size > > [ FAILED ] Activate storage domain > > > > Any ideea on how to escalate this issue ? > > It just does not make sense to not be able to install from scratch a > fresh node... > > > > Have a nice day ! > > > > Leo > > > > > > On Tue, Apr 2, 2019 at 12:11 PM Gobinda Das <godas(a)redhat.com> wrote: > >> > >> Hi Leo, > >> Can you please paste "df -Th" and "gluster v status" out put ? > >> Wanted to make sure engine mounted and volumes and bricks are up. > >> What does vdsm log say? > >> > >> On Tue, Apr 2, 2019 at 2:06 PM Leo David <leoalex(a)gmail.com> wrote: > >>> > >>> Thank you very much ! > >>> I have just installed a new fresh node, and triggered the single > instance hyperconverged setup. It seems it fails at the hosted engine final > steps of deployment: > >>> INFO ] TASK [ovirt.hosted_engine_setup : Get required size] > >>> [ INFO ] ok: [localhost] > >>> [ INFO ] TASK [ovirt.hosted_engine_setup : Remove unsuitable storage > domain] > >>> [ INFO ] skipping: [localhost] > >>> [ INFO ] TASK [ovirt.hosted_engine_setup : Check storage domain free > space] > >>> [ INFO ] skipping: [localhost] > >>> [ INFO ] TASK [ovirt.hosted_engine_setup : Activate storage domain] > >>> [ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is > "[Cannot attach Storage. There is no active Host in the Data Center.]". > HTTP response code is 409. > >>> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": > "Fault reason is \"Operation Failed\". Fault detail is \"[Cannot attach > Storage. There is no active Host in the Data Center.]\". HTTP response code > is 409."} > >>> Also, the > ovirt-hosted-engine-setup-ansible-create_storage_domain-201932112413-xkq6nb.log > throws the following: > >>> > >>> 2019-04-02 09:25:40,420+0100 DEBUG var changed: host "localhost" var > "otopi_storage_domain_details" type "<type 'dict'>" value: "{ > >>> "changed": false, > >>> "exception": "Traceback (most recent call last):\n File > \"/tmp/ansible_ovirt_storage_domain_payload_87MSyY/__main__.py\", line 664, > in main\n storage_domains_module.post_create_check(sd_id)\n File > \"/tmp/ansible_ovirt_storage_domain_payload_87MSyY/__main__.py\", line 526, > in post_create_check\n id=storage_domain.id,\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py\", line 3053, in > add\n return self._internal_add(storage_domain, headers, query, wait)\n > File \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 232, > in _internal_add\n return future.wait() if wait else future\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 55, in > wait\n return self._code(response)\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 229, in > callback\n self._check_fault(response)\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 132, in > _check_fault\n self._raise_error(response, body)\n File > \"/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py\", line 118, in > _raise_error\n raise error\nError: Fault reason is \"Operation Failed\". > Fault detail is \"[Cannot attach Storage. There is no active Host in the > Data Center.]\". HTTP response code is 409.\n", > >>> "failed": true, > >>> "msg": "Fault reason is \"Operation Failed\". Fault detail is > \"[Cannot attach Storage. There is no active Host in the Data Center.]\". > HTTP response code is 409." > >>> }" > >>> > >>> I have used the ovirt-node-ng-installer-4.3.2-2019031908.el7.iso. So > far, I am unable to deploy oVirt single node Hyperconverged... > >>> Any thoughts ? > >>> > >>> > >>> > >>> On Mon, Apr 1, 2019 at 9:46 PM Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > >>>> > >>>> > >>>> > >>>> On Mon, Apr 1, 2019 at 6:14 PM Leo David <leoalex(a)gmail.com> wrote: > >>>>> > >>>>> Thank you Simone. > >>>>> I've decides to go for a new fresh install from iso, and i'll keep > posted if any troubles arise. But I am still trying to understand what are > the services that mount the lvms and volumes after configuration. There is > nothing related in fstab, so I assume there are a couple of .mount files > somewhere in the filesystem. > >>>>> Im just trying to understand node's underneath workflow. > >>>> > >>>> > >>>> hosted-engine configuration is stored in > /etc/ovirt-hosted-engine/hosted-engine.conf; ovirt-ha-broker will mount the > hosted-engine storage domain according to that and so ovirt-ha-agent will > be able to start the engine VM. > >>>> Everything else is just in the engine DB. > >>>> > >>>>> > >>>>> > >>>>> On Mon, Apr 1, 2019, 10:16 Simone Tiraboschi <stirabos(a)redhat.com> > wrote: > >>>>>> > >>>>>> Hi, > >>>>>> to understand what's failing I'd suggest to start attaching setup > logs. > >>>>>> > >>>>>> On Sun, Mar 31, 2019 at 5:06 PM Leo David <leoalex(a)gmail.com> > wrote: > >>>>>>> > >>>>>>> Hello Everyone, > >>>>>>> Using 4.3.2 installation, and after running through HyperConverged > Setup, at the last stage it fails. It seems that the previously created > "engine" volume is not mounted under "/rhev" path, therefore the setup > cannot finish the deployment. > >>>>>>> Any ideea which are the services responsible of mounting the > volumes on oVirt Node distribution ? I'm thinking that maybe this > particularly one failed to start for some reason... > >>>>>>> Thank you very much ! > >>>>>>> > >>>>>>> -- > >>>>>>> Best regards, Leo David > >>>>>>> _______________________________________________ > >>>>>>> Users mailing list -- users(a)ovirt.org > >>>>>>> To unsubscribe send an email to users-leave(a)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/PUXDAQHVNZWF4… > >>> > >>> > >>> > >>> -- > >>> Best regards, Leo David > >>> _______________________________________________ > >>> Users mailing list -- users(a)ovirt.org > >>> To unsubscribe send an email to users-leave(a)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/NROCMKIFJDEIW… > >> > >> > >> > >> -- > >> > >> > >> Thanks, > >> Gobinda > > > > > > > > -- > > Best regards, Leo David > > _______________________________________________ > > Users mailing list -- users(a)ovirt.org > > To unsubscribe send an email to users-leave(a)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/XDJNBS6EOXCMJ… > -- Best regards, Leo David

1 0

trying to use Managed Block Storage in 4.3.2 with Ceph / Authentication Keys
by Matthias Leopold 02 Apr '19

02 Apr '19

Hi, I upgraded my test environment to 4.3.2 and now I'm trying to set up a "Managed Block Storage" domain with our Ceph 12.2 cluster. I think I got all prerequisites, but when saving the configuration for the domain with volume_driver "cinder.volume.drivers.rbd.RBDDriver" (and a couple of other options) I get "VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Error connecting to ceph cluster" in engine log (full error below). Unfortunately this is a rather generic error message and I don't really know where to look next. Accessing the rbd pool from the engine host with rbd CLI and the configured "rbd_user" works flawlessly... Although I don't think this is directly connected there is one other question that comes up for me: how are libvirt "Authentication Keys" handled with Ceph "Managed Block Storage" domains? With "standalone Cinder" setups like we are using now you have to configure a "provider" of type "OpenStack Block Storage" where you can configure these keys that are referenced in cinder.conf as "rbd_secret_uuid". How is this supposed to work now? Thanks for any advice, we are using oVirt with Ceph heavily and are very interested in a tight integration of oVirt and Ceph. Matthias 2019-04-01 11:14:55,128+02 ERROR [org.ovirt.engine.core.common.utils.cinderlib.CinderlibExecutor] (default task-22) [b6665621-6b85-438e-8c68-266f33e55d79] cinderlib execution failed: Traceback (most recent call last): File "./cinderlib-client.py", line 187, in main args.command(args) File "./cinderlib-client.py", line 275, in storage_stats backend = load_backend(args) File "./cinderlib-client.py", line 217, in load_backend return cl.Backend(**json.loads(args.driver)) File "/usr/lib/python2.7/site-packages/cinderlib/cinderlib.py", line 87, in __init__ self.driver.check_for_setup_error() File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/rbd.py", line 288, in check_for_setup_error with RADOSClient(self): File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/rbd.py", line 170, in __init__ self.cluster, self.ioctx = driver._connect_to_rados(pool) File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/rbd.py", line 346, in _connect_to_rados return _do_conn(pool, remote, timeout) File "/usr/lib/python2.7/site-packages/cinder/utils.py", line 799, in _wrapper return r.call(f, *args, **kwargs) File "/usr/lib/python2.7/site-packages/retrying.py", line 229, in call raise attempt.get() File "/usr/lib/python2.7/site-packages/retrying.py", line 261, in get six.reraise(self.value[0], self.value[1], self.value[2]) File "/usr/lib/python2.7/site-packages/retrying.py", line 217, in call attempt = Attempt(fn(*args, **kwargs), attempt_number, False) File "/usr/lib/python2.7/site-packages/cinder/volume/drivers/rbd.py", line 344, in _do_conn raise exception.VolumeBackendAPIException(data=msg) VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Error connecting to ceph cluster.

2 8

Strange storage data center failure
by Fabrice Bacchella 02 Apr '19

02 Apr '19

I have a storage data center that I can't use. It's a local one. When I look on vdsm.log: 2019-04-02 10:55:48,336+0200 INFO (jsonrpc/2) [vdsm.api] FINISH connectStoragePool error=Cannot find master domain: u'spUUID=063d1217-6194-48a0-943e-3d873f2147de, msdUUID=49b1bd15-486a-4064-878e-8030c8108e09' from=::ffff:XXXXX,59590, task_id=a56a5869-a219-4659-baa3-04f673b2ad55 (api:50) 2019-04-02 10:55:48,336+0200 ERROR (jsonrpc/2) [storage.TaskManager.Task] (Task='a56a5869-a219-4659-baa3-04f673b2ad55') 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 connectStoragePool File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1035, in connectStoragePool spUUID, hostID, msdUUID, masterVersion, domainsMap) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 1097, in _connectStoragePool res = pool.connect(hostID, msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 700, in connect self.__rebuild(msdUUID=msdUUID, masterVersion=masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1274, in __rebuild self.setMasterDomain(msdUUID, masterVersion) File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1495, in setMasterDomain raise se.StoragePoolMasterNotFound(self.spUUID, msdUUID) StoragePoolMasterNotFound: Cannot find master domain: u'spUUID=063d1217-6194-48a0-943e-3d873f2147de, msdUUID=49b1bd15-486a-4064-878e-8030c8108e09' 2019-04-02 10:55:48,336+0200 INFO (jsonrpc/2) [storage.TaskManager.Task] (Task='a56a5869-a219-4659-baa3-04f673b2ad55') aborting: Task is aborted: "Cannot find master domain: u'spUUID=063d1217-6194-48a0-943e-3d873f2147de, msdUUID=49b1bd15-486a-4064-878e-8030c8108e09'" - code 304 (task:1181) 2019-04-02 11:44:50,862+0200 INFO (jsonrpc/0) [vdsm.api] FINISH getSpmStatus error=Unknown pool id, pool not connected: (u'063d1217-6194-48a0-943e-3d873f2147de',) from=::ffff:10.83.16.34,46546, task_id=cfb1c871-b1d4-4b1a-b2a5-f91ddfaba 54b (api:50) 2019-04-02 11:44:50,862+0200 ERROR (jsonrpc/0) [storage.TaskManager.Task] (Task='cfb1c871-b1d4-4b1a-b2a5-f91ddfaba54b') 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 getSpmStatus File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 634, in getSpmStatus pool = self.getPool(spUUID) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 350, in getPool raise se.StoragePoolUnknown(spUUID) StoragePoolUnknown: Unknown pool id, pool not connected: (u'063d1217-6194-48a0-943e-3d873f2147de',) 063d1217-6194-48a0-943e-3d873f2147de is indeed the datacenter id and 49b1bd15-486a-4064-878e-8030c8108e09 the storage domain: <storage_domain href="/ovirt-engine/api/storagedomains/49b1bd15-486a-4064-878e-8030c8108e09" id="49b1bd15-486a-4064-878e-8030c8108e09"> <storage> <type>fcp</type> <volume_group id="cEOxNG-R4fv-EDo3-Y3lm-ZMAH-xOT4-Nn8QyP"> <logical_units> </logical_units> </volume_group> </storage> <storage_format>v4</storage_format> <data_centers> <data_center href="/ovirt-engine/api/datacenters/063d1217-6194-48a0-943e-3d873f2147de" id="063d1217-6194-48a0-943e-3d873f2147de"/> </data_centers> </storage_domain> On engine.log, I'm also getting: 2019-04-02 11:43:57,531+02 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [] Command 'org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand' return value ' TaskStatusListReturn:{status='Status [code=654, message=Not SPM: ()]'} ' lsblk shows that the requested volumes are here: lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT cciss!c0d1 104:16 0 1.9T 0 disk |-49b1bd15--486a--4064--878e--8030c8108e09-metadata 253:0 0 512M 0 lvm |-49b1bd15--486a--4064--878e--8030c8108e09-outbox 253:1 0 128M 0 lvm |-49b1bd15--486a--4064--878e--8030c8108e09-xleases 253:2 0 1G 0 lvm |-49b1bd15--486a--4064--878e--8030c8108e09-leases 253:3 0 2G 0 lvm |-49b1bd15--486a--4064--878e--8030c8108e09-ids 253:4 0 128M 0 lvm |-49b1bd15--486a--4064--878e--8030c8108e09-inbox 253:5 0 128M 0 lvm |-49b1bd15--486a--4064--878e--8030c8108e09-master 253:6 0 1G 0 lvm |-49b1bd15--486a--4064--878e--8030c8108e09-6225ddc3--b600--49ef--8de4--6e53bf4cad1f 253:7 0 128M 0 lvm `-49b1bd15--486a--4064--878e--8030c8108e09-bdac3a3a--8633--41bf--921d--db2cf31f5d1c 253:8 0 128M 0 lvm There is no usefull data on them. So I don't mind destroying everything. But using the GUI I can't do any thing on that domain. I'm runing 4.2.7.5-1.el7 on rhel 7.6

1 0

oVirt Survey 2019 results
by Sandro Bonazzola 02 Apr '19

02 Apr '19

Thanks to the 143 participants to oVirt Survey 2019! The survey is now closed and results are publicly available at https://bit.ly/2JYlI7U We'll analyze collected data in order to improve oVirt thanks to your feedback. As a first step after reading the results I'd like to invite the 30 persons who replied they're willing to contribute code to send an email to devel(a)ovirt.org introducing themselves: we'll be more than happy to welcome them and helping them getting started. I would also like to invite the 17 people who replied they'd like to help organizing oVirt events in their area to either get in touch with me or introduce themselves to users(a)ovirt.org so we can discuss about events organization. Last but not least I'd like to invite the 38 people willing to contribute documentation and the one willing to contribute localization to introduce themselves to devel(a)ovirt.org. Thanks! -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

6 5

Not being able to create new partition with fdisk
by pawel.zajac＠mikrosimage.com 01 Apr '19

01 Apr '19

Hi, I am not able to add new or extend a partitions under CentOS 7 VM in oVirt 4.2.7.5 - 1.el7 Once I get to write to partition table the system pauses with error. "VM XXXX has been paused due to unknown storage error." Can't see much in the log, messages doesn't even signaled it. The VM just pauses. VM storage is on a NFS share, so not a block device, like most of the issues I found. Did search web for similar issue, bit no luck so far. Any ideas? Thank you. Best, Pawel

1 0

Multiple Active VM before the preview" snapshots
by Bruckner, Simone 31 Mar '19

31 Mar '19

Hi, we see some VMs that show an inconsistent view of snapshots. Checking die database for one example vm shows the following result: engine=# select snapshot_id, status, description from snapshots where vm_id = '40c0f334-dac5-42ad-8040-e2d2193c73c0'; snapshot_id | status | description --------------------------------------+------------+------------------------------ b77f5752-f1a4-454f-bcde-6afd6897e047 | OK | Active VM 059d262a-6cc4-4d35-b1d4-62ef7fe28d67 | OK | Active VM before the preview d22e4f74-6521-45d5-8e09-332c05194ec3 | OK | Active VM before the preview 87d39245-bedf-4cf1-a2a6-4228176091d3 | IN_PREVIEW | base (4 rows) We cannot perform any snapshot, clone, copy operations on those vms. Is there a way to get this cleared? All the best, Simone

1 1

Is iSCSI performance better for VMs on the selected Host?
by sebastian.freitag＠aptiv.com 30 Mar '19

30 Mar '19

Hi all, I am planning to add block storage (iSCSI) to my oVirt environment. I just stumbled across this point from the oVirt Documentation: "6. Select an active host in the Use Host field. If this is not the first data domain in a data center, you must select the data center's SPM host. Important: All communication to the storage domain is through the selected host and not directly from the oVirt Engine." (you find it here: https://www.ovirt.org/documentation/admin-guide/chap-Storage.html#adding-bl…) So my question is: Is there a significant performance advantage for VMs using the storage that are running on that "selected host"? Because if this is the case, I would connect all my host machines to the dedicated storage network, create multiple data domains and "split" my iSCSI storage server(s) among those domains. If it is not the case, I would only have my storage server(s) and one of my hosts in the storage network. This also has implications on the dimensions (and cost!) of the switch that I use for the storage network, so I would be grateful if someone has any insight. Thanks

3 4

High iowait and low throughput on NFS, oflag=direct fixes it?
by Frank Wall 29 Mar '19

29 Mar '19

Hi, I've been using oVirt for years and have just discovered a rather strange issue that causes EXTREME high iowait when using a NFSv3 storage. Here's a quick test on a CentOS 7.6 VM running on any oVirt 4.2.x node: (5 oVirt nodes, all showing the same results) # CentOS VM $ dd if=/dev/zero of=TEST02 bs=1M count=3000 3000+0 records in 3000+0 records out 3145728000 bytes (3.1 GB) copied, 141.649 s, 22.2 MB/s # iostat output Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await r_await w_await svctm %util vdb 0.00 0.00 1.00 50.00 0.00 23.02 924.39 121.62 2243.47 2301.00 2242.32 19.61 100.00 As you can see iowait is beyond bad both for read and write requests. During this test the underlying NFS storage server was idle, disks barely doing anything. iowait on the NFS storage server was very low. However, when using oflag=direct the test shows a completely different result: # CentOS VM $ dd if=/dev/zero of=TEST02 bs=1M count=3000 oflag=direct 3000+0 records in 3000+0 records out 3145728000 bytes (3.1 GB) copied, 21.0724 s, 149 MB/s # iostat output Device: rrqm/s wrqm/s r/s w/s rMB/s wMB/s avgrq-sz avgqu-sz await r_await w_await svctm %util vdb 0.00 0.00 4.00 483.00 0.02 161.00 677.13 2.90 5.96 0.00 6.01 1.99 97.10 This test shows the *expected* performance in this small oVirt setup. Notice how iowait remains healthy, although the throughput is 7x higher now. I think this 2nd test may prove multiple things: the NFS storage is fast enough and there's no networking/switch issue either. Still, under normal conditions WRITE/READ operations are really slow and iowait goes through the roof. Do these results make sense to anyone? Any hints how to find what's wrong here? Any tests I should run or sysctls/tunables that would make sense? FWIW, iperf result looks good between the oVirt Node and the NFS storage: [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 10.9 GBytes 9.36 Gbits/sec Regards - Frank

1 1

Vagrant Plugin
by Jeremy Tourville 29 Mar '19

29 Mar '19

I am having some trouble getting the Ovirt Vagrant plugin working. I was able to get Vagrant installed and could even run the example scenario listed in the blog. https://www.ovirt.org/blog/2017/02/using-oVirt-vagrant.html My real issue is getting a vm generated by the SecGen project https://github.com/SecGen/SecGen to come up. If I use the VirtualBox provider everything works as expected and I can launch the vm with vagrant up. If I try to run using Ovirt provider it fails. I had originally posted this over in Google groups / Vagrant forums and it was suggested to take it to Ovirt. Hopefully, somebody here has some insights. The process fails quickly with the following output. Can anyone give some suggestions on how to fix the issue? I have also included a copy of my vagrantfile below. Thanks in advance for your assistance! ***Output*** Bringing machine 'escalation' up with 'ovirt4' provider... ==> escalation: Creating VM with the following settings... ==> escalation: -- Name: SecGen-default-scenario-escalation ==> escalation: -- Cluster: default ==> escalation: -- Template: debian_stretch_server_291118 ==> escalation: -- Console Type: spice ==> escalation: -- Memory: ==> escalation: ---- Memory: 512 MB ==> escalation: ---- Maximum: 512 MB ==> escalation: ---- Guaranteed: 512 MB ==> escalation: -- Cpu: ==> escalation: ---- Cores: 1 ==> escalation: ---- Sockets: 1 ==> escalation: ---- Threads: 1 ==> escalation: -- Cloud-Init: false ==> escalation: An error occured. Recovering.. ==> escalation: VM is not created. Please run `vagrant up` first. /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/service.rb:52:in `raise_error': Fault reason is "Operation Failed". Fault detail is "Entity not found: Cluster: name=default". HTTP response code is 404. (OvirtSDK4::Error) from /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/service.rb:67:in `check_fault' from /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/ovirt-engine-sdk-4.0.12/lib/ovirtsdk4/services.rb:35570:in `add' from /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/create_vm.rb:67:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/set_name_of_domain.rb:17:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:121:in `block in finalize_action' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/call.rb:53:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /home/secgenadmin/.vagrant.d/gems/2.4.4/gems/vagrant-ovirt4-1.2.2/lib/vagrant-ovirt4/action/connect_ovirt.rb:31:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/after_trigger.rb:26:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builtin/before_trigger.rb:23:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/warden.rb:50:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/builder.rb:116:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `block in run' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/util/busy.rb:19:in `busy' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/action/runner.rb:102:in `run' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:238:in `action_raw' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:209:in `block in action' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/environment.rb:615:in `lock' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:195:in `call' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/machine.rb:195:in `action' from /opt/vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run' Non-zero exit status... Not going to destroy escalation, since it does not exist Failed. Not retrying. Please refer to the error above. **Vagrantfile*** VAGRANTFILE_API_VERSION = "2" Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vm.define "escalation" do |escalation| escalation.vm.provider :ovirt4 do |ovirt| ovirt.username = 'admin@internal' ovirt.password = 'my_password' ovirt.url = 'https://engine.cyber-range.lan/ovirt-engine/api' ovirt.cluster = 'default' ovirt.template = 'debian_stretch_server_291118' ovirt.memory_size = '512 MB' ovirt.console = 'spice' ovirt.insecure = true ovirt.debug = true end escalation.vm.provision 'shell', inline: "echo 'datasource_list: [ None ] '> /etc/cloud/cloud.cfg.d/90_dpkg.cfg" escalation.vm.hostname = 'SecGen-default-scenario-escalation' escalation.vm.box = 'ovirt4' escalation.vm.box_url = 'https://github.com/myoung34/vagrant-ovirt4/blob/master/example_box/dummy.bo…' escalation.vm.provision "puppet" do | modules_utilities_unix_update_unix_update | modules_utilities_unix_update_unix_update.module_path = "puppet/escalation/modules" modules_utilities_unix_update_unix_update.environment_path = "environments/" modules_utilities_unix_update_unix_update.environment = "production" modules_utilities_unix_update_unix_update.synced_folder_type = "rsync" modules_utilities_unix_update_unix_update.manifests_path = "puppet/escalation/modules/unix_update" modules_utilities_unix_update_unix_update.manifest_file = "unix_update.pp" end escalation.vm.provision "puppet" do | modules_vulnerabilities_unix_misc_distcc_exec | modules_vulnerabilities_unix_misc_distcc_exec.facter = { "base64_inputs_file" => '94bad9a7b0c9aa1462eb1d4d8277a712', } modules_vulnerabilities_unix_misc_distcc_exec.module_path = "puppet/escalation/modules" modules_vulnerabilities_unix_misc_distcc_exec.environment_path = "environments/" modules_vulnerabilities_unix_misc_distcc_exec.environment = "production" modules_vulnerabilities_unix_misc_distcc_exec.synced_folder_type = "rsync" modules_vulnerabilities_unix_misc_distcc_exec.manifests_path = "puppet/escalation/modules/distcc_exec" modules_vulnerabilities_unix_misc_distcc_exec.manifest_file = "distcc_exec.pp" end escalation.vm.provision "puppet" do | modules_vulnerabilities_unix_local_chkrootkit | modules_vulnerabilities_unix_local_chkrootkit.facter = { "base64_inputs_file" => '170197cbf03410f71d7d777e9d468382', } modules_vulnerabilities_unix_local_chkrootkit.module_path = "puppet/escalation/modules" modules_vulnerabilities_unix_local_chkrootkit.environment_path = "environments/" modules_vulnerabilities_unix_local_chkrootkit.environment = "production" modules_vulnerabilities_unix_local_chkrootkit.synced_folder_type = "rsync" modules_vulnerabilities_unix_local_chkrootkit.manifests_path = "puppet/escalation/modules/chkrootkit" modules_vulnerabilities_unix_local_chkrootkit.manifest_file = "chkrootkit.pp" end escalation.vm.provision "puppet" do | modules_services_unix_nfs_nfs_share | modules_services_unix_nfs_nfs_share.facter = { "base64_inputs_file" => '98ddf2a16a97f46fd4856a509df9b75a', } modules_services_unix_nfs_nfs_share.module_path = "puppet/escalation/modules" modules_services_unix_nfs_nfs_share.environment_path = "environments/" modules_services_unix_nfs_nfs_share.environment = "production" modules_services_unix_nfs_nfs_share.synced_folder_type = "rsync" modules_services_unix_nfs_nfs_share.manifests_path = "puppet/escalation/modules/nfs_share" modules_services_unix_nfs_nfs_share.manifest_file = "nfs_share.pp" end escalation.vm.network :private_network, type: "dhcp", :ovirt__network_name => 'ovirtmgmt' end end

1 0

oVirt 4.2.8 - guest Windows 10 - oVirt tools - no mouse pointer
by Timmi 29 Mar '19

29 Mar '19

Hi guys, I have a problem with some of my Windows 10 VMs. There is no mouse pointer in case I'm connecting to the console through the virt-viewer. I have also other Windows 10 VMs which don't show the same issue. The mouse pointer is working as soon as I uninstall the oVirt tools. Any ideas? Best regards Timmi

1 0

ovirt "discard after delete" storage access request
by Simon Coter 29 Mar '19

29 Mar '19

Hi experts, how can I find a storage that supports “Discard” option for our oVirt storage domains ? I mean, I’ve tried more storage models and I always get: Discard is not supported by underlying storage. This is an example I’ve did on a very old storage (HP MSA): Thanks in advance for your help. Simon

2 1

cpu hotplug cannot be applied for windows 10
by zodaoko＠gmail.com 29 Mar '19

29 Mar '19

Hi there, I am running ovirt engine 4.2.8. I did cpu hotplug for windows 10 guest os, ovirt (from 1*2*1 to 2*2*1) successfully, and the output of virsh vcpuinfo also shows now there are total 4 vcpus: # virsh --readonly vcpuinfo 13 VCPU: 0 CPU: 51 State: running CPU time: 3911.8s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy VCPU: 1 CPU: 15 State: running CPU time: 907.7s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy VCPU: 2 CPU: 26 State: running CPU time: 1086.2s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy VCPU: 3 CPU: 2 State: running CPU time: 1085.7s CPU Affinity: yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy Issue: But when I log into windows 10, from the task manager, there are only two vcpus listed. Then I opened device manager, and found that there are 4 processors listed. refer to https://bugzilla.redhat.com/show_bug.cgi?id=1377155, I have updated os to the latest version 1809. refer to the ovirt doc, cpu hot plug is explicitly supported for windows 10 (both x86 and x86_64) , but from my testing result, the cpu hotplug was not applied. So is this a windows 10 bug? or is there any workaround? Thank you! Thanks, -Zhen

1 2

HE Install cannot login to VM
by Callum Smith 29 Mar '19

29 Mar '19

Dear all, Giving up on running ansible playbook remotely we're hitting earlier issues running hosted-engine --deploy 2019-03-28 15:42:33,975+0000 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 TASK [ovirt.hosted_engine_setup : Wait for the local VM] 2019-03-28 15:45:40,739+0000 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:103 {u'msg': u"timed out waiting for ping module test success: Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this. Please add this host's fingerprint to your known_hosts file to manage this host.", u'elapsed': 186, u'changed': False, u'_ansible_no_log': False, u'_ansible_delegated_vars': {u'ansible_delegated_host': u'he.virt.in.bmrc.ox.ac.uk', u'ansibl e_host': u'he.virt.in.bmrc.ox.ac.uk'}} 2019-03-28 15:45:40,840+0000 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:107 fatal: [localhost -> he.virt.in.bmrc.ox.ac.uk]: FAILED! => {"changed": false, "elapsed": 186, "msg": "timed out waiting for ping module test success: Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this. Please add this host's fingerprint to your known_hosts file to manage this host."} At a bit of a loss, especially since the old no-ansible install is not available anymore? Regards, Callum -- Callum Smith Research Computing Core Wellcome Trust Centre for Human Genetics University of Oxford e. callum(a)well.ox.ac.uk<mailto:callum@well.ox.ac.uk>

2 2