The `fault` should be included to log error message when vmware error happens

Bug #1367741 reported by Jaroslav Henner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned
oslo.vmware
Confirmed
Medium
Unassigned

Bug Description

... because it can contain important information. For example:

(TaskInfo){
   key = "task-34928"
   task =
      (task){
         value = "task-34928"
         _type = "Task"
      }
   description =
      (LocalizableMessage){
         key = "com.vmware.vim.vpxd.vpx.vmprov.CreateDestinationVm"
         message = "Copying Virtual Machine configuration"
      }
   name = "CreateVM_Task"
   descriptionId = "Folder.createVm"
   entity =
      (entity){
         value = "group-v3"
         _type = "Folder"
      }
   entityName = "vm"
   state = "error"
   cancelled = False
   cancelable = False
   error =
      (LocalizedMethodFault){
         fault =
            (PlatformConfigFault){
               text = "Failed to attach port"
            }
         localizedMessage = "An error occurred during host configuration."
      }
   reason =
      (TaskReasonUser){
         userName = "root"
      }
   queueTime = 2014-09-10 12:46:48.283593
   startTime = 2014-09-10 12:46:48.290384
   completeTime = 2014-09-10 12:46:49.798797
   eventChainId = 157130
 }

Currently, only the localizedMessage is used to produce the log line in nova/virt/vmwareapi/driver.py _poll_task(). In this case, the message is too general. The important reason is said in the error.fault.text, so It should be reported as well.

Tags: vmware
Sean Dague (sdague)
Changed in nova:
status: New → Confirmed
importance: Undecided → Low
tags: added: vmware
Revision history for this message
Jaroslav Henner (jhenner) wrote :

Now I think it may rather be a bug in vmware then in openstack. the error.localizedMessage should probably contain the error.fault.text. Therefore I am abandoning https://review.openstack.org/#/c/120431/ and waiting for vmware guys to resolve this.

Changed in oslo.vmware:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
importance: Low → Undecided
status: Confirmed → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.