Open Stack

On 2017-07-27 20:37:49 -0700 (-0700), Eric K wrote:
> 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?
[...]

Could you flip this around and create the original instances with
the tempest user? That seems less likely to violate base assumptions
about the test environment.
-- 
Jeremy Stanley