It turns out the problem arises out of cargo cult programming on my part. The bang in KERNEL=="sd*[!0-9]" is what I copied out of stackexchange, and it's exactly what prevents the mount from matching. I suspected that early on, but ruled it out because when the device first connects it must connect as /dev/sda (as the partition table must be read before there can be an sda1). Now I'm figuring the sda gets replaced with sda1 before it reaches my custom rule.
In any case, the bug is not as I reported. I'm sorry this turned out to be a non-bug and I'm sorry I wasted your time Mr. Streetman. This can be closed. I may open a new bug report to improve the debug output, because we shouldn't have to work in the dark and guess about what the matching criteria is doing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890836 Title: udev rule read but "RUN" command is not executed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890836/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
