Floating IP cannot be assigned if instance joins an existing network but not the env's default
Bug #1474092 reported by
Alexander Tivelkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
Medium
|
Alexander Tivelkov |
Bug Description
If the Instance joins an existing network without joining an environment's default network, it may not be assigned a floating IP address.
This happens because fip assignment requires a so-called "primary network" which get automatically resolved as "either a default environment's network or a flat network is the former is not assigned".
If neither environment's default nor flat networks are assigned for the instance, but some custom networks are present, some of them should be chosen as "primary", however this does not happen.
Changed in murano: | |
assignee: | nobody → Alexander Tivelkov (ativelkov) |
milestone: | none → liberty-2 |
status: | New → In Progress |
importance: | Undecided → Medium |
summary: |
- Floating IP cannot be assigned if instance joins an existing network + Floating IP cannot be assigned if instance joins an existing network but + not the env's default |
tags: | added: kilo-backport-potential |
tags: | removed: kilo-backport-potential |
Changed in murano: | |
status: | Fix Committed → Fix Released |
Changed in murano: | |
milestone: | liberty-2 → 1.0.0 |
Changed in murano: | |
milestone: | 1.0.0 → 1.0.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/201304
Review: https:/