Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1640950

Summary: [CI] opendaylight_api container goes into unhealthy state, curl: The requested URL returned error: 503 Service Unavailable\n\n503 172.17.1.13:8081
Product: Red Hat OpenStack Reporter: Waldemar Znoinski <wznoinsk>
Component: opendaylightAssignee: lpeer <lpeer>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Noam Manos <nmanos>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 14.0 (Rocky)CC: mkolesni, nyechiel, wznoinsk
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-06 07:19:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
karaf log unhealthy
none
opendaylight_api unhealthy robot log.html none

Description Waldemar Znoinski 2018-10-19 08:38:36 UTC
Created attachment 1495565 [details]
karaf log unhealthy

Description of problem:
after CSIT testing, part of which is bringing the opendaylight_api docker container down and up on controllers (HA_L2/3 test suite), as well as blocking ports (External Network suite) opendaylight_api on 1of3 overcloud controllers went into unhealthy state:

docker inspect opendaylight_api shows:
            "Health": {
                "Status": "unhealthy",
                "FailingStreak": 751,
                "Log": [
                    {
                        "Start": "2018-10-19T04:29:38.693654975-04:00",
                        "End": "2018-10-19T04:29:39.243704218-04:00",
                        "ExitCode": 1,
                        "Output": "  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\n503 172.17.1.13:8081 0.005 seconds\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (22) The requested URL returned error: 503 Service Unavailable\n"
                    },
                    {
                        "Start": "2018-10-19T04:30:09.244109388-04:00",
                        "End": "2018-10-19T04:30:09.804145173-04:00",
                        "ExitCode": 1,
                        "Output": "\n503 172.17.1.13:8081 0.005 seconds\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                 Dload  Upload   Total   Spent    Left  Speed\n\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\r  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0\ncurl: (22) The requested URL returned error: 503 Service Unavailable\n"
                    },



Version-Release number of selected component (if applicable):
OSP14, puddle: 2018-10-10.3
opendaylight-8.3.0-4.el7ost.noarch
puppet-opendaylight-8.3.0-0.20180816081508.8c1f7e5.el7ost.noarch


How reproducible:
50%



Steps to Reproduce:
1. deploy osp14 + odl, optionally install a newer ovs2.10 as ovs2.10 in the above puddle is dying when working with ODL, more info in https://bugzilla.redhat.com/show_bug.cgi?id=1637926#c24
2. run ha_l2/3, external network csit test suites
3. observe opendaylight_api container on controller-1 goes into unhealthy state

Actual results:


Expected results:


Additional info:

Comment 1 Waldemar Znoinski 2018-10-19 08:44:31 UTC
Created attachment 1495566 [details]
opendaylight_api unhealthy robot log.html

Comment 2 Mike Kolesnik 2018-10-22 08:46:59 UTC
Waldek,

Can you please attach the relevant logs from OpenStack as well?

Comment 3 Waldemar Znoinski 2018-10-22 09:05:58 UTC
will do next time I catch it, it was not caught in CI but on personal deployment and I don't have these logs anymore

Comment 4 Mike Kolesnik 2018-11-06 07:19:59 UTC
Seems there's not enough info right now, please reopen with the relevant logs if you hit this again.