Public gateway ip unaccessible should not resolve in deployment error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
Alex Schultz | ||
Mitaka |
Fix Released
|
Medium
|
Fuel Sustaining |
Bug Description
public_vip_ping will timeout if the public gateway is not accessible. In many environments people first try to deploy without the public gateway being accessible. Fuel should show a big warning in stead of failing the whole deployment.
Steps to reproduce:
Deploy Fuel and configure Fuel to use mirrors from Fuel itself. This way we don't require a public gateway to access the mirrors when deploying or when the network verification is done.
Actual result:
If public gateway is unaccessible the network verification will pass but after the deployment starts it will fail at ping public_vip check. An error is shown in the puppet log but users often have no clue why their deployment fails.
Expected result:
There are 2 different kinds of expectations:
1. If we can finish the deployment without a public gateway being up then we should just make sure that the deployment finishes with an error.
2. If the deployment would never be able to finish without an public gateway being up then the Network Checker should catch this issue before the deployment starts and show an easy to understand message that the gateway should be up.
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
milestone: | none → 8.0 |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: | added: area-python module-netcheck |
tags: | added: team-network |
tags: | removed: need-info |
no longer affects: | fuel/newton |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: | added: on-verification |
tags: | added: on-verification |
We passed SCF in 8.0. Moving the bug to 9.0.