Deployment with controllers in non-default nodegroup cause problems with floating IPs
Bug #1537054 reported by
Maksym Strukov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Documentation Team | ||
8.0.x |
Won't Fix
|
Medium
|
Fuel Python (Deprecated) | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Documentation Team | ||
Newton |
Confirmed
|
Medium
|
Fuel Documentation Team |
Bug Description
Given multirack environment on 8.0-429:
Rack01 (default):
* slave01 = compute
* slave02 = cinder
Rack02 (custom):
* slave03..05 = controllers
Instances will not be able to reach internet and will not be reachable from public/private networks IF floating range configured as a part of `public` network of rack with no controllers. So in this case correct to configure float range as part of public net of rack2.
There few issues with this:
1. Issue are not described in our documentation: https:/
2. Fuel are not validate this case BEFORE deployment (both on UI or backend)
I suppose the best way to fix it is to add validation to pre-deployment nailgun checks, it should check that provided floating IP range matches public network of node group with controller(s). If there's no controllers in environment, then no additional validation is needed. Assigned to fuel-python.