Following up on bug 1549218, we will be changing the TripleO OpenDaylight healthcheck from the /controller/nb/v2/neutron URL to the better status URL which will be exposed in ODL upstream by https://jira.opendaylight.org/browse/INFRAUTILS-33.
The new INFRAUTILS-33 OpenDaylight status /diagstatus URL healthcheck is dev complete upstream in ODL, and about to be merged there. This BZ issue should then be re-assigned to someone else than me who can take care of the required TripleO healthcheck URL change and impact handling.
The current implementation needs some more fixes. The status returned should be 503 Service unavailable. Right now HTTP GET always returns 200, and HTTP HEAD gives 418 and then hangs when a node is isolated:
[root@controller-0 ~]# curl -i -X GET http://172.17.1.14:8081/diagstatus && curl -i -X HEAD http://172.17.1.14:8081/diagstatus --max-time 5
HTTP/1.1 200 OK
"timeStamp": "Tue Aug 21 21:20:07 UTC 2018",
HTTP/1.1 418 418
curl: (28) Operation timed out after 5001 milliseconds with 0 out of 132 bytes received
Fixes have just been proposed upstream, and should trickle downstream eventually.
The patches have been back-ported d/s https://code.engineering.redhat.com/gerrit/#/q/topic:1566080+(status:open+OR+status:merged) but we'll get them for free the next time we rebase on Oxygen.
According to our records, this should be resolved by opendaylight-8.3.0-3.el7ost. This build is available now.
(In reply to Lon Hohberger from comment #17)
> According to our records, this should be resolved by
> opendaylight-8.3.0-3.el7ost. This build is available now.
Lon, looks like you got this wrong, could that be? According to https://brewweb.engineering.redhat.com/brew/packageinfo?packageID=54522 (which Tomas just showed me), opendaylight-8.3.0-3.el7ost was built on 2018-08-07 but https://code.engineering.redhat.com/gerrit/#/c/148168/ (and the others listed above) were only merged Sep 5 - so this didn't make it into 8.3.0-3 but 8.3.0-4.... I'm therefore adjusting the Fixed In Version accordingly.
Could someone who understands the process better than I do update the Status?
*** Bug 1638702 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.