Bug 1328773

Summary:	neutron - Error while processing VIFS ports fails to apply iptables rules
Product:	Red Hat OpenStack	Reporter:	Nir Magnezi <nmagnezi>
Component:	openstack-neutron	Assignee:	Nir Magnezi <nmagnezi>
Status:	CLOSED ERRATA	QA Contact:	GenadiC <gcheresh>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	amuller, chrisw, jjoyce, jschluet, mlopes, nyechiel, srevivo, stuartjames, tfreger
Target Milestone:	ga
Target Release:	9.0 (Mitaka)
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-neutron-8.1.0-6.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, `ipset` was not declared as a dependency of the Open vSwitch (OVS) and Linux Bridge neutron agents. However, ipset is a dependency of the openstack-neutron package, and this would result in nodes that had the packages for the Open vSwitch or Linux Bridge agent installed, but did not have `openstack-neutron` installed. The L2 agents required ipset for configuration of security groups. With this update, ipset is a dependency of the openstack-openvswitch-agent, and the openstack-linuxbridge-agent packages depend on ipset.	Story Points:	---
Clone Of:	1321870	Environment:
Last Closed:	2016-08-11 12:16:58 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:
Bug Depends On:	1321870
Bug Blocks:	1328757, 1328772

Comment 3 GenadiC 2016-06-21 13:04:54 UTC

Verified in openstack-neutron-8.1.0-6.el7ost.noarch.

Verified as follows:
1) As "ipset" was already installed on compute, I uninstalled it and checked that when creating a new VM the Task State was stucked in spawning and Power state in No state.
2) Checked that there is a traceback in /var/log/neutron/openvswitch-agent.log
3) Reinstalled the ipset and checked that VM changed Power state to running as should

Comment 5 errata-xmlrpc 2016-08-11 12:16:58 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.

https://rhn.redhat.com/errata/RHEA-2016-1597.html