Description of problem: During the final days of heat development, we found that instance names were limited to 63 characters. We have found through lots of upstream support requests, that this doesn't work for many people's use cases. I believe our customers would be negatively impacted if they see this limit. Version-Release number of selected component (if applicable): openstack-heat-2013.1.4-1.el6 How reproducible: 100% Steps to Reproduce: 1. create a template with a instance resource name of greater then 63 characters 2. 3. Actual results: Heat generates an error to the user that the template has a resource name that is too long Expected results: Heat should work with any resource name length Additional info:
@sbaker, You did the work on the upstream patch. I seem to recall from IRC that you were planning on handling backports for Havana. If this is not the case, could you assign the cherry-pick to someone else? I believe Steve Hardy also has experience in this area. Once the bug is merged into stable/havana upstream, set needinfo on me, and I'll do a build with the changes.
Version number is wrong in Comment #0. It should be: openstack-heat-2013.2-1.0.el6
Backport proposed internally: https://code.engineering.redhat.com/gerrit/16909 in parallel with the review on stable/havana upstream: https://review.openstack.org/56828 (to avoid any delays in it landing upstream blocking the fix getting into the RC).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html