Bug 1158358

Looking at the art_test_runner.log file I see that the first time, directly with the REST API, the "deactivate" action was invoked with the following XML document:

  <action>
    <async>false</async>
    <grace_period>
      <expiry>10</expiry>
    </grace_period>
  </action>

And the second time, with the Python SDK, it was invoked with the following XML document:

  <action>
    <async>false</async>
    <grace_period>
      <expiry>10</expiry>
    </grace_period>
  </action>

Exactly the same, so there is no difference between direct call and the Python SDK call, thus we can take the Python SDK out of the picture.

The RESTAPI always does the same in this case: it runs the MaintenanceNumberOfVdss action. Like this:

  public Response deactivate(Action action) {
    return doAction(
      VdcActionType.MaintenanceNumberOfVdss,
      new MaintenanceNumberOfVdssParameters(asList(guid), false),
      action
    );
  }

There is little room there for differences between calls with the same arguments, so if there is a difference it must be in the state of the involved host, and this is managed by the backend and by VDSM, not by the RESTAPI.

this looks like a timing issue of previous test. Please check the conditions before you run the test and/or try to invoke it separately

Hi Michal,
What condition should I check?

Of the environment. Check that the state of the host corresponds to what the test expects. I'd suspect if you run it separately/manually it will work

Hi Micahl,
Thanks, you were right