Bug 584623 - Bug 559844 in RHEL6
Bug 559844 in RHEL6
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: udev (Show other bugs)
x86_64 Linux
low Severity low
: rc
: ---
Assigned To: Harald Hoyer
Karel Volný
Depends On:
  Show dependency treegraph
Reported: 2010-04-22 00:31 EDT by Vadym Chepkov
Modified: 2010-11-10 16:49 EST (History)
3 users (show)

See Also:
Fixed In Version: udev-147-2.7.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-10 16:49:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vadym Chepkov 2010-04-22 00:31:46 EDT
It seems bug Bug 559844 is present in Redhat 6 beta

Retrigger failed udev eventstrigger: unrecognized option '--retry-failed'
Comment 2 RHEL Product and Program Management 2010-04-22 01:27:21 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 5 Gordan Bobic 2010-04-24 19:06:53 EDT
This is a regression. RHEL6b udev packages are version 147-2.6.el6. This is newer than the Fedora 12's 145-17.fc12. Fedora 12 packages don't exhibit this issue.
Comment 6 Harald Hoyer 2010-04-26 06:17:36 EDT
already fixed in udev >= 147-2.7.el6
Comment 7 Karel Volný 2010-10-06 09:26:04 EDT
the actual version (udev-147-2.29.el6) does not use the "--retry-failed" option

comparing with pre-fix version:

# diff udev-post /etc/init.d/udev-post 
<       /sbin/udevadm trigger --retry-failed
>       /sbin/udevadm trigger --type=failed
Comment 8 releng-rhel@redhat.com 2010-11-10 16:49:26 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

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