# Udev rules not triggering after reboot

**URL:** https://forums.suse.com/t/udev-rules-not-triggering-after-reboot/16054
**Category:** RancherOS
**Created:** [December 10, 2019, 2:32am UTC](https://forums.suse.com/t/udev-rules-not-triggering-after-reboot/16054 "2019-12-10T02:32:01Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![manutenfruits](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/manutenfruits/32/5885_2.png) [@manutenfruits](https://forums.suse.com/u/manutenfruits)
#### Post date: [December 10, 2019, 2:32am UTC](https://forums.suse.com/t/udev-rules-not-triggering-after-reboot/16054/1 "2019-12-10T02:32:01Z")

</div>

I have the following in my config:

```
write_files:
- path: /etc/udev/rules.d/99-z-wave-stick.rules
  container: udev
  permissions: "0644"
  owner: root
  content: |
    SUBSYSTEM=="tty", GROUP="dialout", ATTRS{interface}=="HubZ Z-Wave Com Port", SYMLINK+="zwave"
    SUBSYSTEM=="tty", GROUP="dialout", ATTRS{interface}=="HubZ ZigBee Com Port", SYMLINK+="zigbee"

```

If I connect the USB, it works, but whenever I reboot the Rancher OS host, the symlinks are not created. If I do `sudo system-docker exec -it udev bash` and inside of the container run `udevadm trigger` the symlinks are created instantly.

How can I make this happen magically across reboots? Did I miss something?

---

<div class="post-metadata">

### Author: ![manutenfruits](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/manutenfruits/32/5885_2.png) [@manutenfruits](https://forums.suse.com/u/manutenfruits)
#### Post date: [December 16, 2019, 3:11pm UTC](https://forums.suse.com/t/udev-rules-not-triggering-after-reboot/16054/2 "2019-12-16T15:11:57Z")

</div>

Bump! I don’t know what other forums to try ☹
