Fuel network check test reports failure for Neutron DHCP servers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Łukasz Oleś | ||
6.0.x |
Won't Fix
|
High
|
Fuel Python (Deprecated) | ||
6.1.x |
Won't Fix
|
High
|
Fuel Python (Deprecated) | ||
7.0.x |
Fix Released
|
High
|
Łukasz Oleś |
Bug Description
When adding additional nodes to an existing cloud deployed by Fuel, the end users may run the network validation check to make sure the new nodes and/or additional switches are properly configured. If the cloud has active tenants, the Fuel network check detects the tenant DHCP servers and reports a network check failure.
One suggestion is to parse out the DHCP servers detected with MAC addresses from the virtual MAC address range set by Fuel for clouds that are already deployed and do not cause these to fail the check. This does not require access to the OpenStack environment.
If access to the environment is permissible (user provides admin credentials), neutron can be queried to exclude the specific DHCP server MAC's used by tenants. This is probably overkill, but is one option.
Changed in fuel: | |
milestone: | none → 6.0.1 |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
tags: | added: release-notes |
tags: | added: fuel-to-mos |
no longer affects: | fuel/6.0.1-updates |
Issue confirmed on 6.0, have not testing on 6.1 RC yet.