Comment 3 for bug 1886807

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

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://a5e1b7092bd931de9d7c-99461a827f8c9e81159099d5f417814c.ssl.cf1.rackcdn.com/738163/21/check/neutron-ovn-tempest-full-multinode-ovs-master/462d24b/compute1/logs/screen-n-cpu.txt
[2]http://paste.openstack.org/show/798558/
[3]http://paste.openstack.org/show/798570/
[4]https://bugs.launchpad.net/nova/+bug/1863021
[5]https://github.com/openstack/oslo.concurrency/blob/ff1e681656ff67fe5e4a276d9dabd77a29db08cb/oslo_concurrency/processutils.py#L193
[6]https://review.opendev.org/#/c/755256/