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

   <!--
   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 -->
    * Bug Report
   
   
   ##### COMPONENT NAME
   <!--
   Categorize the issue, e.g. API, VR, VPN, UI, etc.
   -->
   ~~~
   Cloud-Server
   ~~~
   
   ##### CLOUDSTACK VERSION
   <!--
   New line separated list of affected versions, commit ID for issues on main 
branch.
   -->
   
   ~~~
   commit ID: 45d267ccbf2749c547cbbbac4a2cb1f3351dcaf2 on main branch.
   ~~~
   
   ##### CONFIGURATION
   <!--
   Information about the configuration if relevant, e.g. basic network, 
advanced networking, etc.  N/A otherwise
   -->
   
   
   ##### OS / ENVIRONMENT
   <!--
   Information about the environment if relevant, N/A otherwise
   -->
   
   
   ##### SUMMARY
   <!-- Explain the problem/feature briefly -->
   Sensitive information of jobVo.getResult() may log out at 
"s_logger.debug("New job " + workJob.getId() + ", result field: " + 
jobVo.getResult());"
   
   ##### STEPS TO REPRODUCE
   <!--
   For bugs, show exactly how to reproduce the problem, using a minimal 
test-case. Use Screenshots if accurate.
   
   For new features, show how the feature would be used.
   -->
   
   <!-- Paste example playbooks or commands between quotes below -->
   ~~~
   
   ~~~
   
   <!-- You can also paste gist.github.com links for larger files -->
   
   ##### EXPECTED RESULTS
   <!-- What did you expect to happen when running the steps above? -->
   
   ~~~
   
   ~~~
   
   ##### ACTUAL RESULTS
   <!-- What actually happened? -->
   
   <!-- Paste verbatim command output between quotes below -->
   ~~~
   
   ~~~
   
   ##### error code location
   com.cloud.storage.VolumeApiServiceImpl#attachVolumeToVmThroughJobQueue
   
   ~~~
   public Outcome<Volume> attachVolumeToVmThroughJobQueue(final Long vmId, 
final Long volumeId, final Long deviceId) {
   
       final CallContext context = CallContext.current();
       final User callingUser = context.getCallingUser();
       final Account callingAccount = context.getCallingAccount();
   
       final VMInstanceVO vm = _vmInstanceDao.findById(vmId);
   
       VmWorkJobVO workJob = new VmWorkJobVO(context.getContextId());
   
       workJob.setDispatcher(VmWorkConstants.VM_WORK_JOB_DISPATCHER);
       workJob.setCmd(VmWorkAttachVolume.class.getName());
   
       workJob.setAccountId(callingAccount.getId());
       workJob.setUserId(callingUser.getId());
       workJob.setStep(VmWorkJobVO.Step.Starting);
       workJob.setVmType(VirtualMachine.Type.Instance);
       workJob.setVmInstanceId(vm.getId());
       workJob.setRelated(AsyncJobExecutionContext.getOriginJobId());
   
       // save work context info (there are some duplications)
       VmWorkAttachVolume workInfo = new 
VmWorkAttachVolume(callingUser.getId(), callingAccount.getId(), vm.getId(), 
VolumeApiServiceImpl.VM_WORK_JOB_HANDLER, volumeId, deviceId);
       workJob.setCmdInfo(VmWorkSerializer.serialize(workInfo));
   
       _jobMgr.submitAsyncJob(workJob, VmWorkConstants.VM_WORK_QUEUE, 
vm.getId());
   
       AsyncJobVO jobVo = _jobMgr.getAsyncJob(workJob.getId());
       s_logger.debug("New job " + workJob.getId() + ", result field: " + 
jobVo.getResult());
   
       
AsyncJobExecutionContext.getCurrentExecutionContext().joinJob(workJob.getId());
   
       return new VmJobVolumeOutcome(workJob, volumeId);
   }
   ~~~


-- 
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