[
https://issues.apache.org/jira/browse/KNOX-2962?focusedWorklogId=884028&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-884028
]
ASF GitHub Bot logged work on KNOX-2962:
----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Oct/23 10:23
Start Date: 09/Oct/23 10:23
Worklog Time Spent: 10m
Work Description: zeroflag opened a new pull request, #800:
URL: https://github.com/apache/knox/pull/800
## What changes were proposed in this pull request?
pending..
## How was this patch tested?
pending ..
Issue Time Tracking
-------------------
Worklog Id: (was: 884028)
Remaining Estimate: 0h
Time Spent: 10m
> Knox readiness check gateway-status endpoint should return the list of
> topologies for which it is waiting for
> --------------------------------------------------------------------------------------------------------------
>
> Key: KNOX-2962
> URL: https://issues.apache.org/jira/browse/KNOX-2962
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: J.Andreina
> Assignee: Attila Magyar
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current behaviour :
> Knox readiness api return only no/pending as the status . Hence when there is
> any issue with any custom topology deployment
> "https://localhost:8443/gateway/health/v1/gateway-status" is invoked , it
> shows status as only PENDING . User have to check the gateway.log file to
> understand what are topologies it is waiting for to be deployed
> Expectation :
> If "https://localhost:8443/gateway/health/v1/gateway-status" is PENDING
> should return the list of topology for which it is waiting for .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)