Okay this looks like a simple RPC call timeout to the conductor as the test is setting this timeout to 1 [1] while the actual call and task within the conductor can easily take longer than this [2][3]. I'm not sure why we are suddenly seeing this but I think the easiest thing to do here is to move the call over to long_rpc_timeout?
Okay this looks like a simple RPC call timeout to the conductor as the test is setting this timeout to 1 [1] while the actual call and task within the conductor can easily take longer than this [2][3]. I'm not sure why we are suddenly seeing this but I think the easiest thing to do here is to move the call over to long_rpc_timeout?
[1] https:/ /github. com/openstack/ nova/blob/ 72c8722e09a4779 4fc5412a14587a7 4e79195fca/ nova/tests/ functional/ test_cross_ cell_migrate. py#L73- L75 /github. com/openstack/ nova/blob/ 72c8722e09a4779 4fc5412a14587a7 4e79195fca/ nova/conductor/ rpcapi. py#L459- L468 /github. com/openstack/ nova/blob/ 72c8722e09a4779 4fc5412a14587a7 4e79195fca/ nova/conductor/ tasks/cross_ cell_migrate. py#L1027- L1050
[2] https:/
[3] https:/