Multiple Functional Health Checks Fail when the Network deployed is a Provider Network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel QA Team | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel QA Team | ||
Newton |
Confirmed
|
Medium
|
Fuel QA Team |
Bug Description
If a customer has chosen to deploy a Provider Network or really any SDN style network in place of OVS with VLAN segmentation or Neutron with GRE Tunneling, the following Functional tests fail when executed from the Fuel Health Check menu. The list includes:
- Create volume and boot instance from it
- Create volume and attach it to instance
- Launch instance
- Launch instance, create snapshot, launch instance from snapshot
- Ceilometer test to check alarm status and get Nova notifications
Each fails with the same error message:
Default private network 'net04' isn't present.Please verify it is properly created. Please refer to
OpenStack logs for more details.
It appears that we are seeking the hard coded name 'net04' as the L3 Subnet attached to the 'net04_ext' L2 network when OVS with VLAN or Neutron with GRE are deployed and we are not checking for any other network against which to act. We should either mark these tests as 'Inactive' or 'Unable to Execute' prior to the attempt to execute. Or, we should better enhance the test to recognize the alternative network configuration.
Changed in fuel: | |
importance: | Undecided → Medium |
assignee: | nobody → Fuel QA Team (fuel-qa) |
status: | Incomplete → Confirmed |
milestone: | none → 7.0 |
Changed in fuel: | |
milestone: | 7.0 → 8.0 |
tags: | added: area-qa |
tags: |
added: area-ostf removed: area-qa health-checks |
@Bruce, thank you for your issue. Could you attach fuel version and diagnostic snapshot, we need it for investigation.