Display instance uuid instead of VM object
Bug #1489736 reported by
Romil Gupta
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| networking-vsphere |
Fix Committed
|
Undecided
|
Romil Gupta | ||
Bug Description
It is difficult to understand the instance ID whenever we receive an event from vCenter for a particular VM.
so, instead of logging this:
Added vm to cache: <networking_
it should display:
Added VM to cache: 206220f6-
Similarly, instead of logging this:
Handling event VM_CREATED for <networking_
0x7f1b6d837ad0>
it should display:
Handling event VM_CREATED for 206220f6-
| Changed in networking-vsphere: | |
| assignee: | nobody → Romil Gupta (romilg) |
| status: | New → In Progress |
| description: | updated |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-vsphere (master) | #1 |
| Changed in networking-vsphere: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to networking-vsphere (stable/kilo) | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to networking-vsphere (stable/kilo) | #3 |
| tags: | added: in-stable-kilo |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1c51beb361f6dd8
Author: Romil Gupta <email address hidden>
Date: Fri Aug 28 00:19:22 2015 -0700
Display instance uuid instead of VM object
We were logging object handle instead of instance ID
in the debug statements for critical VCenter events.
This fix addresses log-statement only changes to print
instance IDs.
Change-Id: I4483c02de444e7
Closes-Bug: #1489736