[openstack-dev] [TripleO][Heat] reverting the HOT migration? // dealing with lockstep changes

James Slagle james.slagle at gmail.com
Wed Aug 13 19:00:50 UTC 2014

On Tue, Aug 12, 2014 at 7:10 PM, Robert Collins
<robertc at robertcollins.net> wrote:
> On 13 August 2014 11:05, Robert Collins <robertc at robertcollins.net> wrote:
>> I've reproduced the problem with zane's fix for the validation error -
>> and it does indeed still break:
>> "| stack_status_reason  | StackValidationFailed: Property error :
>> NovaCompute6:
>> |                      | key_name Value must be a string
>>              "
> Filed https://bugs.launchpad.net/heat/+bug/1356097 to track this.
> Since this makes it impossible to upgrade a pre-HOT-migration merged
> stack, I'm going to push forward on toggling back to non-HOT, at least
> until we can figure out whether this is a shallow or deep problem in
> Heat. (Following our 'rollback then fix' stock approach to issues).

The backwards compatibility spec is yet to be approved. This is partly
the reason why i pushed for the stable branches last cycle -- because
TripleO has no backwards compatibility guarantee (yet).

Regardless, I'd hate to see the migration to HOT reverted. That will
cause a lot of churn on folks. Especially on the parts of the Tuskar
work that are depending on this migration. And then the disruption on
everyone again when we try to merge it next time.

I think working through the Heat bugs is less churn. Steve Baker
proposed a fix for the latest issue:
https://review.openstack.org/#/c/113739/ but it's marked WIP. I'd
rather push on getting these fixes merged vs. reverting. Since we
actually don't know if it's a shallow vs. deep problem, let's not
assume deep and automatically cause a bunch of churn for everyone.

-- James Slagle

More information about the OpenStack-dev mailing list