stack-list throws an error if any stack returned contains a template error

[Paul Nelson]

Now that template information is being verified, it is possible that old templates created before validation are now considered invalid. If any of stacks were made with a template that is now considered invalid, python-heatclient fails to show anything on stack-list except for an error (using python-heatclient v0.2.8):

ERROR: "2014-03-07" is not a valid heat_template_version. Should be one of: ('2013-05-23',)

Only the error is shown, even though there are many other templates that are fine and should be shown.

[Randall Burt (randall-burt)]

Seems that we may want to skip template validation all together on a stack-list.

[Steve Baker (steve-stevebaker)]

This is really a heat problem

[Steven Dake (sdake)]

I'll investigate removing template validation on stack-list and stack-delete (sbaker's idea). Not really sure we can do much about the update case, since we need validation on update, yet an update of an old stack with the new code will still result in this problem.

[OpenStack Infra (hudson-openstack)]

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

[Steven Dake (sdake)]

Resolution involved a database migration rather than reworking the parsers into a separate validate and parse operation. Long term we might want to think about separating the parsers into these two separate operations, or we may not want to do that :)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/83241
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=b4f14d6e5f19e64e160e224fd7140629729e1666
Submitter: Jenkins
Branch: master

commit b4f14d6e5f19e64e160e224fd7140629729e1666
Author: Steven Dake <email address hidden>
Date: Wed Mar 26 16:04:51 2014 -0700

    Migrate invalid template version values

    If a stack was created with a template that specified an invalid time,
    a variety of operations cannot be done on the stack, resulting in a
    general breakage of Heat. This patch migrates any occurances of version
    numbers that are invalid that were specified prior to the merging of this
    patch. This patch also handles invalid version fields where a non-date
    is specified or an invalid date was specified.

    Change-Id: I5387ffb84dba5160103b3cb02f3d1cc5f352ff29
    Closes-bug: 1296859