Work around problems storing huge properties in events
There is a maximum limit on the size of the resource properties we can
store for an event in MySQL.
To work around this, store an error instead of the largest property,
as this is expected to cater for graceful-failure of the most common
known case (large SoftwareConfig config properties), with a fallback
of storing only the error when this also fails.
Reviewed: https:/ /review. openstack. org/222352 /git.openstack. org/cgit/ openstack/ heat/commit/ ?id=ab78bde75bb 6aae2025815abd4 613d8dabbbd4df
Committed: https:/
Submitter: Jenkins
Branch: master
commit ab78bde75bb6aae 2025815abd4613d 8dabbbd4df
Author: Zane Bitter <email address hidden>
Date: Thu Sep 10 10:58:52 2015 -0400
Work around problems storing huge properties in events
There is a maximum limit on the size of the resource properties we can
store for an event in MySQL.
To work around this, store an error instead of the largest property,
as this is expected to cater for graceful-failure of the most common
known case (large SoftwareConfig config properties), with a fallback
of storing only the error when this also fails.
Co-Authored-By: Steven Hardy <email address hidden> 3fd20bc5271d6af ea941a5f277
Co-Authored-By: Marios Andreou <email address hidden>
Closes-Bug: #1493858
Change-Id: I668c7ed8ca6c06