← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1574985] [NEW] Update security group using Heat

 

Public bug reported:

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

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  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-manik
+   sec_group:
+     type: string
+     default: test-manik
  
  resources:
-   security_group:
-     type: OS::Neutron::SecurityGroup
-     properties:
-       name: { get_param: sec_group }
-       id: b82fd6a2-3592-4173-95a9-e4aab7336610
-       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
+   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

** Description changed:

  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-manik
+     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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1574985

Title:
  Update security group using Heat

Status in neutron:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1574985/+subscriptions


Follow ups