Open Stack

Hi,

On Wed, Nov 25, 2020 at 04:21:11PM +0100, Oliver Wenz wrote:
> > First of all I'd suggest checking `openstack network agent list` and ensure that lxb agent is present there up and healthy.
> > Next I'd check nova-scheduler log (journalctl eventually) as it might have more insights.
> 
> linuxbridge agent is up and healthy and the nova-scheduler log doesn't
> show any errors either
> 
> > Please check in neutron server logs for the problems with binding port
> 
> Indeed, running journalctl and grepping for the instance id shows an
> error (last lines):
> 
> journalctl -u neutron-server -n 300 | grep
> 33c662c2-99d6-40fb-a716-118ad8b3b193
> 
> Nov 25 15:06:58 infra1-neutron-server-container-cbf4b105
> neutron-server[88]: 2020-11-25 15:06:58.738 88 INFO neutron.wsgi
> [req-e5b7df6c-bfde-438a-bbb1-f2713b63e16b
> 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 -
> default default] 192.168.110.128,192.168.110.201 "GET
> /v2.0/ports?device_id=33c662c2-99d6-40fb-a716-118ad8b3b193 HTTP/1.1"
> status: 200  len: 205 time: 0.3313231
> Nov 25 15:07:04 infra1-neutron-server-container-cbf4b105
> neutron-server[89]: 2020-11-25 15:07:04.782 89 INFO neutron.wsgi
> [req-9bdadc77-27d9-4f9d-86b5-349b598b1ba4
> eaf8235312004e2da519b54d196f5415 474b7aa9b7894d6782402135c6ef4c2a -
> default default] 192.168.110.205,192.168.110.201 "GET
> /v2.0/ports?tenant_id=0f14905dab5546e0adec2b56c0f6be88&device_id=33c662c2-99d6-40fb-a716-118ad8b3b193
> HTTP/1.1" status: 200  len: 1084 time: 0.0956030
> Nov 25 15:07:05 infra1-neutron-server-container-cbf4b105
> neutron-server[89]: 2020-11-25 15:07:05.020 89 INFO
> neutron.notifiers.nova [-] Nova event response: {'name':
> 'network-changed', 'server_uuid':
> '33c662c2-99d6-40fb-a716-118ad8b3b193', 'tag':
> '1e24a151-bd29-47f8-914b-05c66587541b', 'status': 'completed', 'code': 200}
> Nov 25 15:07:05 infra1-neutron-server-container-cbf4b105
> neutron-server[89]: 2020-11-25 15:07:05.781 89 INFO neutron.wsgi
> [req-9b729386-4847-4be3-80fa-dce244435ddd
> eaf8235312004e2da519b54d196f5415 474b7aa9b7894d6782402135c6ef4c2a -
> default default] 192.168.110.205,192.168.110.201 "GET
> /v2.0/ports?tenant_id=0f14905dab5546e0adec2b56c0f6be88&device_id=33c662c2-99d6-40fb-a716-118ad8b3b193
> HTTP/1.1" status: 200  len: 1084 time: 0.1147285
> Nov 25 15:12:12 infra1-neutron-server-container-cbf4b105
> neutron-server[89]: 2020-11-25 15:12:12.445 89 INFO neutron.wsgi
> [req-15cbcb76-04cd-4813-b1f9-d7f6596e14bf
> 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 -
> default default] 192.168.110.205,192.168.110.201 "GET
> /v2.0/ports?device_id=33c662c2-99d6-40fb-a716-118ad8b3b193 HTTP/1.1"
> status: 200  len: 1085 time: 0.4594653
> Nov 25 15:12:14 infra1-neutron-server-container-cbf4b105
> neutron-server[83]: 2020-11-25 15:12:14.453 83 WARNING
> neutron.notifiers.nova [-] Nova event: {'server_uuid':
> '33c662c2-99d6-40fb-a716-118ad8b3b193', 'name': 'network-vif-deleted',
> 'tag': '1e24a151-bd29-47f8-914b-05c66587541b', 'status': 'failed',
> 'code': 422} returned with failed status

So this looks like issue during sending notification to Nova. You should check
in Nova logs now why it returned You 422

> 
> 
> Kind regards,
> Oliver
> 

-- 
Slawek Kaplonski
Principal Software Engineer
Red Hat