So I looked at first reported failed job[1] where unshelving timed out. Here is the grepped output with the relevant logs [2]
Sequence of events from the nova-compute perspective:
1) unshelving starts
?) (I don't see when the binding of the port happened but it should be done by the compute at [3])
2) vif-plugged event received but treated as unexpected and ignored
3) nova starts waiting for the vif-plugged event
5) nova plugs the vif
4) nova times out waiting for the plugged event.
Does neutron sends the vif plugged event at bind time instead of plug time in this case?!
So I looked at first reported failed job[1] where unshelving timed out. Here is the grepped output with the relevant logs [2]
Sequence of events from the nova-compute perspective:
1) unshelving starts
?) (I don't see when the binding of the port happened but it should be done by the compute at [3])
2) vif-plugged event received but treated as unexpected and ignored
3) nova starts waiting for the vif-plugged event
5) nova plugs the vif
4) nova times out waiting for the plugged event.
Does neutron sends the vif plugged event at bind time instead of plug time in this case?!
[1] https:/ /zuul.opendev. org/t/openstack /build/ bbf40b69b30d42a 194af50f60915f9 cd/logs
[2] https:/ /paste. opendev. org/show/ 811535/ /github. com/openstack/ nova/blob/ 9f296d775d8f58f cbd03393c81a023 268c7071cb/ nova/compute/ manager. py#L6675
[3] https:/