Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1115588

Summary:	Upon rebuild instances might never get to Active state
Product:	Red Hat OpenStack	Reporter:	Attila Fazekas <afazekas>
Component:	openstack-neutron	Assignee:	Ihar Hrachyshka <ihrachys>
Status:	CLOSED ERRATA	QA Contact:	Toni Freger <tfreger>
Severity:	high	Docs Contact:
Priority:	medium
Version:	5.0 (RHEL 7)	CC:	afazekas, chrisw, ihrachys, ndipanov, nyechiel, sclewis, slong, yeylon
Target Milestone:	rc
Target Release:	5.0 (RHEL 7)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-2014.1.1-5.el6ost openstack-neutron-2014.1.1-5.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, OpenStack Networking could stop processing network ports that disappeared from the integration bridge during the L2-agent loop, even after those ports were back on the bridge. As a result, updates for temporarily disappeared ports were not handled by the L2 agent. With this update, these ports are no longer marked as processed if not found on the integration bridge. Ports are now processed correctly even after they temporarily disappear from the integration bridge.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-02 17:59:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Attila Fazekas 2014-07-02 16:45:15 UTC

Description of problem:
Nova can miss neutron notification, which leads to the instance never get into the active state.

Comment 2 Attila Fazekas 2014-07-03 15:29:01 UTC

The referenced upstream change (99182) does not seams to really solves the issue,
may be it will be solved on neutron side or by new nova change.

Comment 3 Attila Fazekas 2014-07-09 14:14:58 UTC

Look like the root cause was on the neutron side, moving this to neutron.

Comment 4 Ihar Hrachyshka 2014-07-28 11:09:01 UTC

Steps to reproduce are not that clear. We know that the issue may be triggered by e.g. instance rebuild or reboot that make VIF to disappear for some time. If it's disappearance is caught by L3 agent loop, it's not marked as passive, and hence no notifications or updates are processed afterwards.

Comment 5 Ihar Hrachyshka 2014-07-28 11:10:15 UTC

Sorry, L2 agent, not L3 one.

Comment 9 Toni Freger 2014-08-14 11:04:27 UTC

The rebuild option works as expected via CLI and Dashboard.
VMs became active after the rebuild process.

Info:
RHOS: http://download.eng.bos.redhat.com/rel-eng/OpenStack/5.0-RHEL-6/2014-08-13.1
On RHEL7
All-In-One

Comment 12 errata-xmlrpc 2014-09-02 17:59:45 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2014-1119.html