Bug 981423

Summary: 'can't get boot images' error
Product: [Fedora] Fedora Reporter: Adam Huffman <bloch>
Component: fedupAssignee: Will Woods <wwoods>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: tflink, wwoods
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-09 19:58:10 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:

Description Adam Huffman 2013-07-04 16:15:10 UTC
Description of problem:

When I try to upgrade from F18 to F19, I see the following error on one machine:

fedup-cli -d --network 19
fedup INFO: /bin/fedup-cli starting at Thu Jul  4 17:10:01 2013
setting up repos...
fedup DEBUG: setup_downloader(version=19, repos=[])
fedup.yum INFO: FedupDownloader(version=19, cachedir=/var/tmp/fedora-upgrade)
fedup.yum DEBUG: prerepoconf.cache=0
fedup.yum INFO: checking repos
fedup.yum DEBUG: conf.cache=0
fedup.yum INFO: can't find valid repo metadata for Dropbox
fedup.yum INFO: repo adobe-linux-x86_64 seems OK
default-installrepo/metalink                                                                  |  26 kB  00:00:00     
fedup.yum INFO: can't find valid repo metadata for default-installrepo
fedup.yum INFO: repo fedora seems OK
fedup.yum INFO: repo google-chrome seems OK
fedup.yum INFO: repo google-talkplugin seems OK
fedup.yum INFO: repo rpmfusion-free seems OK
fedup.yum INFO: repo rpmfusion-free-updates seems OK
fedup.yum INFO: repo rpmfusion-nonfree seems OK
fedup.yum INFO: repo rpmfusion-nonfree-updates seems OK
fedup.yum INFO: repo updates seems OK
fedup.yum DEBUG: repos.cache=0
No upgrade available for the following repos: Dropbox
fedup INFO: disabled repos: Dropbox
Error: can't get boot images.
The installation repo isn't available.
You need to specify one with --instrepo.
fedup INFO: /bin/fedup-cli exiting at Thu Jul  4 17:10:03 2013

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

How reproducible:

Many times

Steps to Reproduce:
1. fedup --network 19

Actual results:

Error with default-installrepo

Expected results:

Additional info:

Comment 1 Will Woods 2013-10-09 19:58:10 UTC

*** This bug has been marked as a duplicate of bug 957364 ***