Bug #576

The core does not check monitoring data

Added by Carlos Martín over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:04/14/2011
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Core & System
Target version:Release 3.0
Resolution:fixed Pull request:
Affected Versions:

Description

If the vmm_mad returns malformed monitoring data, the internal XML representation of the VM breaks.

This leads to an unstable state where the VM can't be managed. If OpenNebula is restarted, the VM can't be loaded from the DB, but its name appears in the VM Pool.

e.g.

POLL SUCCESS 0 STATE=a =512 NETTX=12345

Associated revisions

Revision dd32809e
Added by Ruben S. Montero over 9 years ago

Bug #576: Parser of the monitor information is now more robust. Error parsing the monitor info is log as an error in the VM template. The Template attributes are also XML secure, names are fixed to conform XML namimg conventions

History

#1 Updated by Ruben S. Montero over 9 years ago

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

The parser was not really a problem here. It has been improved to be more robust though. The real problem is attribute names non conforming XML specifications. This has been solved also in this bug. Changes in master.

Also available in: Atom PDF