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 875421 - Anaconda fails with Could not run transaction
Summary: Anaconda fails with Could not run transaction
Keywords:
Status: CLOSED DUPLICATE of bug 875422
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-11 05:31 UTC by Shawn Starr
Modified: 2012-11-11 05:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-11 05:37:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Shawn Starr 2012-11-11 05:31:28 UTC 
Description of problem:

Anaconda aborts install with poor error

"The following error occurred while installing. This is a fatal error and installation will be aborted.

Could not run transaction
"

Version-Release number of selected component (if applicable):
Any Fedora 18 build of Anaconda

How reproducible: 100%

Steps to Reproduce:
1. Set VM image disk size to 5GiB
2. Select GNOME Desktop for install
3. Dialog box pops up that it cannot continue 'transaction error'
  
Actual results:
package.log shows:

various errors (not enough space)

ERR packaging: installing package ibus-typing-booster-0.0.20-1.fc18.noarch needs 77MB on the / filesystem


Expected results:
Should gracefully fail with a error a user can understand


Additional info:

Legacy Anaconda would gracefully tell user not enough space.
Comment 1 Shawn Starr 2012-11-11 05:37:43 UTC 

*** This bug has been marked as a duplicate of bug 875422 ***
Note You need to log in before you can comment on or make changes to this bug.