FloatingIP resource implicitly depends on too many ports
Bug #1399713 reported by
Zane Bitter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Sergey Kraynev | ||
Juno |
Fix Released
|
Medium
|
Sergey Kraynev |
Bug Description
Due to a typo in the fix for bug 1384114 (see after-the-fact comment on https:/
Of course we only want to look at the Port to which the FloatingIP is bound, and take a dependency on the RouterInterfaces for its Subnet.
Changed in heat: | |
assignee: | nobody → Sergey Kraynev (skraynev) |
importance: | Undecided → Medium |
status: | New → Triaged |
milestone: | none → kilo-1 |
tags: | added: juno-backport-potential |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-1 → 2015.1.0 |
tags: | removed: juno-backport-potential |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/140272
Review: https:/