Nova conductor container fails on healthcheck
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Emilien Macchi |
Bug Description
Periodic standalone jobs in master fail because of failing nova-conductor healthcheck:
In periodic-
TASK [Fail if nova-conductor healthcheck report failed status] *****************
2019-09-11 04:52:09 | fatal: [standalone]: FAILED! => {"changed": false, "msg": "nova-conductor isn't working (healthcheck failed)"}
In standalone upgrade job: http://
2019-09-11 02:57:21 | 2019-09-11 02:57:21.970 76995 WARNING tripleoclient.
2019-09-11 02:57:22 | 2019-09-11 02:57:22.004 76995 WARNING tripleoclient.
Changed in tripleo: | |
importance: | Undecided → Critical |
tags: | added: queens-backport-potential |
Changed in tripleo: | |
assignee: | Emilien Macchi (emilienm) → Cédric Jeanneret (cjeanner) |
Changed in tripleo: | |
assignee: | Cédric Jeanneret (cjeanner) → Emilien Macchi (emilienm) |
IIUC https:/ /github. com/openstack/ paunch/ blob/b33aeea972 8233aca852a3e13 2f23fca71ac42df /paunch/ utils/systemd. py#L238 set OnActiveSec=120 so first healthcheck does not run until 2 minutes after starting the service. The validation tasks need to account for this