Update security group using Heat

Bug #1574985 reported by Manik Sidana
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Invalid
Undecided
Unassigned

Bug Description

I created a security group using Horizon dashboard. Then, I created a heat template with the same security group name with some new rules so that my security group gets updatee with new rules. However, heat template created a new security group instead of updating the existing one.

Is this a bug or an unsupported feature ?

Below is my yaml file

heat_template_version: 2013-05-23

description: Create a security group

parameters:
  sec_group:
    type: string
    default: test-secgroup

resources:
  security_group:
    type: OS::Neutron::SecurityGroup
    properties:
      name: { get_param: sec_group }
      rules:
        - remote_ip_prefix: 0.0.0.0/0
          protocol: tcp
          port_range_min: 22
          port_range_max: 22
        - remote_ip_prefix: 0.0.0.0/0
          protocol: icmp

Manik Sidana (manik019)
description: updated
description: updated
Revision history for this message
Doug Wiegley (dougwig) wrote :

Names are not unique for SG's, so it depends on if its a put or post. Was this intended in the heat template?

affects: neutron → heat
Revision history for this message
Manik Sidana (manik019) wrote :

Yes, it is intended for heat template to update an existing security group that was created using neutron CLI.

Changed in heat:
status: New → Invalid
Revision history for this message
Manik Sidana (manik019) wrote :

can u please add a comment with a conclusive answer.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.