Comment 6 for bug 1193132

Reviewed: https://review.openstack.org/33894
Committed: http://github.com/openstack/heat/commit/90203b89d582b1e8ff673ba1a555683307678fb9
Submitter: Jenkins
Branch: master

commit 90203b89d582b1e8ff673ba1a555683307678fb9
Author: Steve Baker <email address hidden>
Date: Fri Jun 21 10:18:37 2013 +1200

    Do not refresh timestamp from database on read.

    Doing a database refresh on timestamp read is causing errors
    such as:
    heat.openstack.common.rpc.amqp InvalidRequestError:
      Could not refresh instance '<Stack at 0x2c95a90>'

    This has only been seen using postgres, possibly because the problem is
    being masked on mysql due to the driver's lack of concurrency.

    The database refresh seems to be unnecessary, as there appears to be
    no logic which depends on timestamps being accurate (nor is there
    any timestamp comparison logic at all)

    Fixes bug: #1193132
    Change-Id: I22c3c4546a0f44b76a95e473b68b6fbb2e423b90