[
https://issues.apache.org/jira/browse/YUNIKORN-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-1480.
---------------------------------------------
Fix Version/s: 1.2.0
Resolution: Fixed
This seems to link back to [klog issue
67|https://github.com/kubernetes/klog/issues/67] and [klog issue
336|https://github.com/kubernetes/klog/issues/336], does not look like it will
change and allow setting a log level.
> Scheduler crashes if debug logging is enabled on startup
> --------------------------------------------------------
>
> Key: YUNIKORN-1480
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1480
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Affects Versions: 1.2.0
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.2.0
>
>
> After the implementation of dynamic configuration, logging gets
> re-initialized after startup. When the Kubernetes klogger is re-initialized
> due to debug mode being enabled, it causes a Panic and results in a crash
> loop.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
