Hide Forgot
Description of problem: luns table remain with lun information in case createStoragePool is rolled-back after createStorageDomain. implications: - when logged in again to this target, lun doesn't appear in GUI and user can't use it unless it runs an sql statement that manually deletes lun from luns table. repro: - createStorageDomain (iscsi) - createStoragePool (restart vdsm once command is initiated) - vdsm is restated - createStoragePool gets roll-backed - storage domain is missing from GUI - try to create new storage domain - discover server that expose lun used to create storage domain from previous step - login to that lun - lun is missing from GUI just to show its not host problem; running multipath -r or pvscan shows the lun. running sql statement shows that lun still exists in luns table iAJaDA-yAf2-YEQs-1LVS-obt9-d3D1-XaVQnh | 36090a068a0744b3c07efb43c5b25dda0 | 4jl37C-HqIX-3gf2-vTdp-3cGH-HYNn-R3i9oX | SEQLOGIC_100E-00_6090A068A0744B3C07EFB43C5B25DDA0 | 0 | EQLOGIC | 100E-00 | 75 git log: 4aedff6b61f714f8e24ccb9efff052e347d8de3f
Created attachment 549485 [details] engine log.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.