← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1505571] [NEW] VM delete operation fails with 'Connection to neutron failed - Read timeout' error

 

Public bug reported:

Problem description:
With series of VM delete operation in openstack (4000 vms) with KVM compute nodes,  the VM instance goes into ERROR state.
The error shown in Horizon UI is 
"ConnectionFailed: Connection to neutron failed: HTTPConnectionPool(host='192.168.0.1', port=9696): Read timed out. (read timeout=30)"

This happens because neutron takes more than 30 secs (actually around 80 secs) to delete one port, and nova sets the instance into ERROR state 'cz the default timeout of all neutron api(s) is set to 30 sec in nova.
This can be worked around, by increasing the timeout to 120 in nova.conf. But this cannot be recommended as the solution.

cat /etc/nova/nova.conf | grep url_timeout
url_timeout = 120

** Affects: neutron
     Importance: Undecided
     Assignee: Sonu (sonu-sudhakaran)
         Status: New


** Tags: delete read timeout

** Changed in: neutron
     Assignee: (unassigned) => Sonu (sonu-sudhakaran)

** Tags added: delete

** Tags added: read timeout

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1505571

Title:
  VM delete operation fails with 'Connection to neutron failed - Read
  timeout' error

Status in neutron:
  New

Bug description:
  Problem description:
  With series of VM delete operation in openstack (4000 vms) with KVM compute nodes,  the VM instance goes into ERROR state.
  The error shown in Horizon UI is 
  "ConnectionFailed: Connection to neutron failed: HTTPConnectionPool(host='192.168.0.1', port=9696): Read timed out. (read timeout=30)"

  This happens because neutron takes more than 30 secs (actually around 80 secs) to delete one port, and nova sets the instance into ERROR state 'cz the default timeout of all neutron api(s) is set to 30 sec in nova.
  This can be worked around, by increasing the timeout to 120 in nova.conf. But this cannot be recommended as the solution.

  cat /etc/nova/nova.conf | grep url_timeout
  url_timeout = 120

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1505571/+subscriptions


Follow ups