Bug #2296

Wrong log level for some driver messages

Added by Carlos Martín almost 8 years ago. Updated over 7 years ago.

Status:ClosedStart date:09/03/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Core & System
Target version:Release 4.4
Resolution:invalid Pull request:
Affected Versions:OpenNebula 4.2

Description

For example, a failed attach disk operation logs the error reason as DEBUG, when it should be ERROR

Fri Aug  2 12:32:44 2013 [VMM][D]: Message received: LOG E 0 attach_disk: Command "virsh --connect qemu:///system attach-device 
one-0 /var/lib/one//datastores/0/0/disk.1.attach" failed: error: Failed to attach device from /var/lib/one//datastores/0/0/disk.
1.attach

Fri Aug  2 12:32:44 2013 [VMM][D]: Message received: LOG I 0 error: unsupported configuration: disk bus 'ide' cannot be hotplugg
ed.

Fri Aug  2 12:32:44 2013 [VMM][D]: Message received: LOG E 0 Could not attach /var/lib/one//datastores/0/0/disk.1 (hdb) to one-0

History

#1 Updated by Carlos Martín over 7 years ago

  • Status changed from New to Closed
  • Resolution set to invalid

My bad, it is not a bug, just a bit confusing. The VirtualMachineManagerDriver::protocol method logs any message received from the driver as [D], but the LOG messages are then copied to the individual VM log with the right debug level.

Also available in: Atom PDF