[IBP] get rid of 'udevd: can not read' scary error messages

[Alexander Gordeev]

Currently, our fix for 'device busy' issue blacklists udev rules bringing those type of error messages to udev logs.

STR: provision a node with multiple cpu onboard.
Expected results: no various 'udevd: can not read' error messages could be found at /var/log/messages on nodes.
Actual: there're few 'udevd: can not read' messages. Amount of these warnings and relation to particular files may vary from time to time due to asynchronous udev's nature.

[Alexander Gordeev (a-gordeev)]

could be fixed with ease just by writing ether emply line or comment sign '#' to rule. Rule should be non-empty.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/170577

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/170577
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=6ef3d6c9d7c3fd6733fbc4b635891a8f60cadc5f
Submitter: Jenkins
Branch: master

commit 6ef3d6c9d7c3fd6733fbc4b635891a8f60cadc5f
Author: Alexander Gordeev <email address hidden>
Date: Mon Apr 6 19:33:48 2015 +0300

    [IBP] fix scary udev errors

    Udev was moaning about its zero-sized rule files.
    Adding a simple empty rule will help to avoid all error messages
    such as 'udevd: can not read'.

    Change-Id: I7777e1e1f17491cdc3aa91d538c23e0c5a4ab849
    Closes-Bug: #1422717

[Alexander Gordeev (a-gordeev)]

I've checked on scale lab; the amount of lines with errors is floating between 20-30. Looks like async nature of udev strikes back again. Maybe sleep for a few seconds and 'settle' prior partitioning should help, i don't know.

for x in `seq 2 254`; do grep udevd /var/log/docker-logs/remote/10.20.1.${x}/bootstrap/messages.log | grep 'can not' -c; done
29
29
29
26
30
29
27
27
29
28
28
29
29
28
29
29
25
25
28
28
30
28
29
27
27
25
29
29
29
29
29
30
28
27
28
31
27
29
29
30
28
27
28
29
29
28
28
28
28
29
30
28
25
28
27
33
29
28
29
27
29
29
29
30
29
31
28
29
29
34
25
28
25
28
27
25
28
27
0
29
26
30
29
27
28
29
28
28
29
28
30
29
28
29
29
30
28
30
28
30
28
27
29
28
27
29
26
28
28
29
26
28
28
29
28
30
28
29
29
27
28
25
29
27
28
28
29
25
29
30
27
29
30
28
29
33
28
28
29
28
29
28
29
0
25
28
28
28
30
0
28
30
26
29
27
28
28
27
28
29
32
28
29
25
28
30
33
28
28
29
29
29
29
28
29
25
29
30
27
28
29
25
25
28
29
28
30
25
29
28
28
29
30
27
33
29
30
28
31
29
27
28
27
29
27
25
28
28
27
25
29
29
30
29
28
30
29
29
28
29
27
28
30
28
26
31
27
27
29
29
27
25
28
27
34
28
28
25
29
27
25
28
33
29
26
27
29
28
29
32
28
29
29

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/176742

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/204149

[Alexander Gordeev (a-gordeev)]

Not sure, but it may be fixed in udev-151
http://git.kernel.org/cgit/linux/hotplug/udev.git/tree/ChangeLog?id=HEAD#n1273

[OpenStack Infra (hudson-openstack)]

Change abandoned by Aleksandr Gordeev (<email address hidden>) on branch: master
Review: https://review.openstack.org/176742
Reason: fix is available for fuel-agent repo

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/204149
Committed: https://git.openstack.org/cgit/stackforge/fuel-agent/commit/?id=81ff5ad15d0e47bb464fa9f9ce24263463382d7a
Submitter: Jenkins
Branch: master

commit 81ff5ad15d0e47bb464fa9f9ce24263463382d7a
Author: Alexander Gordeev <email address hidden>
Date: Tue Jul 21 19:12:59 2015 +0300

    fix 'udevd: can not read' warnings

    Those warnings appear when fuel-agent performs udev rules
    blacklisting.

    Adding a syncing with udev via 'udevadm settle' to the lines which
    actually manipulate with these rules, totally eliminates those scary
    warnings.

    Change-Id: I9e528f948f83d97e9cf084e3b2c3250eef518c5e
    Closes-Bug: #1422717

[Vitaly Sedelnik (vsedelnik)]

Won't Fix for 6.0-updates because of Medium importance

[Ksenia Svechnikova (kdemina)]

MOS 7.0, build 301

Verify on HW lab with 8 nodes:
[root@fuel-lab5-mos6 ~]# for x in `seq 0 7`; do grep udevd /var/log/docker-logs/remote/172.16.40.7${x}/bootstrap/messages.log | grep 'can not' -c; done
0
0
0
0
0
0
0
0