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 578783 [details]
vdsm.log

Description of problem:
When adding a FC storage domain through the RHEVM Admin interface, the installation disk is presented as a valid FC disk for the storage domain.  This should be filetered out.

RHEV-H is installed on an FC Lun.

Version-Release number of selected component (if applicable):
RHEVM 3.0.2_0001-2
vdsm-4.9.6-8.el6
rhev-hypervisor-6.3-20120419.0.el6

How reproducible:
Always

Steps to Reproduce:
1.install rhev-h to FC lun
2.register to rhevm in an FC datacenter
3.create new storage domain using rhevh as the host to create
  
Actual results:
presents all fc luns including the installation disk

Expected results:
should filter the disk(s) where rhev-h is installed

Additional info:

I believe this is not specific to RHEV-H: if we install on a RHEL host which has mounted filesystems on its FC devices, vdsm would report these FCs as available for a storage domain. And although dangerous, this is not new and I do not think that it is a blocker.

According to Eduardo, this is solved as part of

http://gerrit.ovirt.org/5515

which would report locally-mounted devices as "gray".

http://gerrit.usersys.redhat.com/#change,1338

fixed in vdsm-4.9.6-21.0.el6_3.x86_64, when I choose the mounted-lun and click ok, new pop-up with approval latch is displayed.

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-2012-1508.html