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

Bug 1053078

Summary:	[RFE][heat]: Implement handle_update for security group resource
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	ddomingo, markmc, nbarcet, sbaker, shardy, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/heat/+spec/handle-update-for-security-groups
Whiteboard:	upstream_milestone_kilo-1 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-heat-2015.1.0-3.el7ost	Doc Type:	Enhancement
Doc Text:	Resources of type AWS::EC2::SecurityGroup can now be updated in-place when their rules are modified. This is consistent with the behaviour of AWS::EC2::SecurityGroup in CloudFormation. Previously, security groups would be replaced if they were modified.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:11:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-01-14 16:27:41 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/heat/+spec/handle-update-for-security-groups.

Description:

Since neutron and nova-network API allows to update security groups with new rules heat should be able to do that.
Flow:
1. Check if group already exists.
2. Create new rule in group.

https://github.com/openstack/heat/blob/master/heat/engine/resources/security_group.py

Specification URL (additional information):

None

Comment 8 errata-xmlrpc 2015-08-05 13:11:22 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://access.redhat.com/errata/RHEA-2015:1548