The `fault` should be included to log error message when vmware error happens
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 =
(
key = "com.vmware.
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 =
(
fault =
text = "Failed to attach port"
}
}
reason =
(
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/
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: vmware |
Changed in oslo.vmware: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Now I think it may rather be a bug in vmware then in openstack. the error.localized Message 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.