Running the python-tripleoclient unit tests results in a .tripleo/history file being created and left on the system. It also seems to make a test fail with py35 sometimes, though I haven't been able to reproduce consistently, maybe it was a fluke:
======================================================================
FAIL: tripleoclient.tests.v1.overcloud_deploy.test_overcloud_deploy.TestDeployOvercloud.test_tht_deploy_with_plan_environment_file
tags: worker-1
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/jpichon/devel/python-tripleoclient/tripleoclient/utils.py", line 72, in store_cli_param
os.mkdir(history_path)
FileExistsError: [Errno 17] File exists: '/home/jpichon/.tripleo'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/jpichon/devel/python-tripleoclient/.tox/py35/lib/python3.5/site-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
File "/home/jpichon/devel/python-tripleoclient/tripleoclient/tests/v1/overcloud_deploy/test_overcloud_deploy.py", line 390, in test_tht_deploy_with_plan_environment_file
self.cmd.take_action(parsed_args)
File "/home/jpichon/devel/python-tripleoclient/tripleoclient/v1/overcloud_deploy.py", line 806, in take_action
utils.store_cli_param(parsed_args)
File "/home/jpichon/devel/python-tripleoclient/tripleoclient/utils.py", line 76, in store_cli_param
raise OSError(messages)
OSError: Unable to create TripleO history directory:
Regardless, we should probably mock the file creation calls and avoid creating and leaving files on the system when running unit tests.
Related fix proposed to branch: master
Review: https:/