yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #72562
[Bug 1761536] Re: Nova compute manager failed to create virtual interface
The crashdump shows multiple occurrences of RPC Timeouts in neutron-openvswitch-agent.log:
Timeout in RPC method tunnel_sync. Waiting for 54 seconds before next attempt. If the server is not down, consider increasing the rpc_response_timeout option as Neutron server(s) may be overloaded and unable to respond quickly enough.: MessagingTimeout: Timed out waiting for a reply to message ID 6ecd4578ba6942769d00f39be63017a7
Right before the server build failure this message is logged:
2018-04-05 11:19:04.188 232295 ERROR neutron.agent.linux.openvswitch_firewall.firewall [req-8b07034a-1536-4fb0-a356-5df4be8a2c8c - - - - -] Initializing unfiltered port e84c9f3c-d412-45de-80fc-acf2af4ab56b that does not exist in ovsdb: Port e84c9f3c-d412-45de-80fc-acf2af4ab56b is not managed by this agent..: OVSFWPortNotFound: Port e84c9f3c-d412-45de-80fc-acf2af4ab56b is not managed by this agent.
It seems to me that the Neutron OpenvSwitch Agent on compute node nova-
compute-kvm_4 is out of sync and that the worker-multiplier and/or rpc-
response-timeout config options of the deployment need adjusting.
** Changed in: charm-neutron-gateway
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1761536
Title:
Nova compute manager failed to create virtual interface
Status in OpenStack neutron-gateway charm:
Invalid
Status in OpenStack Compute (nova):
Invalid
Bug description:
Rally test scenario: NovaServers.boot_server_associate_and_dissociate_floating_ip fails.
All 5 nova-compute-kvm instances timeout:
--------------------------------------------------------------------------------
Task 2ccf3cf6-c252-4e0f-8fdd-ca58ad819aff has 5 error(s)
--------------------------------------------------------------------------------
TimeoutException: Rally tired waiting 300.00 seconds for Server
s_rally_504bd98b_fLz3akho:23cbd6ad-67f7-4e0f-9095-390f50897b62 to
become ('ACTIVE') current status BUILD
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/rally/task/runner.py", line 71, in _run_scenario_once
getattr(scenario_inst, method_name)(**scenario_kwargs)
File "/usr/local/lib/python2.7/dist-packages/rally/plugins/openstack/scenarios/nova/servers.py", line 1116, in run
server = self._boot_server(image, flavor, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/rally/task/atomic.py", line 91, in func_atomic_actions
f = func(self, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/rally/plugins/openstack/scenarios/nova/utils.py", line 86, in _boot_server
check_interval=CONF.openstack.nova_server_boot_poll_interval
File "/usr/local/lib/python2.7/dist-packages/rally/task/utils.py", line 252, in wait_for_status
timeout=timeout)
TimeoutException: Rally tired waiting 300.00 seconds for Server s_rally_504bd98b_fLz3akho:23cbd6ad-67f7-4e0f-9095-390f50897b62 to become ('ACTIVE') current status BUILD
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-gateway/+bug/1761536/+subscriptions
References