0000064: Updating of kmod packages is broken on el5.5

(0000290)
pperry (administrator)
2010-05-18 17:47

This appears to be el5.5 related. Reverting /sbin/weak-modules to that in el5.4 fixes the issue.

(0000291)
pperry (administrator)
2010-05-18 17:47

$ diff weak-modules.el5.4 weak-modules.el5.5
117c117,118
< if [ "xen" == "`echo $kernel|sed -nre 's:^.*(xen)$:\1:p'`" ];
---
> if [ "xen" == "`echo $kernel|sed -nre 's:^.*(xen)$:\1:p'`" \
> -a "(" -e /proc/xen/xsd_kva -o ! -d /proc/xen ")" ];
354a356
> orig_module="`readlink $weak_module`"
362a365
> [ "$module" != "$orig_module" ] || continue

(0000292)
pperry (administrator)
2010-05-18 18:20

Bug filed upstream:

https://bugzilla.redhat.com/show_bug.cgi?id=593504 [^]

(0000298)
burakkucat (administrator)
2010-06-03 04:28

As per Ned's Comment 11 upstream (https://bugzilla.redhat.com/show_bug.cgi?id=593504), [^] this issue can be resolved by a modification to the kmodtool file, as distributed by Red Hat.

A revision of his patch is attached.

(0000300)
pperry (administrator)
2010-06-12 04:57

Users should please see here for latest information and a workaround:

http://elrepo.org/tiki/Update [^]

(0000325)
pperry (administrator)
2010-07-29 23:27

Looks like upstream intend to revert the original patch that breaks updating:

https://bugzilla.redhat.com/show_bug.cgi?id=477089 [^]

(0000326)
pperry (administrator)
2010-07-29 23:29

As a workaround, we have built module-init-tools-3.3-0.pre3.1.60.el5.elrepo with the patch reverted (now in both elrepo and elrepo-testing), and will add:

Conflicts: module-init-tools-3.3-0.pre3.1.60.el5

to updated packages which will allow the newer version of module-init-tools to be pulled as a dependency.

(0000328)
pperry (administrator)
2010-07-30 07:19

The Conflicts line would get added to new kmod packages (in kmodtool) so our updated module-init-tools package is pulled in as a dependency (to automatically replace the older conflicting package).

Because module-init-tools gets updated first, the fixed (reverted) weak-modules acript is now used to update the kmod package, and thus the update works (weak links are present and correct).

(0000329)
pperry (administrator)
2010-08-01 12:02

Just to try to clarify further...

Yum will try to resolve a Conflict in much the same way as it would a Requires by seeking to update the conflicting package if a newer version is available.

So if a user does:

yum update kmod-foo

and kmod-foo conflicts with the currently installed version of module-init-tools, then yum will seek to first update module-init-tools to a newer version to resolve the conflict. This is the case for the current version of module-init-tools in el5.5

Users still running an older version of module-init-tools, in el5.4 or before, are unaffected by the bug so they can continue with their current version of module-init-tools. If we were to use a Requires > 3.3-0.pre3.1.60.el5, then users still running el5.4 and before would unnecessarily receive an update from el5.5 which might potentially cause other issues.

One point to note is that when using the priorities plugin to protect base packages, the elrepo repository will need to be allowed to replace packages from base/updates in order to update module-init-tools otherwise the yum transaction will fail with an unresolved dependency as yum is unable to resolve the conflict.

Issue History
Date Modified	Username	Field	Change
2010-05-18 17:37	pperry	New Issue
2010-05-18 17:37	pperry	Status	new => assigned
2010-05-18 17:37	pperry	Assigned To	=> stindall
2010-05-18 17:47	pperry	Note Added: 0000290
2010-05-18 17:47	pperry	Note Added: 0000291
2010-05-18 17:49	pperry	Assigned To	stindall => burakkucat
2010-05-18 18:20	pperry	Note Added: 0000292
2010-06-03 04:28	burakkucat	Note Added: 0000298
2010-06-03 04:29	burakkucat	File Added: kmodtool.patch
2010-06-12 04:57	pperry	Note Added: 0000300
2010-07-29 23:27	pperry	Note Added: 0000325
2010-07-29 23:29	pperry	Note Added: 0000326
2010-07-30 07:19	pperry	Note Added: 0000328
2010-08-01 12:02	pperry	Note Added: 0000329
2010-08-17 08:45	burakkucat	Status	assigned => resolved
2010-08-17 08:45	burakkucat	Resolution	open => fixed

Notes
(0000290) pperry (administrator) 2010-05-18 17:47	This appears to be el5.5 related. Reverting /sbin/weak-modules to that in el5.4 fixes the issue.

(0000291) pperry (administrator) 2010-05-18 17:47	$ diff weak-modules.el5.4 weak-modules.el5.5 117c117,118 < if [ "xen" == "`echo $kernel\|sed -nre 's:^.(xen)$:\1:p'`" ]; --- > if [ "xen" == "`echo $kernel\|sed -nre 's:^.(xen)$:\1:p'`" \ > -a "(" -e /proc/xen/xsd_kva -o ! -d /proc/xen ")" ]; 354a356 > orig_module="`readlink $weak_module`" 362a365 > [ "$module" != "$orig_module" ] \|\| continue

(0000292) pperry (administrator) 2010-05-18 18:20	Bug filed upstream: https://bugzilla.redhat.com/show_bug.cgi?id=593504 [^]

(0000298) burakkucat (administrator) 2010-06-03 04:28	As per Ned's Comment 11 upstream (https://bugzilla.redhat.com/show_bug.cgi?id=593504), [^] this issue can be resolved by a modification to the kmodtool file, as distributed by Red Hat. A revision of his patch is attached.

(0000300) pperry (administrator) 2010-06-12 04:57	Users should please see here for latest information and a workaround: http://elrepo.org/tiki/Update [^]

(0000325) pperry (administrator) 2010-07-29 23:27	Looks like upstream intend to revert the original patch that breaks updating: https://bugzilla.redhat.com/show_bug.cgi?id=477089 [^]

(0000326) pperry (administrator) 2010-07-29 23:29	As a workaround, we have built module-init-tools-3.3-0.pre3.1.60.el5.elrepo with the patch reverted (now in both elrepo and elrepo-testing), and will add: Conflicts: module-init-tools-3.3-0.pre3.1.60.el5 to updated packages which will allow the newer version of module-init-tools to be pulled as a dependency.

(0000328) pperry (administrator) 2010-07-30 07:19	The Conflicts line would get added to new kmod packages (in kmodtool) so our updated module-init-tools package is pulled in as a dependency (to automatically replace the older conflicting package). Because module-init-tools gets updated first, the fixed (reverted) weak-modules acript is now used to update the kmod package, and thus the update works (weak links are present and correct).

(0000329) pperry (administrator) 2010-08-01 12:02	Just to try to clarify further... Yum will try to resolve a Conflict in much the same way as it would a Requires by seeking to update the conflicting package if a newer version is available. So if a user does: yum update kmod-foo and kmod-foo conflicts with the currently installed version of module-init-tools, then yum will seek to first update module-init-tools to a newer version to resolve the conflict. This is the case for the current version of module-init-tools in el5.5 Users still running an older version of module-init-tools, in el5.4 or before, are unaffected by the bug so they can continue with their current version of module-init-tools. If we were to use a Requires > 3.3-0.pre3.1.60.el5, then users still running el5.4 and before would unnecessarily receive an update from el5.5 which might potentially cause other issues. One point to note is that when using the priorities plugin to protect base packages, the elrepo repository will need to be allowed to replace packages from base/updates in order to update module-init-tools otherwise the yum transaction will fail with an unresolved dependency as yum is unable to resolve the conflict.

Relationships