Bug 752724

Summary: Update (14->16) fails after reboot with "error: cannot open Packages database"
Product: [Fedora] Fedora Reporter: Michael Styer <michael>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: anaconda-maint-list, dekela, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-15 15:02:32 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:
Attachments:
Description Flags
Log files none

Description Michael Styer 2011-11-10 08:55:52 UTC 
Description of problem:

I'm trying to upgrade a Fedora 14 system to 16. I've run preupgrade, and it has installed the "Upgrade to Fedora 16 (Verne)" boot option in my grub config.

When I boot that option, it starts the graphical installer, but after "examining storage devices", it gives me an error dialog saying "The root for the previously installed system was not found.". After I click OK on that dialog, I'm returned to a blue screen with the following lines of text at the bottom:

  Running Anaconda 16.15, the Fedora system installer - please wait
  00:17:42 Starting graphical installation
  error: cannot open Packages database in /mnt/sysimage/var/lib/rpm

I have tried running "yum clean all" in F14, but that made no difference.

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

Anaconda 16.15
Fedora 14 to 16 upgrade

How reproducible:

Mmm, not sure. It happens every time I boot into that option, but I don't know whether it would be reproducible on a different system.

Steps to Reproduce:
1. Boot into "Upgrade to Fedora 16" boot option
  
Actual results:

Error message described above.

Expected results:

Anaconda installation completes.

Additional info:

I'd be very happy to provide more info, logs, etc. Just tell me what would be helpful and where to find it and I'll attach them to the ticket.
Comment 1 dekela 2011-11-10 12:52:49 UTC 
I am having this issue as well.
Upgrading from f15 to f16 using preupgrade.
Comment 2 Chris Lumens 2011-11-10 14:49:37 UTC 
/tmp/anaconda.log, /tmp/syslog, and /tmp/storage.log from the installation environment would help.  Thanks.
Comment 3 Michael Styer 2011-11-10 17:28:01 UTC 
You mean from the Fedora 14 (or 15, in Dekel's case) environment, right? I'll get those tonight.
Comment 4 Michael Styer 2011-11-11 06:02:12 UTC 
Created attachment 532980 [details]
Log files

I didn't have /tmp/syslog or /tmp/anaconda.log. I did have, in /var/log:
  * anaconda.log
  * anaconda.storage.log
  * anaconda.yum.log
  * anaconda.syslog
  * anaconda.xlog
  * anaconda.program.log. 

I've attached those. Hope they're helpful; happy to provide any more information needed.
Comment 5 Chris Lumens 2011-11-13 01:04:59 UTC 
Actually, I meant from the installation environment.  However, I think a more important piece of information is:  Do you have /var on a separate partition or logical volume?
Comment 6 Michael Styer 2011-11-15 05:24:11 UTC 
Aha. OK, I haven't figured out how to get to the installation environment -- the installation fails with the error above, and then I don't have console access, as far as I can tell. Is there another way I can get log files from the installation environment? I don't actually know where the installation environment is, but if you point me to it I'll be happy to look.

Anyway, yes, I have /var on a separate logical volume:


$ mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/mapper/VolGroup00-LogVol02 on /home type ext3 (rw)
/dev/mapper/VolGroup00-LogVol04 on /tmp type ext3 (rw)
/dev/mapper/VolGroup00-LogVol05 on /opt type ext3 (rw)
/dev/mapper/VolGroup00-LogVol01 on /usr type ext3 (rw)
/dev/sda3 on /boot type ext3 (rw)
/dev/mapper/VolGroup00-LogVol03 on /var type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

Is that a problem?
Comment 7 Chris Lumens 2011-11-15 15:02:32 UTC 
Yeah, there's a bug about that in F16 unfortunately.  You'll need to use the updates image referenced in the bug I'm marking this one as a dupe of.

*** This bug has been marked as a duplicate of bug 748119 ***
Comment 8 Michael Styer 2011-11-15 17:16:42 UTC 
OK, sounds like that's it. Thanks for the info; I'll try the image in the other bug.