Bug 175941

Summary:	kernel-devel removes inintab (.rpmsave) and initscripts doesn't replace it during update
Product:	[Fedora] Fedora	Reporter:	Peter Quiring <pquiring>
Component:	yum	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	nobody+pnasrat, notting, sundaram
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:	2006-02-20 11:24:42 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 Peter Quiring 2005-12-16 16:28:39 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051211 Fedora/1.5-1.1 Firefox/1.5

Description of problem:
When running 'yum update' today, I noticed that during kernel-devel package update it renamed inittab and adjtime to .rpmsave files.  Then the initscripts was removed and then updated but these files were not put back.  Not sure what would happen if I rebooted but I think I know what would happen (boot failure).

Note : There is currently a break in yum so I did a partial update (yum update "i*" "k*" "s*"):

Here is a dump of yum output:

Running Transaction
  Updating  : system-config-date           ####################### [ 1/12]
  Installing: kernel-devel                 ####################### [ 2/12]
warning: /etc/inittab saved as /etc/inittab.rpmsave
warning: /etc/adjtime saved as /etc/adjtime.rpmsave
  Removing  : initscripts                  ####################### [ 3/12]
  Updating  : selinux-policy-targeted      ####################### [ 4/12]
  Updating  : sysklogd                     ####################### [ 5/12]
  Updating  : initscripts                  ####################### [ 6/12]
fgrep: /etc/inittab: No such file or directory
  Installing: kernel                       ####################### [ 7/12]
  Cleanup   : kernel                       ####################### [ 8/12]
  Cleanup   : selinux-policy-targeted      ####################### [ 9/12]
  Cleanup   : sysklogd                     ####################### [10/12]
  Cleanup   : kernel-devel                 ####################### [11/12]
  Cleanup   : system-config-date           ####################### [12/12]

Removed: kernel.i686 0:2.6.14-1.1765_FC5 kernel-devel.i686 0:2.6.14-1.1765_FC5
Installed: kernel.i686 0:2.6.14-1.1767_FC5 kernel-devel.i686 0:2.6.14-1.1767_FC5
Updated: initscripts.i386 0:8.19-1 selinux-policy-targeted.noarch 0:2.1.6-4 sysklogd.i386 0:1.4.1-34 system-config-date.noarch 0:1.7.99.11-1
Complete!


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

How reproducible:
Didn't try

Steps to Reproduce:
1.yum update
2.
3.
  

Actual Results:  /etc/inittab and adjtime renamed to .rpmsave and no new files to replace them.

Expected Results:  Create new files or leave old ones there.

Additional info:

Comment 1 Bill Nottingham 2005-12-17 07:29:34 UTC

This is a yum issue - it should not be running remove before install.

Comment 2 Seth Vidal 2005-12-17 13:37:21 UTC

Yum is using rpm's ordering mechanism, not its own.


You'll note in the transaction output it lists update and installs first and
cleanups last.

cleanups == removal.

Comment 3 Seth Vidal 2005-12-17 17:51:23 UTC

whoops - I missed the removal of initscripts in the output.

Still - yum is just using ts.order() for the ordering.

Paul? Anything change in transaction ordering?

Comment 4 Paul Nasrat 2005-12-18 12:05:46 UTC

No I haven't changed yum's ordering code.

Comment 5 Rahul Sundaram 2006-02-20 11:24:42 UTC


These bugs are being closed since a large number of updates have been released
after the FC5 test1 and test2 releases. Kindly update your system by running yum
update as root user or try out the third and final test version of FC5 being
released in a short while and verify if the bugs are still present on the system
.Reopen or file new bug reports as appropriate after confirming the presence of
this issue. Thanks