- Users - oVirt List Archives

Re: oVirt and CentOS Stream
by Strahil 27 Sep '19

27 Sep '19

Should I understand that the most tested platform will be CentOS Stream 8 ? Will Fedora & CentOS 8 still viable option ? Best Regards, Strahil NikolovOn Sep 26, 2019 16:13, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > > Progress cannot be made without change. As technologists, we recognize this every day. Most of the time, these changes are iterative: progressive additions of features to projects like oVirt. Sometimes those changes are small, and sometimes not. And that’s, of course, just talking about our project. But one of the biggest strengths of our community’s software is that we are not alone, and because of that, changes to other projects have ripple effects that can affect our own, even in positive ways. > > > This week, our collaborators in the CentOS Project have announced a change in the way their software is released moving forward. > > Beyond this week release of CentOS Linux 8, the CentOS team has announced CentOS Stream, a rolling release distribution that will be the "midstream" between Fedora and Red Hat Enterprise Linux. > > > To be clear, Fedora will remain as the first upstream of RHEL. But when RHEL branches off, CentOS will be upstream for ongoing work on those RHEL versions. This change gives public visibility into ongoing work on released RHEL, and a place for developers and community projects like ours to collaborate at that level. > > > CentOS has been heading in the direction of Stream for quite some time. CentOS SIGs — the special interest groups for virtualization, storage, config management, and so on — have given our project a way to provide input into the CentOS platform. Now, though, we can actually provide direct improvements or fixes to CentOS Stream platform that will be beneficial to our project. Long-term, those project-specific changes can find their way into the next release of RHEL, providing smoother transitions for those users of our downstream projects. > > > We expect the positive effects to extend beyond our own project’s ecosystem. Through CentOS Stream, developers will have early access to new features and content that are being built into the upcoming RHEL version. This will help to allow next-generation applications to have compatibility with future versions of RHEL. > > > The benefits of these changes are clear for ecosystem developers working on projects such as ours, writing hardware drivers, or extending protocols for RHEL. As we push the innovations that start in Fedora through the new CentOS Stream, the community will have a clear vision of the future of Red Hat Enterprise Linux. > > > For users of oVirt, we expect CentOS Stream to be the preferred upstream platform on which oVirt should be run, especially with the capability for our users to now contribute changes to our software and the community-built platform on which oVirt runs. > > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA > > sbonazzo(a)redhat.com > > Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

3 3

How to take incremental backup of a vm
by smidhunraj＠gmail.com 27 Sep '19

27 Sep '19

Can you tell me the method on how to take incremental backup of a VM in ovirt .Is there any opensource python script available to get this done.

3 2

NFS based - incremental backups
by Leo David 27 Sep '19

27 Sep '19

Hello Everyone, Ive been struggling since a while to find out a propper solution to have a full backup scenario for a production environment. In the past, we have used Proxmox, and the scheduled incremenral nfs based full vm backups is a thing that we really miss. As far as i know, at this point the only way to have a backup in oVirt / rhev is by using gluster geo-replication feature. This is nice, but as far as i know it lacks some important features: - ability to have incremental backups to restore vms from - ability to backup vms placed on different storage domains ( only one storage domain can be geo-replicated !!! some vms have disks on ssd volume, some on hdd, some on both) - need to setup an external 3 nodes gluster cluster ( although a workaround would be to have single bricks based volumes for a single instance ) I know we can create snaps, but they will die with the platform in a fail scenario, and neither they can be scheduled. We have found bacchus project that looked promising, although it had a pretty hassled way to achieve backups ( create snap, create vm from the snap, export vm to export domain, delete vm, delete snap - all in a scheduled fashion ) As a mention, Proxmox is incrementaly creating a tar archive of the vm disk content, and places it to an external network storage like nfs. This allowed us to backup/reatore both linux and windows vms very easily. Now, I know this have been discussed before, but i would like to know if there are at least any future plans to implement this feature in the next releases. Personally, i consider this a major, and quite decent feature to have with the platform, without the need to pay for 3rd party solutions that may or may not achieve the goal while adding extra pieces to the stack. Geo-replication is a good and nice feature, but in my oppinion it is not what a "backup domain" would be. Have a nice day, Leo

1 0

not able to import ova file
by Crazy Ayansh 27 Sep '19

27 Sep '19

Hi Team, I am getting below error message when i am trying to import a vm from ova method. [image: image.png] could anyone please help me out here. Hosted engine version:-4.2 Please let me know if any other info required from me. Thanks

1 1

4.2.7 to 4.3.5
by Demeter Tibor 27 Sep '19

27 Sep '19

Dear list members, I would like to upgrade my Centos 7.6 based ovirt 4.2 to 4.3.5. How is safe the upgrade ? How is stable the actual branch ? It seems to me, in 4.3.x there are a lot of cases caused by live migration, snapshot deletion, etc. Are these really existing problems? So, I'm a little bit afraid of the upgrade. It is a productive system, I don't want to make an outage. Thanks in advance, Regards, Tibor

2 1

oVirt and CentOS Stream
by Sandro Bonazzola 26 Sep '19

26 Sep '19

Progress cannot be made without change. As technologists, we recognize this every day. Most of the time, these changes are iterative: progressive additions of features to projects like oVirt. Sometimes those changes are small, and sometimes not. And that’s, of course, just talking about our project. But one of the biggest strengths of our community’s software is that we are not alone, and because of that, changes to other projects have ripple effects that can affect our own, even in positive ways. This week, our collaborators in the CentOS Project have announced a change <https://lists.centos.org/pipermail/centos-announce/2019-September/023449.ht…> in the way their software is released moving forward. Beyond this week release of CentOS Linux 8, the CentOS team has announced CentOS Stream, a rolling release distribution that will be the "midstream" between Fedora and Red Hat Enterprise Linux. To be clear, Fedora will remain as the first upstream of RHEL. But when RHEL branches off, CentOS will be upstream for ongoing work on those RHEL versions. This change gives public visibility into ongoing work on released RHEL, and a place for developers and community projects like ours to collaborate at that level. CentOS has been heading in the direction of Stream for quite some time. CentOS SIGs — the special interest groups for virtualization, storage, config management, and so on — have given our project a way to provide input into the CentOS platform. Now, though, we can actually provide direct improvements or fixes to CentOS Stream platform that will be beneficial to our project. Long-term, those project-specific changes can find their way into the next release of RHEL, providing smoother transitions for those users of our downstream projects. We expect the positive effects to extend beyond our own project’s ecosystem. Through CentOS Stream, developers will have early access to new features and content that are being built into the upcoming RHEL version. This will help to allow next-generation applications to have compatibility with future versions of RHEL. The benefits of these changes are clear for ecosystem developers working on projects such as ours, writing hardware drivers, or extending protocols for RHEL. As we push the innovations that start in Fedora through the new CentOS Stream, the community will have a clear vision of the future of Red Hat Enterprise Linux. For users of oVirt, we expect CentOS Stream to be the preferred upstream platform on which oVirt should be run, especially with the capability for our users to now contribute changes to our software and the community-built platform on which oVirt runs. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Re: Change hostname of physical hosts under an oVirt and Gluster combination
by Strahil 26 Sep '19

26 Sep '19

Unassigned in 99% of the cases means engine cannot communicate with vdsm.service on the host. Check that vdsm.service & glusterd.service are running. Check gluster volume status for each volume. If they are OK - from UI just select activate. Best Regards, Strahil NikolovOn Sep 25, 2019 22:24, TomK <tomkcpr(a)mdevsys.com> wrote: > > On 9/25/2019 8:49 AM, TomK wrote: > > On 9/24/2019 10:55 AM, Sahina Bose wrote: > >> > >> > >> On Tue, Sep 24, 2019 at 6:38 PM TomK <tomkcpr(a)mdevsys.com > >> <mailto:tomkcpr@mdevsys.com>> wrote: > >> > >> Hey Sahina, > >> > >> Thanks very much. > >> > >> I've taken a quick glance and it does mention I need a third host > >> which > >> I don't have. > >> > >> However, since I wrote, I removed everything. Had to force remove > >> hosts > >> however the gluster setup and data in it stayed (Or so I'm thinking). > >> > >> I'll read the article more thoroughly however is there a specific > >> procedure for adding existing oVirt gluster volumes back into a > >> cluster? > >> > >> One additional question. Is the sequence below correct? > >> > >> 1) Create Data Center > >> 2) Create Cluster within the DC > >> > >> > >> When you create the cluster - there's an Import cluster option, if I > >> remember correctly. This should discover the peers and volumes and add > >> it to the engine > > > > Trying that now. On a side note, the autodiscovery box is hard to edit. > > > > So in the meantime, trying to up the version to take advantage of some > > new features and ensure Gluster 6 is fully supported. Not having luck > > with the oVirt UI upgrade at the moment ( Not a self hosted engine. It's > > on a separate VM. ): > > > > --> Processing Conflict: > > ovirt-engine-setup-plugin-ovirt-engine-4.3.5.5-1.el7.noarch conflicts > > ovirt-engine < 4.2.6 > > --> Finished Dependency Resolution > > Error: Package: ovirt-engine-ui-extensions-1.0.6-1.el7.noarch (ovirt-4.3) > > Requires: ovirt-engine-webadmin-portal >= 4.3 > > Installed: > > ovirt-engine-webadmin-portal-4.2.1.7-1.el7.centos.noarch (@ovirt-4.2) > > ovirt-engine-webadmin-portal = 4.2.1.7-1.el7.centos > > Error: ovirt-engine-setup-plugin-ovirt-engine conflicts with > > ovirt-engine-4.2.1.7-1.el7.centos.noarch > > You could try using --skip-broken to work around the problem > > You could try running: rpm -Va --nofiles --nodigest > > > > > > > > Cheers, > > TK > > > > Just upgraded to 4.3.5. > > What do I do if I can't remove a host from a cluster? Maintenance > window options Active and Maintenance are grayed out. Host is currently > showing as Unassigned with an exclamation mark next to it. Items listed > include: > > "Power Management is not configured for this Host. Enable Power Management" > "Gluster status is disconnected for this host. Restart Glusterd service" > "Host has no default route." > > > I try to modify some of this thinking maybe it will nudge the server out > of it's slumber but get this when trying to fix Power Management: > > > "Error while executing action: > mdskvm-p01.nix.mds.xyz: > Cannot edit Host. Host parameters cannot be modified while Host is > operational. > Please switch Host to Maintenance mode first." > > > Of course I can't put it into maintenance since it's grayed out. > > Anyway to remove this host and start fresh? > > Cheers, > TK > > > >> > >> 3) Create a Domain within the Cluster > >> 4) Add hosts to DC > >> 5) Import Gluster Volume > >> > >> > >> 4 & 5 not required if you change step 2 to import. > >> You are running into errors below because the engine sees the addition > >> of new hosts as gluster peer probing to a new cluster > >> > >> > >> > >> Some issues. I create a DC, add a Cluster then add the Host to it. > >> Then > >> I try to add another the second node but it says It's already in a > >> cluster. There is no other cluster and the second host is not listed > >> anywhere. > >> > >> So I try to remove the first host to res

2 1

Outage Notification: Jenkins and Resources Are Not Accessible
by Anton Marchukov 26 Sep '19

26 Sep '19

Hello All. Please note that oVirt services hosted at PHX datacenter are not accessible. Main services running there are: jenkins.ovirt.org resources.ovirt.org This looks to be network related and we are working with the relevant teams to resolve it. Anton. -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat

1 1

Re: ovirtmgmt STP disabled - any reason behind that
by Strahil 26 Sep '19

26 Sep '19

Did I miss someone's reply on this one ? Best Regards, Strahil NikolovOn Sep 24, 2019 00:46, Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: > > Hi All, > > I recently got an issue and due to lack of debug time , I'm still not sure if it was a loop on the network. > Can someone clarify why the ovirtmgmt bridge has STP disabled ? Any reason behind that ? > > Also, what is the proper way to enable STP on those bridges ? > > For now , I have set highest priority of the STP on my router and I don't expect the issue to reoccur (if it really was a loop), but I want to avoid future issues like that. > > > Best Regards, > Strahil Nikolov

1 0

Re: Urgent help needed / Snapshot deletion failure
by Strahil 26 Sep '19

26 Sep '19

Is it really down ? Have you tried to migrate it to another host. I found out yesterday that one of my VMs was constantly reporting errors (relayed to snapshot delete) and the errors stopped when the system got migrated to another host. Best Regards, Strahil NikolovOn Sep 25, 2019 15:27, smirta(a)gmx.net wrote: > > Dear all we are desperate > > We have tried to delete a Snapshot and it hangs at merging the snapshots. We've found out that this is a known bug because the merge process is being called with wrong parameters according to the bug report https://bugzilla.redhat.com/show_bug.cgi?id=1601212. The Snapshot's Disks are in illegal state and the VM is locked. Since it is a very important VM for our non-profit organization, we need to have this machine back online as soon as possible. Is there a way to fix this without updating to qemu-kvm-ev-2.12.0? At least back to the state before the deletion would be fantastic. > > Our vdsm.log: > 2019-09-25 14:01:41,283+0200 WARN (vdsm.Scheduler) [Executor] Worker blocked: <Worker name=jsonrpc/0 running <Task <JsonRpcTask {'params': {u'topVolUUID': u'8a9f190f-2725-4535-a69d-c74e4e57d372', u'vmID': u'1422899a-2151-4d5d-9d66-e74f19084542', u'drive': {u'imageID': u'eb2bce92-e758-4bea-93fa-02a56574b932', u'volumeID': u'8a9f190f-2725-4535-a69d-c74e4e57d372', u'domainID': u'022f39ee-eeb8-4b51-9549-9d7e3c88d4a8', u'poolID': u'00000001-0001-0001-0001-000000000307'}, u'bandwidth': u'0', u'jobUUID': u'c3fdc4a9-9d6d-424a-b9df-b96be5622e0a', u'baseVolUUID': u'3e15121b-0795-4056-bafe-448068c9ec71'}, 'jsonrpc': '2.0', 'method': u'VM.merge', 'id': u'9cd540b7-a32f-4f95-9fe2-9ce70d5b6478'} at 0x7f674fec5710> timeout=60, duration=6420 at 0x7f674fec58d0> task#=1896299 at 0x7f674c06ae90>, traceback: > File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap > self.__bootstrap_inner() > File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner > self.run() > File: "/usr/lib64/python2.7/threading.py", line 765, in run > self.__target(*self.__args, **self.__kwargs) > File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 194, in run > ret = func(*args, **kwargs) > File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run > self._execute_task() > File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task > task() > File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__ > self._callable() > File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 523, in __call__ > self._handler(self._ctx, self._req) > File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 566, in _serveRequest > response = self._handle_request(req, ctx) > File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 606, in _handle_request > res = method(**params) > File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 197, in _dynamicMethod > result = fn(*methodArgs) > File: "<string>", line 2, in merge > File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method > ret = func(*args, **kwargs) > File: "<string>", line 2, in merge > File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 122, in method > ret = func(*args, **kwargs) > File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 739, in merge > drive, baseVolUUID, topVolUUID, bandwidth, jobUUID) > File: "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 6041, in merge > self.updateVmJobs() > File: "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5818, in updateVmJobs > self._vmJobs = self.queryBlockJobs() > File: "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5832, in queryBlockJobs > with self._jobsLock: > File: "/usr/lib/python2.7/site-packages/pthreading.py", line 60, in __enter__ > self.acquire() > File: "/usr/lib/python2.7/site-packages/pthreading.py", line 68, in acquire > rc = self.lock() if blocking else self.trylock() > File: "/usr/lib/python2.7/site-packages/pthread.py", line 96, in lock > return _libpthread.pthread_mutex_lock(self._mutex) (executor:363) > > > Kind regards > Simon > _______________________________________________ > 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/LW7BNZBO5AAGN…

1 0

Change hostname of physical hosts under an oVirt and Gluster combination
by TomK 26 Sep '19

26 Sep '19

Hey All, Would like to change the hostname of hosts within a gluster volume that's been added to oVirt. I also need to readd the bricks to the gluster volume under the new hostname. What's the recommended approach to do so when all this is added to oVirt? -- Thx, TK.

2 7

Managed Block Storage: ceph detach_volume failing after migration
by Dan Poltawski 25 Sep '19

25 Sep '19

On ovirt 4.3.5 we are seeing various problems related to the rbd device staying mapped after a guest has been live migrated. This causes problems migrating the guest back, as well as rebooting the guest when it starts back up on the original host. The error returned is ‘nrbd: unmap failed: (16) Device or resource busy’. I’ve pasted the full vdsm log below. As far as I can tell this isn’t happening 100% of the time, and seems to be more prevalent on busy guests. (Not sure if I should create a bug for this, so thought I’d start here first) Thanks, Dan Sep 24 19:26:18 mario vdsm[5485]: ERROR FINISH detach_volume error=Managed Volume Helper failed.: ('Error executing helper: Command [\'/usr/libexec/vdsm/managedvolume-helper\', \'detach\'] 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/tmptQzb10/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 76076\\nTraceback (most recent call last):\\n File "/usr/libexec/vdsm/managedvolume-helper", 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 149, in detach\\n ignore_errors=False)\\n File "/usr/lib/python2.7/site-packages/vdsm/storage/nos_brick.py", line 121, in disconnect_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 241, in _wrap\\n return self.channel.remote_call(name, args, kwargs)\\n File "/usr/lib/python2.7/site-packages/oslo_privsep/daemon.py", line 203, in remote_call\\n raise exc_type(*result[2])\\noslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command.\\nCommand: rbd unmap /dev/rbd/rbd/volume-0e8c1056-45d6-4740-934d-eb07a9f73160 --conf /tmp/brickrbd_LCKezP --id ovirt --mon_host 172.16.10.13:3300 --mon_host 172.16.10.14:3300 --mon_host 172.16.10.12:6789\\nExit code: 16\\nStdout: u\\\'\\\'\\nStderr: u\\\'rbd: sysfs write failed\\\\nrbd: unmap failed: (16) Device or resource busy\\\\n\\\'\\n\'',)#012Traceback (most recent call last):#012 File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 124, in method#012 ret = func(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1766, in detach_volume#012 return managedvolume.detach_volume(vol_id)#012 File "/usr/lib/python2.7/site-packages/vdsm/storage/managedvolume.py", line 67, in wrapper#012 return func(*args, **kwargs)#012 File "/usr/lib/python2.7/site-packages/vdsm/storage/managedvolume.py", line 135, in detach_volume#012 run_helper("detach", vol_info)#012 File "/usr/lib/python2.7/site-packages/vdsm/storage/managedvolume.py", line 179, in run_helper#012 sub_cmd, cmd_input=cmd_input)#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__#012 return callMethod()#012 File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda>#012 **kwargs)#012 File "<string>", line 2, in managedvolume_run_helper#012 File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod#012 raise convert_to_error(kind, result)#012ManagedVolumeHelperFailed: Managed Volume Helper failed.: ('Error executing helper: Command [\'/usr/libexec/vdsm/managedvolume-helper\', \'detach\'] 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/tmptQzb10/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 76076\\nTraceback (most recent call last):\\n File "/usr/libexec/vdsm/managedvolume-helper", 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 149, in detach\\n ignore_errors=False)\\n File "/usr/lib/python2.7/site-packages/vdsm/storage/nos_brick.py", line 121, in disconnect_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 241, in _wrap\\n return self.channel.remote_call(name, args, kwargs)\\n File "/usr/lib/python2.7/site-packages/oslo_privsep/daemon.py", line 203, in remote_call\\n raise exc_type(*result[2])\\noslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command.\\nCommand: rbd unmap /dev/rbd/rbd/volume-0e8c1056-45d6-4740-934d-eb07a9f73160 --conf /tmp/brickrbd_LCKezP --id ovirt --mon_host 172.16.10.13:3300 --mon_host 172.16.10.14:3300 --mon_host 172.16.10.12:6789\\nExit code: 16\\nStdout: u\\\'\\\'\\nStderr: u\\\'rbd: sysfs write failed\\\\nrbd: unmap failed: (16) Device or resource busy\\\\n\\\'\\n\'',) ________________________________ The Networking People (TNP) Limited. Registered office: Network House, Caton Rd, Lancaster, LA1 3PE. Registered in England & Wales with company number: 07667393 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

4 4

Urgent help needed / Snapshot deletion failure
by smirta＠gmx.net 25 Sep '19

25 Sep '19

Dear all we are desperate We have tried to delete a Snapshot and it hangs at merging the snapshots. We've found out that this is a known bug because the merge process is being called with wrong parameters according to the bug report https://bugzilla.redhat.com/show_bug.cgi?id=1601212. The Snapshot's Disks are in illegal state and the VM is locked. Since it is a very important VM for our non-profit organization, we need to have this machine back online as soon as possible. Is there a way to fix this without updating to qemu-kvm-ev-2.12.0? At least back to the state before the deletion would be fantastic. Our vdsm.log: 2019-09-25 14:01:41,283+0200 WARN (vdsm.Scheduler) [Executor] Worker blocked: <Worker name=jsonrpc/0 running <Task <JsonRpcTask {'params': {u'topVolUUID': u'8a9f190f-2725-4535-a69d-c74e4e57d372', u'vmID': u'1422899a-2151-4d5d-9d66-e74f19084542', u'drive': {u'imageID': u'eb2bce92-e758-4bea-93fa-02a56574b932', u'volumeID': u'8a9f190f-2725-4535-a69d-c74e4e57d372', u'domainID': u'022f39ee-eeb8-4b51-9549-9d7e3c88d4a8', u'poolID': u'00000001-0001-0001-0001-000000000307'}, u'bandwidth': u'0', u'jobUUID': u'c3fdc4a9-9d6d-424a-b9df-b96be5622e0a', u'baseVolUUID': u'3e15121b-0795-4056-bafe-448068c9ec71'}, 'jsonrpc': '2.0', 'method': u'VM.merge', 'id': u'9cd540b7-a32f-4f95-9fe2-9ce70d5b6478'} at 0x7f674fec5710> timeout=60, duration=6420 at 0x7f674fec58d0> task#=1896299 at 0x7f674c06ae90>, traceback: File: "/usr/lib64/python2.7/threading.py", line 785, in __bootstrap self.__bootstrap_inner() File: "/usr/lib64/python2.7/threading.py", line 812, in __bootstrap_inner self.run() File: "/usr/lib64/python2.7/threading.py", line 765, in run self.__target(*self.__args, **self.__kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/common/concurrent.py", line 194, in run ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 301, in _run self._execute_task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 315, in _execute_task task() File: "/usr/lib/python2.7/site-packages/vdsm/executor.py", line 391, in __call__ self._callable() File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 523, in __call__ self._handler(self._ctx, self._req) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 566, in _serveRequest response = self._handle_request(req, ctx) File: "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 606, in _handle_request res = method(**params) File: "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 197, in _dynamicMethod result = fn(*methodArgs) File: "<string>", line 2, in merge File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File: "<string>", line 2, in merge File: "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 122, in method ret = func(*args, **kwargs) File: "/usr/lib/python2.7/site-packages/vdsm/API.py", line 739, in merge drive, baseVolUUID, topVolUUID, bandwidth, jobUUID) File: "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 6041, in merge self.updateVmJobs() File: "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5818, in updateVmJobs self._vmJobs = self.queryBlockJobs() File: "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 5832, in queryBlockJobs with self._jobsLock: File: "/usr/lib/python2.7/site-packages/pthreading.py", line 60, in __enter__ self.acquire() File: "/usr/lib/python2.7/site-packages/pthreading.py", line 68, in acquire rc = self.lock() if blocking else self.trylock() File: "/usr/lib/python2.7/site-packages/pthread.py", line 96, in lock return _libpthread.pthread_mutex_lock(self._mutex) (executor:363) Kind regards Simon

1 1

How to delete obsolete Data Centers with no hosts, but with domains inside
by Claudio Soprano 25 Sep '19

25 Sep '19

Hi to all, We are using ovirt to manage 6 Data Centers, 3 of them are old Data Centers with no hosts inside, but with domains, storage and VMs not running. We left them because we wanted to have some backups in case of failure of the new Data Centers created. Time pass and now we would like to remove these Data Centers, but we got no way for now to remove them. If we try to remove the Storage Domains (using remove o destroy) we get "Error while executing action: Cannot destroy the master Storage Domain from the Data Center without another active Storage Domain to take its place. -Either activate another Storage Domain in the Data Center, or remove the Data Center. -If you have problems with the master Data Domain, consider following the recovery process described in the documentation, or contact your system administrator." if we try to remove the Data Center directly we get "Error while executing action: Cannot remove Data Center. There is no active Host in the Data Center." How can we solve the problem ? It can be done via ovirt-shell or using some script or via ovirt management interface ? Thanks in advance Claudio

2 6

Add External Provider - OpenStack Glance - Test Failed - "Failed to communicate with the External Provider"
by Pravin Mohandass 25 Sep '19

25 Sep '19

We have installed Ovirt Manager 4.3 with couple of KVM compute host added into cluster. When we add OpenStack Glance as an External Provider, failing with following error message - "Failed to communicate with the External Provider" We are able to add the external provider for Openstack Neutron and Openstack Cinder and import the storage and network in to ovirt manager and use it for vm. We are getting following error message on engine.log file "Failed with error PROVIDER_FAILURE and code 5050". But we are able to fetch the images using postman tool. Requesting you to provide some insights on adding the Glance provider.

1 0

[ANN] oVirt 4.3.6 Sixth Release Candidate is now available for testing
by Sandro Bonazzola 25 Sep '19

25 Sep '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.6 Sixth Release Candidate for testing, as of September 25th, 2019. This update is a release candidate of the sixth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.7 or later (but <8) * CentOS Linux (or similar) 7.7 or later (but <8) * oVirt Node 4.3 (available for x86_64 only) has been built consuming CentOS 7.7 Release See the release notes [1] for known issues, new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available Additional Resources: * Read more about the oVirt 4.3.6 release highlights: http://www.ovirt.org/release/4.3.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.3.6/ [2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Messed up 4.2.3.1 installation - SSL handshake ERROR
by souvaliotimaria＠mail.com 25 Sep '19

25 Sep '19

Hello, everyone! So, I have an experimental installation of ovirt 4.2.3.1 with 3 nodes and glustered. Recently I deployed a new installation with ovirt 4.3.5.2, 3nodes and glustered storage here as well. The thing is, in my enthousiasm I thought "hey! what if I can import the experimental nodes as hosts in the new installation in a new cluster and see what happens? Will the 4.3.5.2 engine see them? Probably yeah. But will it see the VMs I have there?" And so I imported the experimental nodes. Without detaching them from their hosted engine. I could see the only VM that was active at the moment and not one of the suspended ones and of course I could not see the 4.2.3.1 HE VM. I have removed the hosts from the new installation and I have tried reconnecting the old engine and its nodes. Passwordless ssh works just fine, but the problem persists. hosted-engine --vm-status reports stale-data on node 2 and node 3 The thing is I know I messed the experimental installation (and I blame only my curiosity), SSL handshake is no longer feasable and I can't remove the hosts from the initial Cluster to Import them again. Basically everything is either in the process of activating without ever being able to do so or down or Non responsive. I would like to find a way around this, as I have seen in other posts in the ovirt forum that the SSL handshake error appears in some other cases and I would like to have a know-how if an occasion like this occurs in the future in production. Is it possible to re-deploy the engine on the nodes and not lose the glustered space or the existing VMs? Can the HE be destroyed and then deployed from scratch? What about the glustered space and the VMs' space? Will the VMs just take up space without being able to neither bring them up nor destroy them? I know I'm asking a lot and it was my fault to begin with but I am really curious if we can see this through. Thanks in advance

1 0

oVirt node - post-upgrade tasks
by dan.munteanu＠mdc-berlin.de 25 Sep '19

25 Sep '19

Dear oVirt community, recently I've started to use oVirt as a replacement for KVM + VirtManager and I've decided to use the oVirt Node installed on Dell EMC servers with self-hosted engine. So far, everything works fine, except that, each time I'm updating the nodes, I must reinstall Dell OMSA needed by the monitoring system (via SNMP). Is there any way to automatize the OMSA installation as a post-upgrade task/hook? Thank you Dan

1 0

Got a RequestError: status: 409 reason: Conflict
by smidhunraj＠gmail.com 25 Sep '19

25 Sep '19

I'm trying to clone the snapshot into a new vm. The tool I am using is ovirtBAckup from the github wefixit-AT The link is here https://github.com/wefixit-AT/oVirtBackup this piece of code snippet throws me error. if not config.get_dry_run(): api.vms.add(params.VM(name=vm_clone_name, memory=vm.get_memory(), cluster=api.clusters.get(config.get_cluster_name()), snapshots=snapshots_param)) VMTools.wait_for_vm_operation(api, config, "Cloning", vm_from_list) print 'hellooooo' logger.info("Cloning finished") The above lines are from the 325 line number of backup.py of the github. I am getting error as !!! Got a RequestError: status: 409 reason: Conflict detail: Cannot add VM. The VM is performing an operation on a Snapshot. Please wait for the operation to finish, and try again. How can i further debug the code to know what is happening wrong in my program.I am new to python please help me.

2 1

Super Low VM disk IO via Shared Storage
by Vrgotic, Marko 24 Sep '19

24 Sep '19

Dear oVirt, I have executed some tests regarding IO disk speed on the VMs, running on shared storage and local storage in oVirt. Results of the tests on local storage domains: avlocal2: [root@mpollocalcheck22 ~]# dd if=/dev/zero of=/tmp/test2.img bs=512 count=100000 oflag=dsync 100000+0 records in 100000+0 records out 51200000 bytes (51 MB) copied, 45.9756 s, 1.1 MB/s avlocal3: [root@mpollocalcheck3 ~]# dd if=/dev/zero of=/tmp/test2.img bs=512 count=100000 oflag=dsync 100000+0 records in 100000+0 records out 51200000 bytes (51 MB) copied, 43.6179 s, 1.2 MB/s Results of the test on shared storage domain: avshared: [root@mpoludctest4udc-1 ~]# dd if=/dev/zero of=/tmp/test2.img bs=512 count=100000 oflag=dsync 100000+0 records in 100000+0 records out 51200000 bytes (51 MB) copied, 283.499 s, 181 kB/s Why is it so low? Is there anything I can do to tune, configure VDSM or other service to speed this up? Any advice is appreciated. Shared storage is based on Netapp with 20Gbps LACP path from Hypervisor to Netapp volume, and set to MTU 9000. Used protocol is NFS4.0. oVirt is 4.3.4.3 SHE.

2 1

neofetch and spice/vnc console
by Nathanaël Blanchet 24 Sep '19

24 Sep '19

Hello When running neofetch in spice/vnc console, terminal become unreadable, does it come from spice/vnc or graphic emulation or neofetch binary? Screenfetch alternative is ok. -- Nathanaël Blanchet Supervision réseau Pôle Infrastrutures Informatiques 227 avenue Professeur-Jean-Louis-Viala 34193 MONTPELLIER CEDEX 5 Tél. 33 (0)4 67 54 84 55 Fax 33 (0)4 67 54 84 14 blanchet(a)abes.fr

1 0

Internal Memory filter not satisfied question
by Vrgotic, Marko 24 Sep '19

24 Sep '19

Dear oVirt, I need help clarifying how internal memory filter is used, at which values it looks at. The log message below is clear, but I am failing to see from where are the memory values calculated, is it based on Guarenteed, Allocated or MaxAvailable memory a VM can get/have? Or something else. We have a shared cluster, with hosts having different memory amount: Tried to create 17VMs, and following errors were observed: 2019-09-20 11:46:10,496Z WARN [org.ovirt.engine.core.bll.RunVmCommand] (EE-ManagedThreadFactory-engine-Thread-967) [2d316914-84dc-4410-856f-f8576e411574] Validation of action 'RunVm' failed for user mvrgotic@ictv.com@ictv.com-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-08.avinity.tv,$filterName Memory,$availableMem 3513,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-02.avinity.tv,$filterName Memory,$availableMem 1605,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-05.avinity.tv,$filterName Memory,$availableMem 1265,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-20.avinity.tv,$filterName Memory,$availableMem 195,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-01.avinity.tv,$filterName Memory,$availableMem 177,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-06.avinity.tv,$filterName Memory,$availableMem 2845,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-09.avinity.tv,$filterName Memory,$availableMem 480,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-03.avinity.tv,$filterName Memory,$availableMem 3116,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-hv-21.avinity.tv,$filterName Memory,$availableMem 1342,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL 2019-09-20 11:46:10,577Z INFO [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (EE-ManagedThreadFactory-engine-Thread-851) [2d316914-84dc-4410-856f-f8576e411574] Candidate host 'ovirt-hv-08.avinity.tv' ('adebaa4f-5402-47c7-8634-5779a4b3f10f') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null) To provide you with bit more detail on our Cluster setup: oVirt SHE 4.3.4.3-1 Cluster Settings and Hosts actual memory usage [A screenshot of a cell phone Description automatically generated][A screenshot of a cell phone Description automatically generated][A screenshot of a cell phone Description automatically generated] And here is the VM information” Name: testvmmvr-th11stitcher Defined Memory: 4096 MB Origin: oVirt Description: Physical Memory Guaranteed: 1024 MB Run On: Any Host in Cluster Template: av-centos-75-baseimage (Thin/Dependent) Guest OS Memory Free/Cached/Buffered: 3453 / 2 / 156 MB Custom Properties: Not Configured Operating System: Red Hat Enterprise Linux 7.x x64 Number of CPU Cores: 4 (1:4:1) Cluster Compatibility Version: 4.3 BIOS Type: Default Guest CPU Count: 4 VM ID: testvmmvr Graphics protocol: VNC Guest CPU Type: SandyBridge,+pcid,+spec-ctrl,+ssbd Video Type: QXL Highly Available: No Priority: Low Number of Monitors: 1 FQDN: testvmmvr-th11stitcher Optimized for: Server USB Policy: Disabled Hardware Clock Time Offset: Etc/GMT Created By: Deployment User Kindly awaiting your reply. If any data is missing, please let me know. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic

1 0

Re: One of the brick in the GFS is down ,How can I slove it?
by Amit Bawer 24 Sep '19

24 Sep '19

On Tuesday, September 24, 2019, zhouhao(a)vip.friendtimes.net < zhouhao(a)vip.friendtimes.net> wrote: > sorry ，execute “gluster peer status” lost a brick，I worry about losing > data > > ------------------------------ > zhouhao(a)vip.friendtimes.net > > > *From:* Amit Bawer <abawer(a)redhat.com> > *Date:* 2019-09-24 15:42 > *To:* zhouhao(a)vip.friendtimes.net > *CC:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Re: One of the brick in the GFS is down ,How > can I slove it? > it is preferable to have all GFS nodes online and running first, you can > follow troubleshooting here: > > https://www.ovirt.org/documentation/gluster-hyperconverged/chap- > Troubleshooting.html > > > On Tue, Sep 24, 2019 at 7:18 AM zhouhao(a)vip.friendtimes.net < > zhouhao(a)vip.friendtimes.net> wrote: > >> >> >> ------------------------------ >> zhouhao(a)vip.friendtimes.net >> >> >> *From:* zhouhao(a)vip.friendtimes.net >> *Date:* 2019-09-24 11:41 >> *To:* zhouhao <zhouhao(a)vip.friendtimes.net>; users <users(a)ovirt.org> >> *Subject:* Re: [ovirt-users] One of the brick in the GFS is down ,How >> can I slove it? >> Can I click The 'start' button?? >> >> >> ------------------------------ >> zhouhao(a)vip.friendtimes.net >> >> >> *From:* zhouhao(a)vip.friendtimes.net >> *Date:* 2019-09-24 11:36 >> *To:* users <users(a)ovirt.org> >> *Subject:* [ovirt-users] One of the brick in the GFS is down ,How can I >> slove it? >> >> *How can I slove it safely? There are 50 vms running in this GFS* >> >> >> *the mail messages below:* >> >> *Time:* 2019-09-24 04:47:20.511 >> *Message:* Detected change in status of brick 192.168.3.16:/vmdata/gfs >> of volume bojoy-GFS of cluster bojoy-cluster from UP to DOWN via cli. >> *Severity:* WARNING >> >> status below: >> >> >> GFS service status >> >> _______________________________________________ >> 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/TBCAJIHSV2AU24IFAMR43GIHRUECWW2V/ >> >

4 3

Unexpected SSO error with first task
by Vrgotic, Marko 24 Sep '19

24 Sep '19

Dear oVirt, In our software tests, we deploy oVirt VMs using ansible and teardown also using ansible. We noticed that each time we run nightly tests, using Jenkins user in ovirt, in one of the Jobs, first task, creating VM, fails with following error, TASK [Login to oVirt] ********************************************************** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AuthError: Error during SSO authentication invalid_grant : The provided authorization grant for the username and password has expired. fatal: [PVyrZMy0-csm-2.avinity.tv<http://pvyrzmy0-csm-2.avinity.tv/> -> localhost]: FAILED! => {"changed": false, "msg": "Error during SSO authentication invalid_grant : The provided authorization grant for the username and password has expired."} Immediately after, Token seem to be renewed and all other VMs are created without issue. The play looks like following: --- # file: provision-ovirt.yml - name: Create VM in OVirt hosts: ovirt-vms gather_facts: false vars: - state: running pre_tasks: - name: Login to oVirt delegate_to: localhost ovirt_auth: url: "{{ ovirt_engine_url }}" username: "{{ ovirt_engine_user }}" password: "{{ ovirt_engine_password }}" ca_file: "{{ ovirt_engine_cafile | default(omit) }}" insecure: "{{ ovirt_engine_insecure | default(true) }}" run_once: true tasks: - name: "Get agent keys" delegate_to: localhost command: ssh-add -L register: ssh_agent_pubkeys run_once: true changed_when: False - name: Create new VMs from template delegate_to: localhost ovirt_vm: auth: "{{ ovirt_auth }}" name: "{{ inventory_hostname_short }}" nics: - name: nic1 profile_name: tenant1 interface: virtio cloud_init_nics: - nic_name: eth0 nic_boot_protocol: dhcp nic_on_boot: true cloud_init: host_name: "{{ inventory_hostname_short }}" authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}" state: "{{ state }}" cluster: "{{ovirt_cluster}}" template: "{{ images_to_template[os_image] }}" instance_type: "{{ os_flavor_to_ovirt_instance_type[os_flavor] }}" - name: "Wait until the ansible user can log into the host (cloud-init needs to have finished)" command: ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no {{ansible_user}}@{{inventory_hostname}} exit register: ssh_output delegate_to: localhost until: ssh_output.rc == 0 retries: 30 delay: 5 changed_when: False post_tasks: - name: Logout from oVirt delegate_to: localhost run_once: true ovirt_auth: state: absent ovirt_auth: "{{ ovirt_auth }}" tags: - always How does token relates to user session in oVirt? We would expect that once we logout, token should be expired and upon new login just get renewed/new token to proceed. Is it a bug? Is it in the play that we are doing something incorrectly? Kindly awaiting your eply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic

1 0

the virtual machine crushed and I cant shutdown the vm successfully
by zhouhao＠vip.friendtimes.net 24 Sep '19

24 Sep '19

The trouble bothered me for a long time;Some times my vm will crush and I cant shutdown it,I had to reboot the ovirt-node to slove it; the vm's error below The ovirt-node's error below The vm's threading on the ovirt-node, the IO ratio is 100% and the vm's process change to defunct I can not kill it,every time I had to shutdown the ovirt-node on the engine website ,the vm's status always in the way to shutdown ,even if I wait for it for hours; It either failed or is shutting down and the "power off" cant shutdown the vm too. ---------------------------------------------------------------- The other infomation about my ovirt-node node-version： node hardware zhouhao(a)vip.friendtimes.net

4 7