Errors in messages.log on bootstrap: udevd-work[11436]: error opening ATTR{/sys/devices/virtual/block/md0/queue/iosched/quantum} for writing: No such file or directory

[Anastasia Palkina]

"build_id": "2015-03-22_22-54-44",
"ostf_sha": "b4d284e9364e30bf5162975c2ba0be6ca0f14ebd",
"build_number": "216",
"release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-03-22_22-54-44", "ostf_sha": "b4d284e9364e30bf5162975c2ba0be6ca0f14ebd", "build_number": "216", "api": "1.0", "nailgun_sha": "51974b50c3961be3ed0fdc7859570db2eeb83e9c", "production": "docker", "python-fuelclient_sha": "b223dcaf5fdad2f714cd245958fefe03995d6207", "astute_sha": "4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "f52e4442df55a2b62637a2cf4038a24ba6f37b6f", "fuellib_sha": "a636c680e3c7d8cc66ed3e03645f38250beb8970"}}},
"auth_required": true,
"api": "1.0",
"nailgun_sha": "51974b50c3961be3ed0fdc7859570db2eeb83e9c",
"production": "docker",
"python-fuelclient_sha": "b223dcaf5fdad2f714cd245958fefe03995d6207",
 "astute_sha": "4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9",
"feature_groups": ["mirantis"],
"release": "6.1",
"fuelmain_sha": "f52e4442df55a2b62637a2cf4038a24ba6f37b6f",
"fuellib_sha": "a636c680e3c7d8cc66ed3e03645f38250beb8970"

1. Create new environment (CentOS)
2. Choose Neutron, GRE
3. Choose Murano
4. Add 1 controller, 1 compute, 1 cinder
5. Start deployment. It was successful
6. Start OSTF tests. It was successful
7. But there are errors in bootstrap/messages.log on controller (node-6):

2015-03-24 11:34:40 ERR

udevd-work[11436]: error opening ATTR{/sys/devices/virtual/block/md0/queue/iosched/quantum} for writing: No such file or directory

2015-03-24 11:34:40 ERR

udevd-work[11436]: error opening ATTR{/sys/devices/virtual/block/md0/queue/iosched/slice_idle} for writing: No such file or directory

[Stanislaw Bogatkin (sbogatkin)]

Cannot reproduce this on last master ISO #227.

[Anastasia Palkina (apalkina)]

Reproduced on ISO #234

"build_id": "2015-03-26_22-54-44", "ostf_sha": "a4cf5f218c6aea98105b10c97a4aed8115c15867", "build_number": "234", "release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-03-26_22-54-44", "ostf_sha": "a4cf5f218c6aea98105b10c97a4aed8115c15867", "build_number": "234", "api": "1.0", "nailgun_sha": "b163f6fc77d6639aaffd9dd992e1ad96951c3bbf", "production": "docker", "python-fuelclient_sha": "e5e8389d8d481561a4d7107a99daae07c6ec5177", "astute_sha": "3f1ece0318e5e93eaf48802fefabf512ca1dce40", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "320b5f46fc1b2798f9e86ed7df51d3bda1686c10", "fuellib_sha": "9c7716bc2ce6075065d7d9dcf96f4c94662c0b56"}}}, "auth_required": true, "api": "1.0", "nailgun_sha": "b163f6fc77d6639aaffd9dd992e1ad96951c3bbf", "production": "docker", "python-fuelclient_sha": "e5e8389d8d481561a4d7107a99daae07c6ec5177", "astute_sha": "3f1ece0318e5e93eaf48802fefabf512ca1dce40", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "320b5f46fc1b2798f9e86ed7df51d3bda1686c10", "fuellib_sha": "9c7716bc2ce6075065d7d9dcf96f4c94662c0b56"

1. Create new environment (CentOS)
2. Choose Nova-network, vlan
3. Choose Ceph for images
4. Choose Sahara, Ceilometer
5. Add 1 controller+ceph, 1 compute+ceph, 1 cinder+ceph, 2 mongo
6. Start deployment. It was successful
7. Start OSTF tests. it was successful
8. There are errors in messages.log again on controller (node-1):

[root@fuel ~]# less /var/log/docker-logs/remote/node-1.domain.tld/bootstrap/messages.log | grep error
2015-03-27T11:30:15.768671+00:00 err: udevd-work[8161]: error opening ATTR{/sys/devices/virtual/block/md0/queue/iosched/slice_idle} for writing: No such file or directory
2015-03-27T11:30:15.768671+00:00 err: udevd-work[8161]: error opening ATTR{/sys/devices/virtual/block/md0/queue/iosched/quantum} for writing: No such file or directory

[Stanislaw Bogatkin (sbogatkin)]

So, it is not problem on node itself, it is a problem on bootstrap. Then it should not be a 'high'.

[Stanislaw Bogatkin (sbogatkin)]

Problem is that udev rules in bootstrap blacklisted iosched rules, that lead to such errors.

[Stanislaw Bogatkin (sbogatkin)]

After a little talk with dev guys we setted that this bug should be setted as "Won't fix", cause we deliberately hiding udev rules for small amount of time, so such errors is expected behavior and they don't affect anything at all.