It cannot be ignored, because actually two test cases failed.
1. uses the the router created by devstack (in this case the extra router does not matters) (fail reason unknown)
2. A neutron related test case where the extra router meters. (fail reason can be the missing router)
The q-vpn logs just contains info about delete attempts, but the creation never happens in the agent perspective, however
the q-svc knows about 2 router creation.
If the router does not created with admin_state_up=down, it is expected to be created soon and it needs to be visible in the q-vpn logs.
(It is late here, I will check the logs again soon.)
It cannot be ignored, because actually two test cases failed.
1. uses the the router created by devstack (in this case the extra router does not matters) (fail reason unknown)
2. A neutron related test case where the extra router meters. (fail reason can be the missing router)
The q-vpn logs just contains info about delete attempts, but the creation never happens in the agent perspective, however
the q-svc knows about 2 router creation.
If the router does not created with admin_state_ up=down, it is expected to be created soon and it needs to be visible in the q-vpn logs.
(It is late here, I will check the logs again soon.)