Description of problem:
When running Octavia scenario tests, after deploying it with TripleO, the following tests are failing:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/tempest/test.py", line 103, in wrapper
return f(self, *func_args, **func_kwargs)
File "/usr/lib/python2.7/site-packages/octavia/tests/tempest/v1/scenario/test_load_balancer_tree_minimal.py", line 44, in test_load_balancer_tree_minimal
File "/usr/lib/python2.7/site-packages/octavia/tests/tempest/v1/scenario/base.py", line 249, in _start_backend_httpd_processes
httpd = self._build_static_httpd()
File "/usr/lib/python2.7/site-packages/octavia/tests/tempest/v1/scenario/base.py", line 239, in _build_static_httpd
File "/usr/lib/python2.7/site-packages/octavia/tests/tempest/v1/scenario/base.py", line 826, in execute
proc = subprocess.Popen(args, **subprocess_args)
File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__
File "/usr/lib64/python2.7/subprocess.py", line 1327, in _execute_child
OSError: [Errno 2] No such file or directory
Version-Release number of selected component (if applicable): openstack-octavia-housekeeping-0.10.0-6.el7ost.noarch
How reproducible: 100
Steps to Reproduce:
1. Deploy Director OSP 11 + Octavia
2. Run Octavia scenario tests
Actual results: Fail
Expected results: All tests passed successfully :)
I think the test assumes that the 'go' binary is present on the test machine, and in our case it isn't?
*** Bug 1451789 has been marked as a duplicate of this bug. ***
(In reply to Assaf Muller from comment #2)
> I think the test assumes that the 'go' binary is present on the test
> machine, and in our case it isn't?
Looks like this is the case in u/s OpenStack Nodes, but indeed not in ours.
I've added this as a dependency for the Octavia tests package: https://review.rdoproject.org/r/#/c/6688/
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.