Bug 435244

Summary:	yum database not updated on upgrade from f7 to f8
Product:	[Fedora] Fedora	Reporter:	Douglas Campbell <doug.campbell>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-06-04 14:00:17 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:

Description Douglas Campbell 2008-02-28 06:34:51 UTC

Description of problem:
Upon upgrade install from f7 to f8 using full f8 dvd, the yum repository
directory in /etc/yum.repos.d remain unchanged and continue to reference the
fedora 7 directories.  The update daemon indicates that over 900 updates are
available.  pup hangs if run.

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


How reproducible:


Steps to Reproduce:
1. install fc7.
2. upgrade install fc8.
3. login as root
  
Actual results:
pup hangs while attempting to utilize f7 directories to update f8 upgrade
install, while update daemon gives popup indicating over 900 updates available.

Expected results:
pup shows small number or zero upgrades available, and installs them if I
request them.

Additional info:
livna configuration was present, but behavior persisted after I uninstalled all
livna stuff and removed their configuration from yum.repos.d

Comment 1 Douglas Campbell 2008-02-29 01:34:39 UTC

Problem apparently occured when livna access added.  *.rpmnew files created upon
update for fedora.repo and fedora-development.repo.  After moving out old *.repo
files and renaming *.repo.rpmnew files to take their place, pup/yum began
working again.

The hang no longer occurs.

Comment 2 Andy Lindeberg 2008-06-04 14:00:17 UTC

Closing as this problem stopped occuring, but please let us know if you
encounter it in Fedora 9.