I saw that Nova is not spawning correctly the VM [1]. This is recurrent in all failing test cases [2].
The problem is almost always the same: the test case cannot connect to the VM. E.g.: [3]
This error [2] could be related to [4]. When Nova compute tries to execute, inside a privsep context, a command execution, the privsep daemon calling [5] does not implement the workaround provided in the LP bug.
Hello:
I saw that Nova is not spawning correctly the VM [1]. This is recurrent in all failing test cases [2].
The problem is almost always the same: the test case cannot connect to the VM. E.g.: [3]
This error [2] could be related to [4]. When Nova compute tries to execute, inside a privsep context, a command execution, the privsep daemon calling [5] does not implement the workaround provided in the LP bug.
I've pushed [6] in an attempt to fix this issue.
Regards.
[1]https:/ /a5e1b7092bd931 de9d7c- 99461a827f8c9e8 1159099d5f41781 4c.ssl. cf1.rackcdn. com/738163/ 21/check/ neutron- ovn-tempest- full-multinode- ovs-master/ 462d24b/ compute1/ logs/screen- n-cpu.txt paste.openstack .org/show/ 798558/ paste.openstack .org/show/ 798570/ /bugs.launchpad .net/nova/ +bug/1863021 /github. com/openstack/ oslo.concurrenc y/blob/ ff1e681656ff67f e5e4a276d9dabd7 7a29db08cb/ oslo_concurrenc y/processutils. py#L193 /review. opendev. org/#/c/ 755256/
[2]http://
[3]http://
[4]https:/
[5]https:/
[6]https:/