A tempest test [1] launches additional instances of Congress using subprocess.popen and tests the coordination between them and the original instance launched by devstack. The problem is, the new instances are launched from the tempest test user rather than the user of the original congress instance devstack created. As a result, the new instances fail for being unable to access the encryption keys created by the original congress instance (600 permission).[2]
Any suggestions for how to workaround this problem? Is it possible to somehow configure the gate job to run tempest tests as SU or as the stackuser that launches the original congress instance? Thanks so much! [1] https://github.com/openstack/congress/blob/master/congress_tempest_tests/te sts/scenario/congress_ha/test_ha.py.disabled#L117 (currently disabled, trying to re-enable) [2] http://logs.openstack.org/35/487235/5/check/gate-congress-dsvm-api-mysql-ub untu-xenial/607623d/logs/testr_results.html.gz (find: OSError: [Errno 13] Permission denied: '/etc/congress/keys/aes_key¹) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
