Created attachment 647180 [details] logs Description of problem: vdsm continues with extend while engine rolls back. the domain will appear active until the next time it will be put in maintenance -> activated since no ConnectStorageServer will be sent for extended lun. Version-Release number of selected component (if applicable): si24.2 vdsm-4.9.6-43.0.el6_3.x86_64 How reproducible: 100% Steps to Reproduce: in a two hosts cluster, create 3 iscsi domain. 1. create and run a vm -> do a live storage migration 2. try to extend both src domain and dst domain 3. after we fail because of timeout, try to extend the domains again 4. put domain in maintenance -> try to activate Actual results: 1. extend will be reported as failed and engine will rollback while operation will succeed in vdsm 2. domain size and vgs on host will show that the vgs was extended. 3. we will not be able to activate the domain once we put it in maintenance because engine will not send ConnectStorageServer on the added lun. Expected results: sync between vdsm and engine. Additional info:logs
I attached the vgs -o all output. I extended Dafna-ext1 with Dafna-ext3 and extended Dafna-ext2 with Dafna-ext4 below table shows only original luns: engine=# SELECT * from storage_server_connections ; id | connection | user_name | password | iqn | port | portal | storage_type | mount_options | vfs_type | nfs_version | nf s_timeo | nfs_retrans --------------------------------------+--------------------------------------------------------------------------------+-----------+----------+-----------------+------+--------+--------------+---------------+----------+-------------+--- --------+------------- d95b1e48-89c4-4980-b33c-590be15b5a9e | 10.35.64.10 | | | Dafna-si24_2-01 | 3260 | 1 | 3 | | | | | f56378df-c771-49aa-a04c-ab66f6c92a6c | 10.35.64.10 | | | Dafna-si24_2-02 | 3260 | 1 | 3 | | | | | 16af35c8-0d11-47dd-a6c2-d7b33e72146f | 10.35.64.10 | | | Dafna-si24_2-03 | 3260 | 1 | 3 | | | | | 6e152e06-98ff-4c53-9d4b-989c29c6945d | wolf.qa.lab.tlv.redhat.com:/volumes/wolf/Dafna_New_Export_0_nfs_71122241851338 | | | | | | 1 | | | | | 08903697-3af9-4f9a-a046-5a7de37b0876 | wolf:/volumes/wolf/shared/shared_iso_domain | | | | | | 1 | | | | | 4089f55c-4bf5-4929-9a9a-4d30c2b2ee70 | 10.35.64.10 | | | Dafna-ext1 | 3260 | 1 | 3 | | | | | d4d8956b-2dac-47a7-936e-2a79e9e316c9 | 10.35.64.10 | | | Dafna-ext2 | 3260 | 1 | 3 | | | | | [root@gold-vdsc ~]# vdsClient -s 0 getStorageDomainInfo dd7e095b-b828-4ae7-8040-9138fe390932 uuid = dd7e095b-b828-4ae7-8040-9138fe390932 vguuid = hjm9xF-e1yq-l9zs-Rbq5-DjBW-QlL0-eQ5YUw lver = -1 state = OK version = 3 role = Regular pool = ['14090d72-316c-11e2-9280-001a4a169741'] spm_id = -1 type = ISCSI class = Data master_ver = 0 name = ext2 [root@gold-vdsc ~]# vgs dd7e095b-b828-4ae7-8040-9138fe390932 VG #PV #LV #SN Attr VSize VFree dd7e095b-b828-4ae7-8040-9138fe390932 2 8 0 wz--n- 59.25g 34.38g [root@gold-vdsc ~]# ls -l /dev/mapper/1Dafna-ext 1Dafna-ext11353240 1Dafna-ext21353240 1Dafna-ext31353240 1Dafna-ext41353240
Created attachment 647183 [details] vgs
Tested according to steps in comment #0. Extend to both src and dst storage domains succeed when doing it while live migrating a disk. Allon, are those the expected results?
As mentioned in the subject, extend storage domain should succeed while LSM. Moving to VERIFIED based on the test described in comment #11 Verified using av9
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html