When using AWS::EC2::SecurityGroup resources with nova-network (not
Neutron), if a SourceSecurityGroupName was specified in a rule but the
name did not correspond to an extant security group it would be silently
ignored. This change ensures that any such error in the template will cause
creation of the security group to fail.
Reviewed: https:/ /review. openstack. org/81558 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=7246abab34b 4b32f9675e081c7 4bfb628932c8b3
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7246abab34b4b32 f9675e081c74bfb 628932c8b3
Author: Zane Bitter <email address hidden>
Date: Mon Mar 17 12:30:18 2014 -0400
Fail if non-existent security group referenced
When using AWS::EC2: :SecurityGroup resources with nova-network (not roupName was specified in a rule but the
Neutron), if a SourceSecurityG
name did not correspond to an extant security group it would be silently
ignored. This change ensures that any such error in the template will cause
creation of the security group to fail.
Closes-bug: #1291091
Change-Id: I9344451c83f418 4ef46d4e9906b94 abda08836df