Bug 913559

Summary: NameError: global name 'productName' is not defined
Product: [Fedora] Fedora Reporter: Kamil Páral <kparal>
Component: python-blivetAssignee: David Lehman <dlehman>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: anaconda-maint-list, bcl, dlehman, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: DevConf
Fixed In Version: blivet-0.7-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-26 17:29:12 UTC Type: Bug
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-tb none

Description Kamil Páral 2013-02-21 13:33:02 UTC
Description of problem:
anaconda 19.7 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1419, in sanityCheck
    "to continue.") % (productName,))
  File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 342, in checkStorage
    StorageChecker.warnings) = self.storage.sanityCheck()
  File "/usr/lib64/python2.7/threading.py", line 504, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 119, in run
    threading.Thread.run(self, *args, **kwargs)
NameError: global name 'productName' is not defined

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

How reproducible:
no idea

Steps to Reproduce:
1. no idea

Comment 1 Kamil Páral 2013-02-21 13:33:40 UTC
Created attachment 700524 [details]
anaconda-tb

Comment 2 Kamil Páral 2013-02-21 13:37:44 UTC
I reproduced it by entering storage spoke, not selecting any disk, returning back to main hub, (and then maybe by entering the storage spoke again, not sure about this).