RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 495457 [details]
vdsm log

Description of problem:
During creation of iscsi data storage domain ,the operation fails with error:
raise se.PhysDevInitializationError(device)

Version-Release number of selected component (if applicable):
RHEVM: ic-114
vdsm:  4.9-58.el6.x86_64
lvm2:   2.02.83-3.el6.x86_64

Setup:
One ISCSI Data Storage Domain
Two hosts (rhel6_u1)


How reproducible:
1)Add storage data domain via RHEVM with first host
2)Remove storage domain via RHEVM with second host
3)Repeat few times  
  
Actual results:
  File "/usr/share/vdsm/storage/task.py", line 862, in _run
    return fn(*args, **kargs)
  File "/usr/share/vdsm/storage/hsm.py", line 859, in public_createVG
    lvm.createVG(vgname, devices, blockSD.STORAGE_UNREADY_DOMAIN_TAG)
  File "/usr/share/vdsm/storage/lvm.py", line 736, in createVG
    _initpv(pvs[0], withmetadata=True)
  File "/usr/share/vdsm/storage/lvm.py", line 648, in _initpv
    raise se.PhysDevInitializationError(device)

CreateVG fails since the LUN it tries to use is already used by something else

Thread-3751::DEBUG::2011-04-28 11:46:20,728::lvm::352::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvcreate --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 filter = [ \\"a%/dev/mapper/360a98000572d45366b4a6175704e3557%\\", \\"r%.*%\\" ] }  global {  locking_type=1  prioritise_write_locks=1  wait_for_locks=1 }  backup {  retain_min = 50  retain_days = 0 } " --metadatasize 128m /dev/mapper/360a98000572d45366b4a6175704e3557' (cwd None)
Thread-3751::DEBUG::2011-04-28 11:46:20,857::lvm::352::Storage.Misc.excCmd::(cmd) FAILED: <err> = "  Can't open /dev/mapper/360a98000572d45366b4a6175704e3557 exclusively.  Mounted filesystem?\n"; <rc> = 5

would you reproduce the case and research what uses that LUN (pvs, lvs, vgs)?
It seems like the LUN is taken by a former storage domain that was never formatted. Does issuing a manual `vgscan` make that vg disappear?

*** This bug has been marked as a duplicate of bug 701671 ***