Bug 589088

Summary: AttributeError: 'Anaconda' object has no attribute 'protected'
Product: [Fedora] Fedora Reporter: Bojan Smojver <bojan>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: anaconda-maint-list, hdegoede, jonathan, mschmidt, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:ef13b613d727a86eab43f631fb1ba2b5b07b21f5ca7a65b57c6021c5cfe6e955
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-05 12:28:25 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
Attached traceback automatically from anaconda. none

Description Bojan Smojver 2010-05-05 11:22:14 UTC
The following was filed automatically by anaconda:
anaconda 13.37.2 exception report
Traceback (most recent call first):
  File "/tmp/updates/storage/__init__.py", line 88, in storageInitialize
    if anaconda.protected:
  File "/tmp/updates/dispatch.py", line 205, in moveStep
    rc = stepFunc(self.anaconda)
  File "/tmp/updates/dispatch.py", line 126, in gotoNext
    self.moveStep()
  File "/tmp/updates/gui.py", line 1401, in setScreen
    self.anaconda.dispatch.gotoNext()
  File "/tmp/updates/gui.py", line 1314, in nextClicked
    self.setScreen ()
AttributeError: 'Anaconda' object has no attribute 'protected'

Comment 1 Bojan Smojver 2010-05-05 11:22:19 UTC
Created attachment 411547 [details]
Attached traceback automatically from anaconda.

Comment 2 Michal Schmidt 2010-05-05 11:55:05 UTC
It may an actual bug in anaconda, but it also may be caused by the medium errors (unrecovered read errors) while reading from /dev/sr0 as reported in the log.

Comment 3 Hans de Goede 2010-05-05 12:28:25 UTC
This bug is caused by using an updates.img meant to be used with TC1 with the beta.