[AAA-66] Restconf calls return with 503 Service Unavailable for some non-deterministic amount of time after loading karaf Created: 30/Sep/15  Updated: 21/Mar/19  Resolved: 15/Dec/15

Status: Resolved
Project: aaa
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Ryan Goulding Assignee: Ryan Goulding
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
is blocked by AAA-72 AAA StoreBuilder init times out too e... Resolved
Duplicate
is duplicated by NETCONF-59 Restconf returns 503 if TokenAuthFilt... Resolved
External issue ID: 4385

 Description   

https://gist.github.com/anonymous/3dfb44423f8f7b16397a

This is recurring issue. The basic theory is there is some unknown race condition related to the order in which bundles are loaded. HTTP requests result in 503 status code, which occurs for a non-deterministic time (system dependent) before the user can successfully perform HTTP operations on RESTCONF endpoints.



 Comments   
Comment by Anton Ivanov [ 05/Nov/15 ]

Current toaster Li-stable from github shows a very similar issue 100% and it does not fix itself. If it happens to be identical, then it would provide a good environment to troubleshoot it

Comment by Ryan Goulding [ 24/Nov/15 ]

Current patch:

https://git.opendaylight.org/gerrit/#/c/29608/

However, this may not be needed if we add the remaining bundles to config subsystem.

Comment by Ryan Goulding [ 14/Dec/15 ]

https://git.opendaylight.org/gerrit/#/c/30738/

Comment by Ryan Goulding [ 14/Dec/15 ]

Resolved by moving idmlight bundle under config subsystem as part of AAA-72

Generated at Wed Feb 07 19:08:32 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.