| 2019-06-10 20:18:06 |
Bin Qian |
description |
Brief Description
-----------------
SM does not provide detail logging on which condition causes a controller is not being able to go-enabled. Adding a piece of log so to help troubleshooting.
Severity
--------
Minor: This change does not affect any functionality or user experience
Steps to Reproduce
------------------
Provision a controller (e.g, simplex), ensure failure of a go-enabled test. The node will be disabled. However /var/log/sm.log does not provide indication of the reason why the node is disabled.
Expected Behavior
------------------
It will be nice (for a designer) to see a log giving the indication why the node has failed. This is more helpful when a log analysis is required (i.e, a lab is not directly accessible).
Actual Behavior
----------------
As described, there isn't any logging info for that.
Reproducibility
---------------
Always reproducible. |
Brief Description
-----------------
SM does not provide detail logging on which condition causes a controller is not being able to go-enabled. Adding a piece of log so to help troubleshooting.
Severity
--------
Minor: This change does not affect any functionality or user experience
Steps to Reproduce
------------------
Provision a controller (e.g, simplex), ensure failure of a go-enabled test. The node will be disabled. However /var/log/sm.log does not provide indication of the reason why the node is disabled.
Expected Behavior
------------------
It will be nice (for a designer) to see a log giving the indication why the node has failed/not go-enabled. This may be helpful when a log analysis is required (i.e, a lab is not directly accessible).
Actual Behavior
----------------
As described, there isn't any logging info for that.
Reproducibility
---------------
Always reproducible. |
|
