overcloud-without-mergepy.yaml Parameter 'MysqlClusterUniquePart' is invalid

[Dan Prince]

Trying to use the new overcloud-without-mergepy.yaml templates with the latest Heat templates causes the following error:

+ heat stack-create -e /home/devtest/overcloud-env.json -e /home/devtest/tripleo-heat-templates/overcloud-resource-registry-puppet.yaml -t 360 -f /home/devtest/tripleo-heat-templates/overcloud-without-mergepy.yaml -P ExtraConfig= overcloud
ERROR: Failed to validate: Parameter 'MysqlClusterUniquePart' is invalid: length (0) is out of range (min: 4, max: 10)

[OpenStack Infra (hudson-openstack)]

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

[Steven Hardy (shardy)]

This is related to the following heat bugs (which are all really the same):

https://bugs.launchpad.net/heat/+bug/1401317
https://bugs.launchpad.net/heat/+bug/1407100
https://bugs.launchpad.net/heat/+bug/1407877

But this one is a little different, because it's failing a template defined constraint, not one hidden inside a resource property schema, so the fix is likely to be different.

The quickest fix for this one is to remove or comment out the parameter constraint in the template, as has been proposed by Dan, I'll look into possible Heat-level solutions, but landing the fix for the properties validation seems most urgent, as that can't be disabled via the template.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/144746
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=00d305fd40ccfdc8b6b496f166469261414caa26
Submitter: Jenkins
Branch: master

commit 00d305fd40ccfdc8b6b496f166469261414caa26
Author: Dan Prince <email address hidden>
Date: Fri Jan 2 08:54:12 2015 -0500

    Drop the MysqlClusterUniquePart validation

    Trying to use overcloud-without-mergepy currently fails with
    a validation error around MysqlClusterUniquePart. This
    works around the issue by temporarily dropping the validation.

    Change-Id: If93945a2c3396b07b592d08efb1f66e11d6194dd
    Partial-bug: #1405446

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 1665174fd54fa245812f455ec053265fd0ae1ddf
Author: Steven Hardy <email address hidden>
Date: Wed Jan 7 10:43:12 2015 +0000

    No parameter value validation when strict_validate disabled

    Partial-Bug: #1405446

    Change-Id: I1c1eedb194e9a30131ee45909542f8b53242262f

[OpenStack Infra (hudson-openstack)]

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

commit f3f9d68fc13d192650f1e4dca484da2efa635a38
Author: Steven Hardy <email address hidden>
Date: Mon Jan 12 16:32:56 2015 +0000

    Make StackResource less strict on initial validation

    When doing the initial validate(), skip validating values by setting
    the stack strict_validate to False, otherwise we incorrectly fail
    validation when values are passed in via properties/parameters which
    refer to resources in the parent stack.

    Co-Authored-by: Angus Salkeld <email address hidden>
    Change-Id: Ib75c2de6c32373de72901b9f7c5e3828bd9ee7d9
    Closes-Bug: #1407100
    Closes-Bug: #1407877
    Closes-Bug: #1405446