reschedule failed because port still in use
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
High
|
Liusheng |
Bug Description
When booting an instance with a port specified, if the instance spawn faild for libvit error, the instance will be rescheduled, and will raise a "PortInUse" exception.
To reproduce, we can add "raise Exception" after spawn in _build_instance() and restart nova-compute.
more details plz see:
Traceback (most recent call last):
File "/usr/lib64/
set_
File "/usr/lib64/
LOG.
File "/usr/lib64/
block_
File "/usr/lib64/
admin_
File "/usr/lib64/
net = netutils.
File "/usr/lib64/
if not (network_info and template):
File "/usr/lib64/
return self._sync_
File "/usr/lib64/
self.wait()
File "/usr/lib64/
self[:] = self._gt.wait()
File "/usr/lib64/
return self._exit_
File "/usr/lib64/
current.
File "/usr/lib64/
result = function(*args, **kwargs)
File "/usr/lib64/
dhcp_
File "/usr/lib64/
raise exception.
PortInUse: Port faf3aa64-
Changed in nova: | |
assignee: | nobody → Liusheng (liusheng) |
description: | updated |
description: | updated |
tags: | added: network |
tags: | added: havana-backport-potential icehouse-backport-potential |
Changed in nova: | |
importance: | Undecided → High |
Fix proposed to branch: master /review. openstack. org/87915
Review: https:/