Bug #355

VMware IM driver fails with new 2.0 drivers

Added by Tino Vázquez almost 9 years ago. Updated almost 8 years ago.

Status:ClosedStart date:09/28/2010
Priority:NormalDue date:
Assignee:Tino Vázquez% Done:

0%

Category:Drivers - Auth
Target version:Release 2.0
Resolution:fixed Pull request:
Affected Versions:

Description

Message structure needs to be revised.

From Chris Jonhston in the users mailing list:

--

Looks like a change in RC1 has broken the vmware IM. The "MONITOR" command is sending more data than the IM is expecting. With beta1 it was 3 arguments, with rc1 its 4 arguments, and only 3 are expected by the vmware IM.

one-2.0-beta1/src/im/InformationManagerDriver.cc - line 32
os << "MONITOR " << oid << " " << host << endl;

opennebula-1.9.90/src/im/InformationManagerDriver.cc - line 32
os << "MONITOR " << oid << " " << host << " " << update << endl;

opennebula-1.9.90/src/im_mad/vmware/OneImVmware.java - lines 118-121
} else if (str_split.length != 3) {
send_message("FAILURE Unknown command");
}

I'm guessing since 'update' is associated with the 'SCRIPTS_REMOTE_DIR' in oned.conf and the im_ssh driver it can be ignored for the vmware IM.

Chris

History

#1 Updated by Shi Jin almost 9 years ago

A quick fix to change it to 4 in the opennebula-1.9.90/src/im_mad/vmware/OneImVmware.java

118 } else if (str_split.length != 4)

#2 Updated by Tino Vázquez almost 9 years ago

Fixed in new vmware-java repository. Thanks!

#3 Updated by Tino Vázquez almost 9 years ago

  • Status changed from New to 3
  • Target version set to Release 2.0
  • Resolution set to fixed

#4 Updated by Ruben S. Montero almost 8 years ago

  • Status changed from 3 to Closed

Also available in: Atom PDF