Hey BTW, I suspect this 'error' is due to upstream commit 97afc0351a96e0daa83964df33937967c75c644f which changed udevadm's behavior; previously it silently ignored errors writing to /sys/devices/*/uevent files, but now it logs error and returns error code. So this is likely not *actually* a new failure, it's just now being reported as failure by udevadm.
There is a similar 'failure' in bug 1845319 where (only on ppc64el) it gets ENODEV when writing to /sys/devices/vio/uevent, but I checked older releases and the vio device has been returning ENODEV for a long time; udevadm was just ignoring that before now.
Hey BTW, I suspect this 'error' is due to upstream commit 97afc0351a96e0d aa83964df339379 67c75c644f which changed udevadm's behavior; previously it silently ignored errors writing to /sys/devices/ */uevent files, but now it logs error and returns error code. So this is likely not *actually* a new failure, it's just now being reported as failure by udevadm.
There is a similar 'failure' in bug 1845319 where (only on ppc64el) it gets ENODEV when writing to /sys/devices/ vio/uevent, but I checked older releases and the vio device has been returning ENODEV for a long time; udevadm was just ignoring that before now.