test appears to verify wrong value in assert

[Amrith Kumar]

It appears that the test at

https://github.com/openstack/trove/blob/master/trove/tests/unittests/guestagent/test_agent_heartbeats_models.py#L206-L209

incorrectly checks for haertbeat_found when it should be checking for updated_heartbeat.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/158374

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/158374
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=b9820ab41a9f22e4ec80ab7dcd81f054ca87e20f
Submitter: Jenkins
Branch: master

commit b9820ab41a9f22e4ec80ab7dcd81f054ca87e20f
Author: Amrith Kumar <email address hidden>
Date: Mon Feb 23 12:45:31 2015 -0500

    Correct a test and order of parameters to assertEqual

    In debugging a failing test (test_update_heartbeat) I observed that
    the test was asserting incorrect values and also that the order of
    parameters to assertEqual were inverted. It appears that the order of
    parameters to assertEqual is a more widespread problem.

    The correct order makes the assertion message more useful.

    Change-Id: Ide9f60f8338398ad8e61ad81f4a30058e415f8e9
    Closes-Bug: #1424741
    Partial-Bug: #1277104