I suspect there are at least two errors happening around the same time in your system. The traceback is about the report_state RPC (which in this case is a call(), so we'll wait for the response) not getting a response before timeout.
However the report_state message is not directly involved in booting a VM.
So I suggest multiple things to look at:
1) Is there another error message in your logs while booting the vm? I suspect there is. Usually there's an error message and a traceback in the 'openstack server show' output already in these cases too. Can you copy-paste that here?
2) Usually report_state calls fail to respond timely when neutron-server is overloaded. Is this a fresh deployment? How many neutron agents do you have? What's the overall workload hitting neutron-server? Have you tried tuning your neutron server's worker settings, especially raising the value of rpc_state_report_workers in neutron.conf?
I suspect there are at least two errors happening around the same time in your system. The traceback is about the report_state RPC (which in this case is a call(), so we'll wait for the response) not getting a response before timeout.
However the report_state message is not directly involved in booting a VM.
So I suggest multiple things to look at:
1) Is there another error message in your logs while booting the vm? I suspect there is. Usually there's an error message and a traceback in the 'openstack server show' output already in these cases too. Can you copy-paste that here?
2) Usually report_state calls fail to respond timely when neutron-server is overloaded. Is this a fresh deployment? How many neutron agents do you have? What's the overall workload hitting neutron-server? Have you tried tuning your neutron server's worker settings, especially raising the value of rpc_state_ report_ workers in neutron.conf?