Hi Dave, reason could be found in the VdsUpdateRunTimeInfo.java:refresh(). The call to vdsUpEvent(_vds) is triggered only here and this is calling the executeCommand of InitVdsOnUpCommand. as you can see, this call is conditioned by the vds going from not "up" status to "up" status and also conditioned to not work in the first transition from "_firstStatus". So, executeCommand of InitVdsOnUpCommand is only called if in some point of its life the vds status was other than "UP" and then it was set to "UP" again. Ofri ----- Original Message -----

From: "Wei D Chen" <wei.d.chen@intel.com> To: "engine-devel" <engine-devel@ovirt.org> Cc: "Lijuan Zhang" <lijuan.zhang@intel.com> Sent: Thursday, May 30, 2013 6:21:01 PM Subject: [Engine-devel] cannot execute command in the class of InitVdsOnUpCommand

Hi,

We suppose when one VDS is added into cluster, executeCommand method in InitVdsOnUpCommand.java will be invoked, so, some logic will be checked there. But per our experiment, this is depended on what we actually did. Here are some cases: 1. when reboot VDS, the logic in " executeCommand" will be invoked. 2. when re-deploy engine, the logic in " executeCommand" will be invoked. 3. when we add a new VDS (vdsm is running) into cluster, the logic in " executeCommand" will not be invoked.

What we expect is the logic will also be invoked in the third case, but why it's not invoked? What's behind all of these?

Best Regards, Dave Chen

_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel