You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "J.Andreina (Jira)" <ji...@apache.org> on 2023/10/09 09:48:00 UTC

[jira] [Updated] (KNOX-2962) Knox readiness check gateway-status endpoint should return the list of topologies for which it is waiting for

     [ https://issues.apache.org/jira/browse/KNOX-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J.Andreina updated KNOX-2962:
-----------------------------
    Description: 
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 . 

  was:
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 logs 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 . 


> 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
>            Priority: Major
>
> 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)