Bug 620297

Summary: Failed to enter stage2 in Anaconda
Product: [Fedora] Fedora Reporter: MingtaoNiu <mniu>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: anaconda-maint-list, jonathan, rhe, robatino, satellitgo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-02 07:49:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 611990    
Description Flags
error info about failing to enter stage2 none

Description MingtaoNiu 2010-08-02 02:54:51 UTC
Created attachment 435945 [details]
error info about failing to enter stage2

Description of problem:
When I install in method of http using command "repo=http://...", it failed to enter stage2 in anaconda with error description "IOError: invalid Python installation: unable to open /usr/include/python2.7/pyconfig-32.h(No such file or directory)"

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

anaconda 14.12

How reproducible:

Steps to Reproduce:
1.Boot from CDROM: Fedora-14-alpha-tc1-i386-boot.iso 
Actual results:
IOError: invalid Python installation: unable to open /usr/include/python2.7/pyconfig-32.h(No such file or directory)

Expected results:
   1.  Anaconda uses the package repository from the HTTP server provided.
   2. Install completes successfully
   3. Package errors (install.log) should not occur
   4. System boots successfully 

Additional info:

Comment 1 He Rui 2010-08-02 03:02:19 UTC
Reproduced in F14-alpha.tc1-x86_64-boot.iso with anaconda 14.12.

1. Boot the system
2. Error occurred before accessing anaconda stage2

Comment 2 He Rui 2010-08-02 07:49:15 UTC

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