Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
we've got a special usb device, and when we plug/unplug we write our own rules which is working properly except one thing. during the boot this lines in udev:
ACTION=="remove", DEVLINKS=="/dev/foo_ups", RUN+="/usr/libexec/foo/liebert-udev"
we always got this during boot:
Starting udev: udevd[476]: unknown key 'DEVLINKS' in /etc/udev/rules.d/10-foo.rules:11
since there is no other way during remove a usb-serial adapter then DEVLINKS we can't find other ways to write the rules. and anyway why it's a problem if it's work properly after boot.
it's not working while the original was working:-(
anyway it's a simple serial to usb converter so you can also try. the add line was:
ACTION=="add", KERNEL=="ttyUSB[0-9]", SYSFS{idVendor}=="058f", SYSFS{idProduct}=="9720", SYMLINK+="foo_ups", RUN+="/usr/libexec/foo/liebert-udev"
the problem is that udev don't give back the SYSFS and SYMLINK parameter in case of remove.
(In reply to comment #4)
> it's not working while the original was working:-(
> anyway it's a simple serial to usb converter so you can also try. the add line
> was:
> ACTION=="add", KERNEL=="ttyUSB[0-9]", SYSFS{idVendor}=="058f",
> SYSFS{idProduct}=="9720", SYMLINK+="foo_ups",
> RUN+="/usr/libexec/foo/liebert-udev"
>
> the problem is that udev don't give back the SYSFS and SYMLINK parameter in
> case of remove.
Yes, because the SYMLINK is removed, there is no more sysfs entry anymore, because the device already disappeared.
it's still not working:-(
anyway the original problem was that the system gives an error during boot.
and the original rule is working:-)
but if you've any other tip we can try it...
ok the exact situatuion is that your solution working on rhel-6, but not on rhel-5, but we find the solution:
http://comments.gmane.org/gmane.linux.hotplug.devel/14254
after we add this line:
ACTION=="remove", ENV{REMOVE_CMD}!="", RUN+="$env{REMOVE_CMD}"
it's working on both rhel-6 and rhel-5:-)