Bug 1330291 - Server images fail to boot due to missed Blivet 2.0 conversion in anaconda.py
Summary: Server images fail to boot due to missed Blivet 2.0 conversion in anaconda.py
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F25AlphaBlocker
TreeView+ depends on / blocked
 
Reported: 2016-04-25 19:29 UTC by Adam Williamson
Modified: 2016-04-29 17:07 UTC (History)
5 users (show)

Fixed In Version: anaconda-25.9-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-29 17:07:00 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Adam Williamson 2016-04-25 19:29:53 UTC 
Moving this over from https://bugzilla.redhat.com/show_bug.cgi?id=1329019 . In recent Rawhide builds, Server images fail to boot. They never reach the anaconda interface, when it tries to start up, the system just sticks at this screen:

https://openqa.fedoraproject.org/tests/14376/modules/_boot_to_anaconda/steps/8

per sgallagh, this seems to be happening because of this traceback:

Traceback (most recent call last):
  File "/sbin/anaconda", line 1099, in <module>
    setupDisplay(anaconda, opts, addon_paths)
  File "/sbin/anaconda", line 580, in setupDisplay
    anaconda.initInterface(addons)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/anaconda.py", line 240, in initInterface
    self._intf = TextUserInterface(self.storage, self.payload,
  File "/usr/lib64/python3.5/site-packages/pyanaconda/anaconda.py", line 176, in storage
    self._storage.setDefaultFSType(self.instClass.defaultFS)
AttributeError: 'Blivet' object has no attribute 'setDefaultFSType'

This is an automatic F25 Alpha blocker as it renders two release-blocking images entirely DOA.
Comment 1 David Shea 2016-04-29 17:07:00 UTC 
Fixed in 8d5a90b459cf216aa0edbcfc16533803cdfe3703
Note You need to log in before you can comment on or make changes to this bug.