Hi, All! When trying to attach iscsi device from my storage system, ovirt complains, that it cannot create a storage pool. In logs I can see only this: ---------------------------------------------------------- RuntimeError(u'Error creating a storage pool: (u"spUUID=3fcace71-cd2b-4ab4-9d64-8ef926ead05a, poolName=hosted_datacenter, masterDom=71b0d510-c24a-49fa-86ec-6b5ebf530140, domList=[u\'71b0d510-c24a-49fa-86ec-6b5ebf530140\', u\'793985b7-9d11-44a4-bf68-4b509a967a52\'], masterVersion=1, clusterlock params: ({\'LEASETIMESEC\': 60, \'LOCKPOLICY\': \'ON\', \'IOOPTIMEOUTSEC\': 10, \'LEASERETRIES\': 3, \'LOCKRENEWALINTERVALSEC\': 5})",)',), <traceback object at 0x35935a8>) ----------------------------------------------------------- I have verified, that this block device can be successfully connected and partitioned on the same server using standard tools (iscsiadm, parted, mount), so, storage system on its own is working fine. My question is: what are requirements for block device in order for it to be compliant with ovirt? I know, that block size must be 512 bytes, but anything else? Thank you in advance, any comments appreciated. Sergei.
Sergei hi, Which version are you using ? Please provide the VDSM and engine logs at the time of the error. Thanks, Fred On Fri, Jan 6, 2017 at 9:30 AM, Sergei Hanus <getallad@gmail.com> wrote:
Hi, All!
When trying to attach iscsi device from my storage system, ovirt complains, that it cannot create a storage pool.
In logs I can see only this: ---------------------------------------------------------- RuntimeError(u'Error creating a storage pool: (u"spUUID=3fcace71-cd2b-4ab4-9d64-8ef926ead05a, poolName=hosted_datacenter, masterDom=71b0d510-c24a-49fa-86ec-6b5ebf530140, domList=[u\'71b0d510-c24a-49fa-86ec-6b5ebf530140\', u\'793985b7-9d11-44a4-bf68-4b509a967a52\'], masterVersion=1, clusterlock params: ({\'LEASETIMESEC\': 60, \'LOCKPOLICY\': \'ON\', \'IOOPTIMEOUTSEC\': 10, \'LEASERETRIES\': 3, \'LOCKRENEWALINTERVALSEC\': 5})",)',), <traceback object at 0x35935a8>) -----------------------------------------------------------
I have verified, that this block device can be successfully connected and partitioned on the same server using standard tools (iscsiadm, parted, mount), so, storage system on its own is working fine.
My question is: what are requirements for block device in order for it to be compliant with ovirt? I know, that block size must be 512 bytes, but anything else?
Thank you in advance, any comments appreciated.
Sergei.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, Fred. I'm using release 4.0.5. I made a fresh redeploy today and reproduced the issue. I'm attaching engine and vdsm log file, the time to look is around 12:15:13 Also, when I try to delete storage domain from engine - it also returns error, so, this domain seems to be stuck in configuration (it is also displayed at the end of engine log) Appreciate any comments. Sergei
Sergei, The files are empty, can you please resend ? Thanks On Mon, Jan 9, 2017 at 1:00 PM, Sergei Hanus <getallad@gmail.com> wrote:
Hi, Fred. I'm using release 4.0.5. I made a fresh redeploy today and reproduced the issue.
I'm attaching engine and vdsm log file, the time to look is around 12:15:13
Also, when I try to delete storage domain from engine - it also returns error, so, this domain seems to be stuck in configuration (it is also displayed at the end of engine log)
Appreciate any comments.
Sergei
Fred, sorry, my fault. Now I have verified the contents. Sergei. On Mon, Jan 9, 2017 at 6:27 PM, Fred Rolland <frolland@redhat.com> wrote:
Sergei,
The files are empty, can you please resend ?
Thanks
On Mon, Jan 9, 2017 at 1:00 PM, Sergei Hanus <getallad@gmail.com> wrote:
Hi, Fred. I'm using release 4.0.5. I made a fresh redeploy today and reproduced the issue.
I'm attaching engine and vdsm log file, the time to look is around 12:15:13
Also, when I try to delete storage domain from engine - it also returns error, so, this domain seems to be stuck in configuration (it is also displayed at the end of engine log)
Appreciate any comments.
Sergei
Sergei hi, In the log, I can see that there is an issue in the VDSM code when parsing your PV due to the ":" in its name. Can you please open a bug with the logs ? Also, to understand why LVM is not seeing your PV , can you run the following command and supply the ouput ? lvm pvs -vvvv --config ' devices { preferred_names = ["^/dev/mapper/"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ '\''a|/dev/mapper/SioFABRICVicinity_iqn.2015-03.com.iofabric:ovirt-master-00|'\'', '\''r|.*|'\'' ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 use_lvmetad=0 } backup { retain_min = 50 retain_days = 0 } ' --noheadings --units b --nosuffix --separator '|' --ignoreskippedcluster -o uuid,name,size,vg_name,vg_uuid,pe_start,pe_count,pe_alloc_count,mda_count,dev_size /dev/mapper/SioFABRICVicinity_iqn.2015-03.com.iofabric:ovirt-master-00 Thanks, Fred On Tue, Jan 10, 2017 at 9:22 AM, Sergei Hanus <getallad@gmail.com> wrote:
Fred, sorry, my fault. Now I have verified the contents.
Sergei.
On Mon, Jan 9, 2017 at 6:27 PM, Fred Rolland <frolland@redhat.com> wrote:
Sergei,
The files are empty, can you please resend ?
Thanks
On Mon, Jan 9, 2017 at 1:00 PM, Sergei Hanus <getallad@gmail.com> wrote:
Hi, Fred. I'm using release 4.0.5. I made a fresh redeploy today and reproduced the issue.
I'm attaching engine and vdsm log file, the time to look is around 12:15:13
Also, when I try to delete storage domain from engine - it also returns error, so, this domain seems to be stuck in configuration (it is also displayed at the end of engine log)
Appreciate any comments.
Sergei
Hi, Fred. Thank you for the investigation. Requested output is attached. I will also open a bug per your request. Sergei.
Bug ID 1413867 <https://bugzilla.redhat.com/show_bug.cgi?id=1413867> has been created. Sergei.
participants (2)
-
Fred Rolland -
Sergei Hanus