Bug 1194361 - liveimg installations fails with mount error 32
Summary: liveimg installations fails with mount error 32
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ovirt-node-ng
TreeView+ depends on / blocked
 
Reported: 2015-02-19 16:10 UTC by Fabian Deutsch
Modified: 2015-02-20 09:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-20 09:03:10 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
anaconda.log (128.12 KB, text/plain)
2015-02-19 16:11 UTC, Fabian Deutsch 		no flags Details
installation.ks (2.07 KB, text/plain)
2015-02-19 16:11 UTC, Fabian Deutsch 		no flags Details
View All

Description Fabian Deutsch 2015-02-19 16:10:54 UTC 
Description of problem:
An installation involving la liveimg source fails with "mount error 32"

Version-Release number of selected component (if applicable):
Fedora 22
10 16:04:54,622 INFO anaconda: /sbin/anaconda 22.20-1

How reproducible:
always

Steps to Reproduce:
1. Use attached ks and a squashfs img install using the follow arguments:
'console=ttyS0 quiet cmdline inst.cmdline inst.ks=http://10.0.2.2:57954/installation.ks inst.stage2=http://10.0.2.2:57954/ '
2.
3.

Actual results:
Fails to install

Expected results:
Succeeds to instal

Additional info:
Comment 1 Fabian Deutsch 2015-02-19 16:11:21 UTC 
Created attachment 993687 [details]
anaconda.log
Comment 2 Fabian Deutsch 2015-02-19 16:11:37 UTC 
Created attachment 993688 [details]
installation.ks
Comment 3 Fabian Deutsch 2015-02-19 16:20:06 UTC 
The exact same kickstart and squashfsimg work with the Fedora 21 pxeboot kernel, initrd and squashfs.
Comment 4 David Shea 2015-02-19 16:23:46 UTC 
Please attach the traceback file.
Comment 5 Fabian Deutsch 2015-02-20 09:03:10 UTC 
This does not happen to me anymore with todays nightly build.
Note You need to log in before you can comment on or make changes to this bug.