Bug 118682

Summary:	up2date -u is disastrous if autofs is upgraded while amd is running
Product:	[Fedora] Fedora	Reporter:	Alexandre Oliva <oliva>
Component:	autofs	Assignee:	Jeff Moyer <jmoyer>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	notting, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-06 20:46:37 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:
Bug Depends On:
Bug Blocks:	114961, 123268

Description Alexandre Oliva 2004-03-18 21:04:01 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124

Description of problem:
When rpm attempts to install the /net directory while amd controls
/net, rpm fails, leaving the database with a partial transaction
completed: packages that were yet to be installed in the same
transaction are gone, and packages that were already installed have
incorrect database entries for config files, so they generate a lot of
rpmnew/rpmorig in case you reinstall them.

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

How reproducible:
Always

Steps to Reproduce:
1.service amd start
2.up2date -u autofs

Actual Results:  There was a fatal RPM install error. The message was:
There was a rpm unpack error installing the package: autofs-4.1.0-8


Expected Results:  It should ideally install flawlessly, without
having to stop amd, but if stopping amd is the only way to avoid the
error, I guess we can live with it.

Additional info:

Comment 1 Nalin Dahyabhai 2004-03-31 00:20:16 UTC

Bill, should filesystem create /net?

Comment 2 Nalin Dahyabhai 2004-03-31 00:21:18 UTC

Details: prior to autofs 4.x, no package owned /net, so RPM attempts
to create the directory when autofs is installed.  If am-utils is
running, this fails.

Comment 3 Jeff Moyer 2004-03-31 01:06:04 UTC

Bill, Nalin and I discussed this quite a bit.  Having filesystem own
this directory would solve many headaches.

Comment 4 Bill Nottingham 2004-03-31 05:33:11 UTC

Does autofs use /net now?

Comment 5 Alexandre Oliva 2004-03-31 13:16:02 UTC

Yup.  And it even works.  And better than amd when referencing
/net/`uname -r`/, since it uses bind mounts instead of NFS over loopback.

Comment 6 Jeff Moyer 2004-08-30 15:10:15 UTC

The autofs package no longer owns /net.  This should fix the problems
described here.

Comment 7 Alexandre Oliva 2004-09-04 19:02:16 UTC

A recent rawhide update has shown that upgrading autofs was no
problem, but I no longer use amd, so I can't quite tell whether it's
actually fixed.  I'll take your word for it :-)  Thanks, feel free to
close as far as I'm concerned.