Bug 712840

Summary: install exited abnormally - value error: invalid flag provided
Product: [Fedora] Fedora Reporter: upgradeservices
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-13 17:16:27 UTC Type: ---
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
anaconda pyparted invalid flag bug none

Description upgradeservices 2011-06-13 10:53:14 UTC 
Description of problem:

anaconda crashes when installing in a vm from iso created with pungi.
pyparted invalid flag provided error occurs when installing to vm guest, like virtualbox.
same issue as previously fixed in: https://bugzilla.redhat.com/show_bug.cgi?id=586046

Version-Release number of selected component (if applicable):
anaconda - latest stable

How reproducible:
kick off an installation within vm, with an iso created with pungi.
error occurs every time.

Steps to Reproduce:
1. kick off an installation within vm, with an iso created with pungi.
2. installation ends in a error
  
Actual results:
Impossible to install.

Expected results:
Installation should not crash.
Comment 1 upgradeservices 2011-06-13 11:07:03 UTC 
Created attachment 504413 [details]
anaconda pyparted invalid flag bug
Comment 2 upgradeservices 2011-06-13 14:00:45 UTC 
just tried installing on a physical - same issue, so this is not limited to just a vm.

try to run install from the small netinstall iso to replicate:
http://fx64.net/f15/
Comment 3 Brian Lane 2011-06-13 17:16:27 UTC 

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