Profile update with security group changes only should not recreate network

Bug #1905490 reported by Duc Truong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
senlin
New
Undecided
Duc Truong

Bug Description

When updating a cluster profile with changes to the port security groups only, the network should not be deleted and recreated. Instead, the security group changes should be applied to the existing port.

E.g. old profile:

type: os.nova.server
version: 1.0
properties:
  flavor: 1
  image: "cirros-0.5.1-x86_64-disk"
  networks:
   - network: private
     security_groups:
        - default
  metadata:
    test_key: test_value

new profile:

type: os.nova.server
version: 1.0
properties:
  flavor: 1
  image: "cirros-0.5.1-x86_64-disk"
  networks:
   - network: private
     security_groups:
        - default
        - blah
  metadata:
    test_key: test_value

Duc Truong (dtruong)
Changed in senlin:
assignee: nobody → Duc Truong (dtruong)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/senlin 11.0.0.0rc1

This issue was fixed in the openstack/senlin 11.0.0.0rc1 release candidate.

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.