SYSTEMD_WANTS does not start the Dell iSM service when the idrac-usb-nic is enabled/disabled multiple times
Issue
- idrac Service Module (iSM) is a daemon service which is supposed to be started and running when the 'idrac' usb-nic interface is enabled from the idrac web-page.
- However, this is not happening when usb-nic is enabled/disabled multiple times from iDRAC web page.
$ cat /usr/lib/udev/rules.d/95-iSM-usbnic-systemd.rules
# Dell USBNIC Device
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", ATTR{idProduct}=="a102", ATTR{manufacturer}=="Dell(TM)", ACTION=="add", RUN+="/bin/touch /opt/dell/srvadmin/iSM/etc/ini/usbnicconfig.ini"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", ATTR{idProduct}=="a102", ATTR{manufacturer}=="Dell(TM)", ACTION=="add", PROGRAM="/bin/systemctl is-enabled dcismeng.service", RESULT=="enabled", TAG+="systemd", ENV{SYSTEMD_WANTS}="dcismeng.service"
-
Expectation is when usb-nic is enabled through iDRAC web page,
dcismeng.servicestarts running. But currently, it does not start thedcismeng.servicewhen we try enable/disable usb-nic multiple times. -
Working fine with RHEL7 but failing with RHEL8 onward
Environment
- Red Hat Enterprise Linux 8
- udev
- Dell PowerEdge server running Dell iSM.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.