Auto security groups are not applied to new instances when scaling a cluster
Bug #1399802 reported by
Andrew Lazarev
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Sahara |
Fix Released
|
High
|
Andrew Lazarev | ||
| Juno |
Fix Released
|
High
|
Nikita Konovalov | ||
Bug Description
Based on https:/
ENVIRONMENT:
Provisioning engine: direct
HOW TO REPRODUCE:
1. Create a cluster. For example, a Vanilla 2 cluster.
2. Create a node group template with enabled auto security groups option.
3. Scale the cluster.
4. Check security groups for new instances.
EXPECTED RESULT:
Auto security groups are applied to new instances.
ACTUAL RESULT:
The default security group is applied to new instances.
| Changed in sahara: | |
| importance: | Undecided → High |
| assignee: | nobody → Andrew Lazarev (alazarev) |
| milestone: | none → kilo-1 |
| Changed in sahara: | |
| status: | New → In Progress |
| Changed in sahara: | |
| status: | Fix Committed → Fix Released |
| Changed in sahara: | |
| milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.

Reviewed: https:/ /review. openstack. org/139285 /git.openstack. org/cgit/ openstack/ sahara/ commit/ ?id=1e3f3663b39 3c988acca178652 78cef39987f24a
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1e3f3663b393c98 8acca17865278ce f39987f24a
Author: Andrew Lazarev <email address hidden>
Date: Thu Dec 4 16:33:33 2014 -0800
Fixed scaling with new node group with auto sg
Need to update node groups after creation of auto security group.
Change-Id: I7fbbe941152f9e 28c5e94dd272d2b a514efbf7c6
Closes-Bug: #1399802