haproxy fails to upgrade if database is disabled
Bug #1630650 reported by
Paul Bourke
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
If for some reason enable_mariadb is false when attempting to upgrade haproxy, it will fail in the start task under "Waiting for virtual IP to appear". This is because we use "database_port" to check for the VIP.
A better way would possibly be to enable some form of health check in haproxy that we can query.
| Changed in kolla: | |
| importance: | Undecided → Medium |
| milestone: | none → ocata-1 |
| status: | New → Triaged |
| Changed in kolla: | |
| milestone: | ocata-1 → ocata-2 |
| Changed in kolla: | |
| milestone: | ocata-2 → ocata-3 |
| Changed in kolla: | |
| milestone: | ocata-3 → ocata-rc1 |
| Changed in kolla: | |
| milestone: | ocata-rc1 → pike-1 |
| Changed in kolla: | |
| assignee: | nobody → Mohammed Naser (mnaser) |
| Changed in kolla: | |
| milestone: | pike-2 → pike-3 |
| Changed in kolla: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in kolla: | |
| milestone: | pike-rc1 → queens-1 |
| Changed in kolla: | |
| milestone: | queens-2 → queens-3 |
| Changed in kolla: | |
| milestone: | queens-3 → queens-rc1 |
| Changed in kolla: | |
| milestone: | queens-rc1 → queens-rc2 |
| Changed in kolla: | |
| milestone: | queens-rc2 → rocky-1 |
Revision history for this message
| Jeffrey Zhang (jeffrey4l) wrote Cleanup EOL bug report | #1 |
| Changed in kolla: | |
| assignee: | Mohammed Naser (mnaser) → nobody |
| importance: | Medium → Undecided |
| status: | Triaged → Expired |
To post a comment you must log in.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
Valid example: CONFIRMED FOR: OCATA