Bug 589088 - AttributeError: 'Anaconda' object has no attribute 'protected'
AttributeError: 'Anaconda' object has no attribute 'protected'
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
rawhide
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
anaconda_trace_hash:ef13b613d727a86ea...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-05 07:22 EDT by Bojan Smojver
Modified: 2010-05-05 08:28 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-05 08:28:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (94.40 KB, text/plain)
2010-05-05 07:22 EDT, Bojan Smojver
no flags Details

  None (edit)
Description Bojan Smojver 2010-05-05 07:22:14 EDT
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 07:22:19 EDT
Created attachment 411547 [details]
Attached traceback automatically from anaconda.
Comment 2 Michal Schmidt 2010-05-05 07:55:05 EDT
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 08:28:25 EDT
This bug is caused by using an updates.img meant to be used with TC1 with the beta.

Note You need to log in before you can comment on or make changes to this bug.