[ 
https://issues.apache.org/jira/browse/KNOX-3282?focusedWorklogId=1010207&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1010207
 ]

ASF GitHub Bot logged work on KNOX-3282:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Mar/26 07:43
            Start Date: 19/Mar/26 07:43
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #1179:
URL: https://github.com/apache/knox/pull/1179#issuecomment-4088390695

   ## Test Results
   7 tests   7 ✅  1s ⏱️
   1 suites  0 💤
   1 files    0 ❌
   
   Results for commit a24a9531.
   
   
[test-results]:data:application/gzip;base64,H4sIADCpu2kC/1WMSQ6DMBAEv4LmnIOdAYLzmch4kUYsjrycovw9hrCYW1e1VB+wNJoAz4rfKgiJ4gE6eRnJzRvmIy7XY9+vkJS6ioHeWbBDWEnjRRjvnd+MT/PeW2aZ+/NZW7mIrVy2lJsmihlA3mspGuRCa266lmPHWtE3Umk0tkYh0CJXrIfvDyESq5z7AAAA
   




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1010207)
    Time Spent: 20m  (was: 10m)

> CM discovery error stacktrace to be printed at INFO level
> ---------------------------------------------------------
>
>                 Key: KNOX-3282
>                 URL: https://issues.apache.org/jira/browse/KNOX-3282
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 2.1.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 3.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When a service discovery error occurs, the following log entry is added in 
> gateway.log with the default log4j settings:
> {noformat}
> ERROR discovery.cm (ClouderaManagerServiceDiscovery.java:discover(233)) - 
> Encountered an error during cluster (MCDH5S) discovery: 
> com.cloudera.api.swagger.client.ApiException: Not Found{noformat}
> This is just a sample, there can be a variety of reasons why Knox couldn't 
> connect to CM for discovery.
> While troubleshooting such issues, it's hard to determine the root cause 
> without setting the log level to {{DEBUG}} (at least for 
> {{{}org.apache.knox.gateway.topology.discovery.cm{}}}).
> Suggested change: let stack trace be printed out in the logs even on {{INFO}} 
> level in this case.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to