Bug 1248476

Summary: [FCoE] ixgbe/bnx2fc FCoE disk is added as local disk after adding in Anaconda GUI
Product: Red Hat Enterprise Linux 7 Reporter: Radek Vykydal <rvykydal>
Component: python-blivetAssignee: Radek Vykydal <rvykydal>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: bgoncalv, jstodola, xhe
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-blivet-0.61.15.14-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 08:49:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
storage.log
none
beaker job for reproducer none

Description Radek Vykydal 2015-07-30 11:37:01 UTC 
Created attachment 1057634 [details]
storage.log

After adding FCoE disk (and doing Refresh List if needed) in Anaconda GUI it is added as a local disk (not recognized as FCoE disk).

Hit with:

http://download.devel.redhat.com/nightly/RHEL-7.2-20150722.n.0/compose/Server/x86_64/os/

here:

https://beaker.engineering.redhat.com/jobs/1032884

Seems like a fallout of
https://github.com/rhinstaller/blivet/commit/0f986f932f7a9bcbd48b0b711e5b270a76b72083

Sending a patch for review.
Comment 2 Radek Vykydal 2015-07-30 11:42:37 UTC 
https://github.com/rhinstaller/blivet/pull/189
Comment 3 Radek Vykydal 2015-07-30 11:48:39 UTC 
Created attachment 1057636 [details]
beaker job for reproducer

To reproduce run attached beaker job.

This kickstart (not relevant to the bug) was used
http://10.34.39.2/ks/rv/ks.fcoebkr.cfg

keyboard us
lang en_US.UTF-8
timezone America/New_York --utc
rootpw chrbkrchl
clearpart --all --drives=sda
Comment 6 errata-xmlrpc 2015-11-19 08:49:06 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2015-2232.html