Found this Unittest Failure in tripleoclient and it would seem that we might be missing a mock for hw_architecture or better detection and usage of current hw_architecture from system.
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
File "tripleoclient/tests/v1/overcloud_image/test_overcloud_image.py", line 521, in test_overcloud_create_images
mock.call(mock.ANY, hw_architecture='x86_64'),
File "/usr/lib/python2.7/site-packages/mock/mock.py", line 969, in assert_has_calls
), cause)
File "/usr/lib/python2.7/site-packages/six.py", line 718, in raise_from
raise value
AssertionError: Calls not found.
Expected: [call(<ANY>, hw_architecture='x86_64'),
call(<ANY>, hw_architecture='x86_64'),
call(<ANY>, hw_architecture='x86_64')]
Actual: [call(10, hw_architecture='ppc64le'),
call(10, hw_architecture='ppc64le'),
call(10, hw_architecture='ppc64le')]
Expected result
===============
Run unittests on hw_architecture other than x86_64 and have unittests pass
Actual result
=============
Unittests fail due to hard coded assumption about hw_architecture not mocked out.
Fix proposed to branch: master
Review: https:/