Unittests leaving a dirty /tmp directory

[Lucas Alvares Gomes]

When running the unittests it's leaving the /tmp directory dirty. It's creating 2 files prefixed with "configdrive" on every run, e.g:

(venv)[lucasagomes@lucasagomes ironic]$ ls -la /tmp/configdrive*
-rw------- 1 lucasagomes lucasagomes 0 Jul 7 13:34 /tmp/configdrive2FML5i
-rw------- 1 lucasagomes lucasagomes 0 Jul 7 13:34 /tmp/configdriveDxy_JS
-rw------- 1 lucasagomes lucasagomes 0 Jul 7 13:34 /tmp/configdrivefdIpBq
-rw------- 1 lucasagomes lucasagomes 0 Jul 7 13:32 /tmp/configdriveo0prQ7
-rw------- 1 lucasagomes lucasagomes 0 Jul 7 13:32 /tmp/configdrivePRVoqD
-rw------- 1 lucasagomes lucasagomes 0 Jul 7 13:34 /tmp/configdriveZFtmBK

We should mock the file creation.

How to reproduce:

1 - Run the unittests
2- Check the /tmp directory

[Dmitry Tantsur (divius)]

Importance low as it does not affect actual features

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/199078
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=65b219d02fb0398195cb563016edd745670f7290
Submitter: Jenkins
Branch: master

commit 65b219d02fb0398195cb563016edd745670f7290
Author: Lucas Alvares Gomes <email address hidden>
Date: Tue Jul 7 13:36:38 2015 +0100

    Mock the file creation for the GetConfigdriveTestCase tests

    The patch mock the call to the tempfile.NamedTemporaryFile in the
    GetConfigdriveTestCase test cases.

    Closes-Bug: #1472245
    Change-Id: Id92fd34ee334a0a8df618b8814be19d06a907436