As far as Ocata is conccerned, as long as it includes https://github.com/openstack/heat/commit/57c5aae88b908002d84a933738293c5917926174 (which it should), then the writing of new properties data for events or resources should always happen in the new resource_properties_data table which includes a longtext data column (and never in the legacy columns in resource or event). So, not sure how that stack trace could happen in Ocata.
I agree with therve that the change he linked to should fix the issue in Newton.
As far as Ocata is conccerned, as long as it includes https:/ /github. com/openstack/ heat/commit/ 57c5aae88b90800 2d84a933738293c 5917926174 (which it should), then the writing of new properties data for events or resources should always happen in the new resource_ properties_ data table which includes a longtext data column (and never in the legacy columns in resource or event). So, not sure how that stack trace could happen in Ocata.
I agree with therve that the change he linked to should fix the issue in Newton.