Bug 587145

Summary:	libvolume_id1 removed during "zypper dup", loosing nfs mount during upgrade
Product:	[openSUSE] openSUSE 11.2	Reporter:	Forgotten User E4aj6OYf6m <forgotten_E4aj6OYf6m>
Component:	Update Problems	Assignee:	E-mail List <zypp-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P3 - Medium	CC:	forgotten_E4aj6OYf6m, ma
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User E4aj6OYf6m 2010-03-10 17:32:34 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8

http://de.opensuse.org/Upgrade
following the upgrade path, during "zypper dup" one of the first rpms being deleted is libvolume_id1. Shortly after, install stops because "mount" can't mount the nfs repo anymore.

So there should be some prevention to delete that package too early. Maybe, for a "zypper dup", package *deletion* should be done *after* install, so that nothing happens?

It would be great if zypper dup works correctly in 11.3, saving lots of time for every machine.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Kay Sievers 2010-03-11 12:23:04 UTC

Sounds like an update problem, nothing I udev could solve.

Comment 2 Jan Kupec 2010-03-12 15:26:16 UTC

Thanx for reporting! This is an interesting case. Zypp guys, any idea how to solve it?

Anyway, there is probably an easy workaround, and the English version of the wiki actually suggests it: tell zypper to download the packages first. See http://en.opensuse.org/Upgrade#Command_line and note 'zypper dup -d'. Can you please try?

This might even be the only solution needed, provided you have enough free disk space to download the packages first.

You can also configure zypp to always prefer this download/install mode by setting commit.downloadMode = DownloadInAdvance in /etc/zypp/zypp.conf.

Comment 3 Michael Andres 2010-03-12 16:12:49 UTC

DownloadInHeaps (or DownloadInAdvance) is the best approach. 

An improved install order (for 11.3) may help, but downloading the required packages before starting the install is the safest approach when doing a system update while the system is running.

Comment 4 Forgotten User E4aj6OYf6m 2010-03-13 07:04:46 UTC

Agreed. Wouldn't it also help to mount all repositories that will be needed just before starting the upgrade? An already mounted repo is no problem, I had NFS shares that were still accessible, you just can't mount nfs anymore.

So simply mount all repos, then start the upgrade, would have helped here. Maybe that's a simple fix that could save the need to DownloadInAdvance. I had everything "local" accessible via NFS, so didn't believe to need to DownloadInAdvance.

Comment 5 Michael Andres 2010-03-15 10:52:44 UTC

Yes, mounting required media in advance could improve your case. I put it on the 11.3 wishlist. As we want to restructure the commit workflow anyway, it might be easily doable.