- Users - oVirt List Archives

Adding posix compliant FS
by carl langlois 16 Mar '17

16 Mar '17

Hi Guys, I am trying to add a posix FS on one of my host. Ovirt in actually mounting it but fail with "Error while executing action Add Storage Connection: General Exception" If i look in the vdsm.log i cant see sonrpc.Executor/7::DEBUG::2017-03-16 12:39:28,248::fileUtils::209::Storage.fileUtils::(createdir) Creating directory: /rhev/data-center/mnt/_dev_dm-3 mode: None jsonrpc.Executor/7::DEBUG::2017-03-16 12:39:28,248::fileUtils::218::Storage.fileUtils::(createdir) Using existing directory: /rhev/data-center/mnt/_dev_dm-3 jsonrpc.Executor/7::INFO::2017-03-16 12:39:28,248::mount::226::storage.Mount::(mount) mounting /dev/dm-3 at /rhev/data-center/mnt/_dev_dm-3 jsonrpc.Executor/7::DEBUG::2017-03-16 12:39:28,270::utils::871::storage.Mount::(stopwatch) /rhev/data-center/mnt/_dev_dm-3 mounted: 0.02 seconds jsonrpc.Executor/7::ERROR::2017-03-16 12:39:28,271::hsm::2403::Storage.HSM::(connectStorageServer) Could not connect to storageServer Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2400, in connectStorageServer conObj.connect() File "/usr/share/vdsm/storage/storageServer.py", line 242, in connect self.getMountObj().getRecord().fs_file) File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 260, in getRecord (self.fs_spec, self.fs_file)) OSError: [Errno 2] Mount of `/dev/dm-3` at `/rhev/data-center/mnt/_dev_dm-3` does not exist any help would be appreciated. Thanks CL

2 1

Re: [ovirt-users] Serious Trouble - Lost Domains
by JC Clark 16 Mar '17

16 Mar '17

This is a multi-part message in MIME format. --------------D32B351E0E3629426DD972AA Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Thank you for your response. My storage is NFS storage. I will try with "qemu-img info" .. I made an attempt to import the domain and I got an error. I will attempt to replicate tonight. Do I have to alter any of the metafiles when importing? I seemed to remember it didn't like to import another data center's domain. Sincerely JC Date: Tue, 14 Mar 2017 10:16:17 +0100 From: Arman Khalatyan<arm2arm(a)gmail.com> To: JC Clark<jc(a)saipantech.com> Cc: users<users(a)ovirt.org> Subject: Re: [ovirt-users] Serious Trouble - Lost Domains Message-ID: <CAAqDm6ap1YDV4ThRa+Z4H-2k3o9VQ8qp4PAWQ7VShYmEeGXSyQ(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" What kind of storage are you using? If you check images with "qemu-img info" are you able to see the filesystems? Can you simply import the domain unto the new ovirt? Am 14.03.2017 9:59 vorm. schrieb "JC Clark"<jc(a)saipantech.com>: > Dear Fellows and Fellettes, > > I am having serious disaster problems. After a power transformer outside > the building literally exploded, surged and fried the motherboard to the > main SPM domain computer in my Ovirt 4.0 system. After getting the computer > working again with a new mother board. I managed to basically loose > integrity of the old engine. I have rebuilt the engine. > > I have backups of the old engine and 4 data domains an ISO domain and an > export domain which appear to not be damaged. They are all accessible from > the CL. > I had to create a new host and SPM. How do I get the floating domains > into the new Engine? > > I have 1 storage container (85GB) I must get back. MUST GET BACK!! > > I really appreciate you reading my sob story. Hope you can help.. > > Thank You much > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users >

2 2

virtio-scsi drive order?
by gflwqs gflwqs 16 Mar '17

16 Mar '17

Hi list! When we upgraded our ovirt environment to 4.1 we get the virtio-scsi interface as default for virtual disks. We have seen a difference in drive order from when we used the virtio interface. Before when we added disks the order of the drives were set by which order the disks was created. So if i had 1 disk as os disk it became vda and added a 50 GB disk that disk became vdb and then added another 8GB disk that became vdc. But now when i add two additional disks with the virtio-scsi interface like the above when i reboot the vm the 50GB disk become sdc and the 8GB disk become sdb even that i created the 50GB disk first? How is the order decided in the virtio-scsi interface? What can i do to ensure that the disks come in the order that i create them? Regards Christian

4 4

iSCSI and multipath deliberation
by Marcin Kruk 16 Mar '17

16 Mar '17

In my opionion the main problem in configuration iscsi and multipath is that the ovirt developers try to start everything automaticaly during installation, and then during start services like vdsmd. But during installation process adminstrator shoud choose the right multipath WWID identifier only. And administrator should be responsible for setting multipath and iSCSI properly. Otherwise ovirt installator does everything automaticaly in the universal way which is weak due to so many storage types. Howgh :)

2 1

Change repository from PRE to Release
by FERNANDO FREDIANI 16 Mar '17

16 Mar '17

This is a multi-part message in MIME format. --------------0BDD173BE2AA4DE842ADD5EF Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hi again folks I have been using the *ovirt-4.1-pre* and *ovirt-4.1-pre-dependencies* repositories, but now that 4.1 is stable I want to change it to *ovirt-release41*. Is there any harm if I just install http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm and remove the other two 'pre' repositories from my /etc/yum.repos.d/ ? Or is there anything I should be concerned when doing that ? Thanks Fernando --------------0BDD173BE2AA4DE842ADD5EF Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hi again folks I have been using the ovirt-4.1-pre and ovirt-4.1-pre-dependencies repositories, but now that 4.1 is stable I want to change it to ovirt-release41. Is there any harm if I just install <a class="moz-txt-link-freetext" href="http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm">http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm</a> and remove the other two 'pre' repositories from my /etc/yum.repos.d/ ? Or is there anything I should be concerned when doing that ? Thanks Fernando </body> </html> --------------0BDD173BE2AA4DE842ADD5EF--

3 3

OVirt new cluster host only logins on one iSCSI
by Duarte Fernandes Rocha 16 Mar '17

16 Mar '17

Hello all, I have a Hosted engine Setup, 2 physical hosts, 1 for virtualization and another for managing OVirt. I've setup the storage via iSCSI, with 2 sessions tcp: [1] *.*.*.*:3260,1 iqn.1992**************** (non-flash) tcp: [2] *.*.*.*:3260,2 iqn.1992**************** (non-flash) Everything is working as expected until I added a new physical host to the cluster. The new host only establishes 1 iSCSI session. If I add the session manually afterwards: iscsiadm -m node -l I do get both sessions but if I put the host in maintenance it only logs out from the one that the OVirt made. Is there a way to force the new added host to login in the same iscsi targets as the other host? OVirt Engine Version: 4.0.5.5-1.el7.centos CentOS Linux release 7.3.1611 (Core) Regards, -- Duarte Fernandes Rocha <dfr(a)eurotux.com>

3 8

Fwd: [ovirt-devel] Loadbalancer.org Enterprise VA with oVirt(RHEV) 4.1
by Sandro Bonazzola 16 Mar '17

16 Mar '17

Initially shared by Nir on devel mailing list ---------- Forwarded message ---------- From: Nir Soffer <nsoffer(a)redhat.com> Date: Thu, Mar 9, 2017 at 7:57 PM Subject: [ovirt-devel] Loadbalancer.org Enterprise VA with oVirt(RHEV) 4.1 To: devel <devel(a)ovirt.org>, Adam Litke <alitke(a)redhat.com>, Ala Hino < ahino(a)redhat.com>, amureini <amureini(a)redhat.com>, Benny Zlotnik < bzlotnik(a)redhat.com>, Daniel Erez <derez(a)redhat.com>, Fred Rolland < frolland(a)redhat.com>, Idan Shaby <ishaby(a)redhat.com>, Liron Aravot < laravot(a)redhat.com>, Maor Lipchuk <mlipchuk(a)redhat.com>, "Nisan, Tal" < tnisan(a)redhat.com>, Shani Leviim <sleviim(a)redhat.com> User explains how cool is ovirt and image upload: http://www.loadbalancer.org/blog/loadbalancer-org- enterprise-va-with-ovirtrhev-4-1 Enjoy, Nir _______________________________________________ Devel mailing list Devel(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/devel -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[ANN] oVirt 4.1.1 Third Release Candidate
by Sandro Bonazzola 16 Mar '17

16 Mar '17

The oVirt Project is pleased to announce the availability of the Third Release Candidate of oVirt 4.1.1 for testing, as of March 16th, 2017 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the third release candidate of the first in a series of stabilization updates to the 4.1 series. 4.1.1 brings 35 enhancements and more than 390 bugfixes, including more than 160 high or urgent severity fixes, on top of oVirt 4.1 series This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 24 (tech preview) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt node and oVirt Live have been already built [4] - oVirt Engine Appliance has been already built Additional Resources: * Read more about the oVirt 4.1.1 release highlights: http://www.ovirt.org/release/4.1.1/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.1/ [4] http://resources.ovirt.org/pub/ovirt-4.1-pre/iso/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

upgrade 3.5 to 3.6 auto import storage domain failed
by Резников А.А. 16 Mar '17

16 Mar '17

Hi list! During the upgrade ovirt from 3.5 to 3.6, I get errors: "VDSM command failed: Can not acquire host id: (u'8905c9ac-d892-478d-8346-63b8fa1c5763 ', SanlockException (22,' Sanlock lockspace add failure ',' Invalid argument '))", "Failed to attach Storage Domain hosted_storage to Data Center Default. (User: SYSTEM)", "Failed to import the Hosted Engine Storage Domain". Thus in my data storage nfs OVF_STORE disks do not appear. The following messages appear in vdsm.log: Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,569 :: task :: 827 :: Storage.TaskManager.Task: :( resourceAcquired) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : _resourcesAcquired: Storage.8905c9ac-d8 92-478d-8346-63b8fa1c5763 (shared) Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,569 :: task :: 993 :: Storage.TaskManager.Task :: (_ decref) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Ref 1 aborting False Thread-2806 :: ERROR :: 2017-03-14 10: 40: 29,569 :: task :: 866 :: Storage.TaskManager.Task :: (_ setError) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Unexpected error Traceback (most recent last call last): File "/usr/share/vdsm/storage/task.py", line 873, in _run Return fn (* args, ** kargs) File "/usr/share/vdsm/logUtils.py", line 49, in wrapper Res = f (* args, ** kwargs) File "/usr/share/vdsm/storage/hsm.py", line 3315, in getImagesList Images = dom.getAllImages () File "/usr/share/vdsm/storage/fileSD.py", line 373, in getAllImages Self.getPools () [0], IndexError: list index out of range Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,569 :: task :: 885 :: Storage.TaskManager.Task :: (_ run) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Task._run: cd294427-d6fa-454b-9289-6660ad228c8f ('8 905c9ac-d892-478d-8346-63b8fa1c5763 ',) {} failed - stopping task Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,570 :: task :: 1246 :: Storage.TaskManager.Task: :( stop) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Stopping in state preparing (force False) Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,570 :: task :: 993 :: Storage.TaskManager.Task :: (_ decref) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Ref 1 aborting True Thread-2806 :: INFO :: 2017-03-14 10: 40: 29,570 :: task :: 1171 :: Storage.TaskManager.Task: :( prepare) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Aborting: Task is aborted: u'list index out of r Ange '- code 100 Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,570 :: task :: 1176 :: Storage.TaskManager.Task: :( prepare) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Prepare: aborted: list index out of range Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,570 :: task :: 993 :: Storage.TaskManager.Task :: (_ decref) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Ref 0 aborting True Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,570 :: task :: 928 :: Storage.TaskManager.Task :: (_ doAbort) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Task._doAbort: force False Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,571 :: resourceManager :: 980 :: Storage.ResourceManager.Owner: :( cancelAll) Owner.cancelAll requests {} Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,571 :: task :: 595 :: Storage.TaskManager.Task :: (_ updateState) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Moving from state preparing -> state aborti Ng Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,571 :: task :: 550 :: Storage.TaskManager.Task :: (__ state_aborting) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : _aborting: recover policy none Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,571 :: task :: 595 :: Storage.TaskManager.Task :: (_ updateState) Task = `cd294427-d6fa-454b-9289-6660ad228c8f`: : Moving from state aborting -> state failed Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,571 :: resourceManager :: 943 :: Storage.ResourceManager.Owner: :( releaseAll) Owner.releaseAll requests {} resources {'Storage.8905c9ac-d892 -478d-8346-6 3b8fa1c5763 ': <ResourceRef' Storage.8905c9ac-d892-478d-8346-63b8fa1c5763 ', isValid:' True 'obj:' None '>} Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,571 :: resourceManager :: 980 :: Storage.ResourceManager.Owner: :( cancelAll) Owner.cancelAll requests {} Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,572 :: resourceManager :: 619 :: Storage.ResourceManager: :( releaseResource) Trying to release resource 'Storage.8905c9ac-d892-478d-8346-63b8fa1c5763 ' Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,572 :: resourceManager :: 638 :: Storage.ResourceManager: :( releaseResource) Released resource 'Storage.8905c9ac-d892-478d-8346-63b8fa1c5763' ( 0 active Users) Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,572 :: resourceManager :: 644 :: Storage.ResourceManager: :( releaseResource) Resource 'Storage.8905c9ac-d892-478d-8346-63b8fa1c5763' is free , Finding ou T if anyone is waiting for it. Thread-2806 :: DEBUG :: 2017-03-14 10: 40: 29,572 :: resourceManager :: 652 :: Storage.ResourceManager: :( releaseResource) Storage.8905c9ac-d892-478d-8346 -63b8fa1c576 3 ', Clearing records. Does anyone have any idea how this can be fixed? Thanks, Alex.

2 7

VM switched off when migration for host maintenance fails
by Eduardo Mayoral 16 Mar '17

16 Mar '17

Hi, An interesting thing just happened on my oVirt deployment. While setting a host for maintenance, one of the VMs running on that host failed to migrate. Then ovirt-engine for some reason turned the VM off. Here are the relevant log lines from engine.log: 2017-03-16 09:56:23,324Z INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (default task-60) [61a52216] Lock Acquired to object 'EngineLock:{exclusiveLocks='[422663a9-d712-4992-7c81-165b2976073e=<VM, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName entorno127.arsysdesarrollo.lan>]', sharedLocks='null'}' 2017-03-16 09:56:23,957Z INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-60) [61a52216] EVENT_ID: VM_MIGRATION_START_SYSTEM_INITIATED(67), Correlation ID: 61a52216, Job ID: fbc5e0d7-4618-4ca8-b7a7-0fd9a43f490f, Call Stack: null, Custom Event ID: -1, Message: Migration initiated by system (VM: entorno127.arsysdesarrollo.lan, Source: llkk594.arsyslan.es, Destination: llkk593.arsyslan.es, Reason: Host preparing for maintenance). 2017-03-16 09:56:26,818Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler10) [7c6c403b-0a82-47aa-aeb4-57fbe06e20e1] VM '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan) was unexpectedly detected as 'MigratingTo' on VDS '43f43ec5-e51d-400d-8569-261c98382e3a'(llkk593.arsyslan.es) (expected on '11a82467-afa4-4e4e-bd92-3383082d0a5e') 2017-03-16 09:56:42,149Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler10) [fac8ade9-a867-4ff7-aac5-912f78cc3bb5] VM '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan) was unexpectedly detected as 'MigratingTo' on VDS '43f43ec5-e51d-400d-8569-261c98382e3a'(llkk593.arsyslan.es) (expected on '11a82467-afa4-4e4e-bd92-3383082d0a5e') 2017-03-16 09:56:54,755Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler3) [54fa9a1b-fddb-4812-b5d2-06cf92834709] VM '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan) moved from 'MigratingFrom' --> 'Down' 2017-03-16 09:56:54,755Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler3) [54fa9a1b-fddb-4812-b5d2-06cf92834709] Handing over VM '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan) to Host '43f43ec5-e51d-400d-8569-261c98382e3a'. Setting VM to status 'MigratingTo' 2017-03-16 09:56:58,160Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler4) [dd4ea7bb-85bc-410e-9a8f-357c28d85d1c] VM '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan) is running in db and not running on VDS '43f43ec5-e51d-400d-8569-261c98382e3a'(llkk593.arsyslan.es) 2017-03-16 09:56:58,161Z INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (DefaultQuartzScheduler4) [dd4ea7bb-85bc-410e-9a8f-357c28d85d1c] add VM '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan) to rerun treatment turn to maintenance while VMs are still running on it.(VM: entorno127.arsysdesarrollo.lan, Source: llkk594.arsyslan.es, Destination: llkk593.arsyslan.es). 2017-03-16 09:56:59,193Z INFO [org.ovirt.engine.core.bll.MigrateVmCommand] (org.ovirt.thread.pool-7-thread-27) [14d40a88] Lock freed to object 'EngineLock:{exclusiveLocks='[422663a9-d712-4992-7c81-165b2976073e=<VM, ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName entorno127.arsysdesarrollo.lan>]', sharedLocks='null'}' Now, I understand an VM migration may fail for a number of reasons, but in that case, shouldn't the VM keep running on the source host? I do not quite understand what happened here or how to avoid it in the future. Best regards, -- Eduardo Mayoral Jimeno (emayoral(a)arsys.es) Administrador de sistemas. Departamento de Plataformas. Arsys internet. +34 941 620 145 ext. 5153

2 1