Red Hat Bugzilla – Bug 118682
up2date -u is disastrous if autofs is upgraded while amd is running
Last modified: 2007-11-30 17:10:38 EST
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):
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.
Bill, should filesystem create /net?
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.
Bill, Nalin and I discussed this quite a bit. Having filesystem own
this directory would solve many headaches.
Does autofs use /net now?
Yup. And it even works. And better than amd when referencing
/net/`uname -r`/, since it uses bind mounts instead of NFS over loopback.
The autofs package no longer owns /net. This should fix the problems
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.