maas-ipmi-autodetect-tool fails to detect IPMI on midway

[Impact]

Machines successfully enlist, but IPMI autodetection fails. This causes MAAS to fail to have any power control parameters for enlisted nodes, which means that manual intervention is required and MAAS fails to "Just Work".

[Upstream Fix]

Revision 1717 in trunk.

[Development Fix]

Pending upstream release/snapshot.

[Stable Fix]

A minimal "import glob" patch should work here.

[Regression Potential]

"glob" is a standard Python library function, and there should be no impact in importing it. If some change to maas-ipmi-autodetect-tool were to cause a regression, it would be that the tool would fail, thus causing the power parameters to fail to set in MAAS upon enlistment. This is the use case being fixed by this SRU.

[Original Description]

maas 1.4+bzr1693+dfsg-0ubuntu2.2 on Saucy

It appears to me that this would affect Highbank, Midway and anything else that does local IPMI detection using this snippet on Saucy.

During enlistment:

Traceback (most recent call last):
  File "/tmp/sh.6FtsiE/bin/maas-ipmi-autodetect-tool", line 44, in <module>
    main()
  File "/tmp/sh.6FtsiE/bin/maas-ipmi-autodetect-tool", line 33, in main
    (status, ipmi_version) = detect_ipmi()
  File "/tmp/sh.6FtsiE/bin/maas-ipmi-autodetect-tool", line 18, in detect_ipmi
    found = glob.glob("/dev/ipmi[0-9]")
NameError: global name 'glob' is not defined

Looks like this was fixed in upstream trunk in revision 1717. This may need a Saucy SRU.

Workaround: add "import glob" to /etc/maas/templates/commissioning-user-data/snippets/maas_ipmi_autodetect_tool.py.