Bug 1299488 - error populating transaction after 10 tries: Packages/gsettings-desktop-schemas
Summary: error populating transaction after 10 tries: Packages/gsettings-desktop-schemas
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: ISO Installer
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 1.0
Assignee: John Matthews
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-18 13:47 UTC by Thom Carlin
Modified: 2016-04-29 16:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-18 14:04:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Thom Carlin 2016-01-18 13:47:02 UTC 
Description of problem:

Fatal error during package install.


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

RHCIOOO-7-RHEL-7-20160115.t.0 (mediaid= 1452882895.133201)

How reproducible:

Unsure

Steps to Reproduce:
1. Install RCHS-I OOO ISO
2.
3.

Actual results:

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

 error populating transaction after 10 retries: failure: Packages/gsettings-desktop-schemas-3.8.2-3.el7.x86_64.rpm from anaconda: [Errno 256] No more mirrors to try. [Exit Installer]

Expected results:

Successful install

Additional info:

I see /run/install/repo/Packages/gsettings-desktop-schemas-3.8.2-3.el7.x86_64.rpm with size 425956 dated 1/25/14 with SELinux context iso9660_t.

Per /tmp/packaging.log, looks to be the first RPM being installed.

Trying reinstalling same ISO for reproducer.
Comment 1 Thom Carlin 2016-01-18 14:04:18 UTC 
ISO already had it's sha256sum verified.  I re-verified the ISO md5 fragment checksums.

Reproducibility:

Worked second time.  Closing as WORKSFORME.

Unsure what's going on since it is the same hardware....
Note You need to log in before you can comment on or make changes to this bug.