Bug 746547

Summary: anaconda cannot install os, cant get release version
Product: Red Hat Enterprise Linux 6 Reporter: Xiaoqing Wei <xwei>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: juzhang, shuang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2d11f3b149ee62809fa9d63400b93f40f9086948a8506360784ffd52248b6fbf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-18 14:17:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda log
none
using this ks file, can install both guest and host successfully
none
/tmp/anaconda-tb* none

Description Xiaoqing Wei 2011-10-17 03:28:49 UTC
abrt version: 2.0.5
executable:     /mnt/runtime/usr/bin/python
hashmarkername: anaconda
kernel:         2.6.32-207.el6.x86_64
product:        Red Hat Enterprise Linux
time:           Sun Oct 16 23:26:49 2011
version:        6.2

description:
:The following was filed automatically by anaconda:
:anaconda 13.21.144 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.6/ConfigParser.py", line 482, in _read
:    raise MissingSectionHeaderError(fpname, lineno, line)
:  File "/usr/lib64/python2.6/ConfigParser.py", line 286, in read
:    self._read(fp, filename)
:  File "/usr/lib/anaconda/yuminstall.py", line 764, in _getReleasever
:    ConfigParser.read(c, treeinfo)
:  File "/usr/lib/anaconda/yuminstall.py", line 806, in doConfigSetup
:    self.preconf.releasever = self._getReleasever()
:  File "/usr/lib/anaconda/yuminstall.py", line 362, in setup
:    self.doConfigSetup(root=self.anaconda.rootPath)
:  File "/usr/lib/anaconda/yuminstall.py", line 1284, in doBackendSetup
:    self.ayum.setup()
:  File "/usr/lib/anaconda/backend.py", line 225, in doBackendSetup
:    if anaconda.backend.doBackendSetup(anaconda) == DISPATCH_BACK:
:  File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
:    rc = stepFunc(self.anaconda)
:  File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
:    self.moveStep()
:  File "/usr/lib/anaconda/dispatch.py", line 231, in currentStep
:    self.gotoNext()
:  File "/usr/lib/anaconda/text.py", line 602, in run
:    (step, instance) = anaconda.dispatch.currentStep()
:  File "/usr/bin/anaconda", line 1116, in <module>
:    anaconda.intf.run(anaconda)
:MissingSectionHeaderError: File contains no section headers.
:file: /tmp/.treeinfo, line: 1
:'CWS\t\\\x06\x01\x00x\x9c\xc4{\t<\x94o\xdf\xef=c\x86\xb1\xc4\x8c\xad\xb1\xd5\x8cu\xecc\xc9\x964\x86,C\xb2\xaf\xa9\xb1o\xd9\t-\x0c\x86\xc6\x1aB\x94e\xec\x14\x8a\xec\x95-[B\xb2\x15\n'

reason:
:MissingSectionHeaderError: File contains no section headers.
:file: /tmp/.treeinfo, line: 1
:'CWS\t\\\x06\x01\x00x\x9c\xc4{\t<\x94o\xdf\xef=c\x86\xb1\xc4\x8c\xad\xb1\xd5\x8cu\xecc\xc9\x964\x86,C\xb2\xaf\xa9\xb1o\xd9\t-\x0c\x86\xc6\x1aB\x94e\xec\x14\x8a\xec\x95-[B\xb2\x15\n'

Comment 2 Xiaoqing Wei 2011-10-17 04:43:14 UTC
Created attachment 528444 [details]
anaconda log

Comment 3 Xiaoqing Wei 2011-10-17 04:59:19 UTC
Created attachment 528450 [details]
using this ks file, can install both guest and host successfully

Comment 4 Xiaoqing Wei 2011-10-17 11:55:21 UTC
to reproduce, just perform a http based installation,
for me , I am using 
http://tree.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL-6.2/RHEL6.2-20111013.1/x86_64/os/

after partitioned, anaconda buggy as above.

Comment 5 Chris Lumens 2011-10-17 13:36:49 UTC
Please attach the complete /tmp/anaconda-tb-* file to this bug report, though this looks an awful lot like a tree composition problem.

Comment 6 Xiaoqing Wei 2011-10-18 05:02:05 UTC
Created attachment 528704 [details]
/tmp/anaconda-tb*

Comment 9 David Cantrell 2011-10-18 14:17:48 UTC
This just looks like a problem with tree synchronization on our fileservers.  And in comment #8 you say another tree works fine.  Closing this as not a bug.