udisks tries to create degraded/sync_action watch files for mdadm IMSM containers

[John Center]

I'm running Ubuntu 14.04 with the 3.17.5 kernel. I have 3 IMSM RAID1
arrays set up & I noticed the following syslog messages:

Dec 15 09:49:06 mariposa udisksd[3255]: udisks daemon version 2.1.3 starting
Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md123/md/sync_action: No such file or directory (g-file-error-quark, 4)
Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md123/md/degraded: No such file or directory (g-file-error-quark, 4)
Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md125/md/sync_action: No such file or directory (g-file-error-quark, 4)
Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md125/md/degraded: No such file or directory (g-file-error-quark, 4)
Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md127/md/sync_action: No such file or directory (g-file-error-quark, 4)
Dec 15 09:49:06 mariposa udisksd[3255]: Error creating watch for file /sys/devices/virtual/block/md127/md/degraded: No such file or directory (g-file-error-quark, 4)
Dec 15 09:49:06 mariposa dbus[1230]: [system] Successfully activated service 'org.freedesktop.UDisks2'

The files (degraded,sync_action) don't exist in the container (md127, etc.) directories, but do exist in the array (md126, etc.) directories themselves. I posted this to the linux-raid list & as I suspected, was told those files are not created in the container directories. I recently ran software updates, but udisks was not one of the packages patched.