Bug 1114783

Summary: anaconda reports no disks detected, yet libblkid sees them
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: python-blivetAssignee: David Lehman <dlehman>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: amulhern, anaconda-maint-list, bcl, dlehman, vpodzime
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-01 15:25:01 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
screenshot
none
storage.log
none
anaconda.log
none
program.log
none
journal none

Description Chris Murphy 2014-07-01 02:07:20 UTC 
Created attachment 913601 [details]
screenshot

Description of problem: Anaconda "Installation Destination" Device Selection lists no disks. Yellow banner at the bottom says "No disks detected." There is an internal SATA SSD in this laptop, nothing unusual about the hardware.


Version-Release number of selected component (if applicable):
anaconda-21.45-1.fc21.x86_64
python-blivet-0.59-1.fc21.noarch


How reproducible:
Non-deterministic.

Steps to Reproduce:
1.
2.
3.

Actual results:
No disks detected.


Expected results:
Should appear as a SATA device.

Additional info:
Bug 1114770 may be related. I get either this bug or bug 1114770 most of the time, maybe 20% of the time the SATA SSD appears in anaconda as sda.

lsblk shows sda and all of its partitions, so seems either anaconda or python-blivet are confused.
Comment 1 Chris Murphy 2014-07-01 02:08:23 UTC 
Created attachment 913602 [details]
storage.log
Comment 2 Chris Murphy 2014-07-01 02:08:52 UTC 
Created attachment 913603 [details]
anaconda.log
Comment 3 Chris Murphy 2014-07-01 02:09:13 UTC 
Created attachment 913604 [details]
program.log
Comment 4 Chris Murphy 2014-07-01 02:11:12 UTC 
Created attachment 913606 [details]
journal

journalctl -l -b -o short-monotonic
Comment 5 Chris Murphy 2014-07-01 02:16:14 UTC 
21:56:21,805 INFO blivet: type detected on 'sda' is 'multipath_member'
21:56:43,641 DEBUG blivet: ignoring partition sda1 on multipath_member


OK so it probably is ultimately bug 1114770, but why does blivet sometimes ignore and conclude no disks detected, and other times it shows it as a multipath device?
Comment 6 Chris Murphy 2014-07-01 02:19:07 UTC 
OK no this is somehow different because /dev/mapper doesn't have any multipath entries with this boot, whereas there are mpathc entries in /dev/mapper for bug 1114770.
Comment 7 Chris Murphy 2014-07-01 02:38:58 UTC 
I think multpathd is just confused and it then confuses anaconda or blivet. Probably a dup of 1114770, but I'll leave it open in case the variable behavior is considered an anaconda or blivet bug.
Comment 8 Brian Lane 2014-07-01 15:25:01 UTC 
We can only go by what the system tells us. multipath is saying that it is a valid device, although the setup seems to have failed.

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