Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 557928

Summary:	rats_install encountered 'Storage Activation Failed' - no anacdump.txt written
Product:	[Fedora] Fedora	Reporter:	James Laska <jlaska>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	awilliam, dcantrell, jonathan, jturner, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-13.26-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-02-08 18:20:34 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:
Bug Depends On:
Bug Blocks:	538274

Description James Laska 2010-01-22 20:10:22 UTC

Description of problem:

During a rawhide acceptance test run (using install.py [1]), a storage activation error was encountered.  Since this is an automated kickstart test, it monitors for /tmp/anacdump.txt and appropriately fails the test if such a file exists.  In this case, no dump file was created.  Instead, the user was prompted during the kickstart install as to whether they wanted to file a bug or not.

If the subsequent traceback is needed for diagnosing the root cause of this failure, I'd like to request that for automated kickstart installs, the user is not prompted to write a kickstart file.  Instead, it is saved directly to /tmp/anacdump.txt

[1] http://git.fedorahosted.org/git/autoqa.git?p=autoqa.git;a=blob;f=tests/rats_install/install.py;hb=HEAD

Version-Release number of selected component (if applicable):
 * anaconda-13.22-1.fc13

How reproducible:
 * This doesn't seem like a common storage bug, I haven't seen it since, but this issue is meant more to track the failure behavior for this class of storage issues.

Steps to Reproduce:
1. Initiate a rats_install/install.py test

$ python install.py -a x86_64 http://alt.fedoraproject.org/pub/alt/stage/rawhide/x86_64/os

Or, just install using the following details

 * stage2=http://alt.fedoraproject.org/pub/alt/stage/rawhide/x86_64/os
 * repo=http://download.fedoraproject.org/pub/fedora/linux/development/x86_64/os
 * updates=http://jlaska.fedorapeople.org/updates-557588.img
 * ks=http://git.fedorahosted.org/git/autoqa.git?p=autoqa.git;a=blob;f=tests/rats_install/ks.cfg;h=0fa5954c08431ca3562605eb8ca2a2bfcd5e00e4;hb=HEAD
  
Actual results:

   ┌─────────────────────┤ Storage Activation Failed ├─────────────────────┐
   │                                                                       │
   │ An error was encountered while activating your storage configuration. │
   │                                                                       │
   │    (root@dell-t5400)-(7/pts/5)-(01/22/2010 11:50am)-8 INFO    : ↑     │
(~)>    Running... ['lvm', 'lvcreate', '-L', '6760m', '-n',          ▮     │
   │    'lv_root', 'VolGroup']                                       ▒     │    
   │                                                                 ▒     │    
   │                                                                 ▒     │    
   │                                                                 ↓     │    
   │                                                                       │    
   │          ┌──────────┐                    ┌────────────────┐           │    
   │          │ File Bug │                    │ Exit installer │           │
   │          └──────────┘                    └────────────────┘           │
   │                                                                       │
   │                                                                       │
   └───────────────────────────────────────────────────────────────────────┘

Expected results:

For a kickstart install, if a failure occurs I expected it to automatically record the traceback locally as /tmp/anacdump.txt.
Additional info:

Comment 1 Adam Williamson 2010-02-05 16:54:36 UTC

Agreed at blocker bug review of 2010-02-05 that this is not an Alpha blocker.

Comment 2 Chris Lumens 2010-02-08 18:20:34 UTC

I've updated the error handling here to make almost all storage exceptions fatal errors that will result in the usual exception handling dialog appear.  However there are still certain cases where the error is not due to an anaconda bug, and those will still cause the more generic dialog to appear.  The intention here is to not make those look like anaconda bugs.