Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 229924 - fedorakmod plugin find no "epoch" property when module is updated sans kernel update
Summary: fedorakmod plugin find no "epoch" property when module is updated sans kernel...
Status: CLOSED DUPLICATE of bug 229917
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 6
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
: 229966 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-24 14:36 UTC by Peter Trenholme
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-02-27 07:46:00 UTC

Attachments (Terms of Use)

Description Peter Trenholme 2007-02-24 14:36:09 UTC
Description of problem:
The fedorakmod yum plugin aborts when the kmod (for the existing, installed
kernel module) is updated but the kernel itself is not updated.

The error message is that the "epoch" property is not defined for the object.

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

How reproducible:
Every time

Steps to Reproduce:
1. Run "yum upgrade" when the kmd has been upgraded for the existing kernel.
Actual results:
Abort: "epoch property not defined"

Expected results:
Module replaced with new module

Additional info:
1) When plugins are disabled, "yum upgrade" runs to completion without any problem.
2) The problem also causes (of course) "yumex" to abort.

Comment 1 Tim Lauridsen 2007-02-26 11:31:46 UTC
*** Bug 229966 has been marked as a duplicate of this bug. ***

Comment 2 Tim Lauridsen 2007-02-27 07:46:00 UTC

*** This bug has been marked as a duplicate of 229917 ***

Note You need to log in before you can comment on or make changes to this bug.