rajujith opened a new issue, #8779:
URL: https://github.com/apache/cloudstack/issues/8779

   <!--
   Verify first that your issue/request is not already reported on GitHub.
   Also test if the latest release and main branch are affected too.
   Always add information AFTER of these HTML comments, but no need to delete 
the comments.
   -->
   
   ##### ISSUE TYPE
   <!-- Pick one below and delete the rest -->
   
    * Improvement Request
    
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Logging
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   4.19
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   External KVM with VMs for import
   Cloudstack with KVM cluster
   
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   
   The logging for ImportVm, specifically importing instance from external KVM 
appears to be unusable. The Command sequence send to the KVM agent and the 
answer are hidden in TRACE level logging. Although many of the logging 
statements are DEBUG they don't appear unless TRACE is enabled. 
   Only 'CopyRemoteVolumeAnswer' is seen once in the logs if we follow the 
async job id. The implementation is same for KVM agent as well. Improving the 
logging for this operation to match all other operations in Cloudstack will be 
convenient for operation and maintenance. 
   
   Seq send to the agent such as the below are missing in the DEBUG level which 
is not expected. 
   com.cloud.agent.api.GetRemoteVmsCommand
   com.cloud.agent.api.GetRemoteVmsAnswer
   com.cloud.agent.api.CopyRemoteVolumeCommand
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to