
Somehow, the instance actions API was different in three places: 1. The actual API from a running system 2. The regular unit tests 3. The api_samples tests This fixes the fake_instance_actions module to look like the database model (which was the root of the problem) as well as the api_samples and regular unit tests to properly confirm the actual behavior I validated manually against a running system. This looks like it changes the external API, but in fact, it makes things match what the external API actually is. Change-Id: I0c8ddff3e0819a65667617083dfaa74f7317cc05
6 lines
565 B
XML
6 lines
565 B
XML
<?xml version='1.0' encoding='UTF-8'?>
|
|
<instanceAction instance_uuid="b48316c5-71e8-45e4-9884-6c78055b9b13" user_id="789" start_time="2012-12-05T00:00:00.000000" request_id="req-3293a3f1-b44c-4609-b8d2-d81b105636b8" action="reboot" message="" project_id="147">
|
|
<events finish_time="2012-12-05 01:02:00.000000" start_time="2012-12-05 01:00:02.000000" traceback="" event="schedule" result="Success"/>
|
|
<events finish_time="2012-12-05 01:04:00.000000" start_time="2012-12-05 01:03:00.000000" traceback="" event="compute_create" result="Success"/>
|
|
</instanceAction>
|