If many properties are set in trunk, overcloud installation will fail to detect the profile

[David Hill]

overcloud installation fails to detect the profile associated to a profile

Version:
openstack-tripleo-ui-7.0.1-0.20170420105345.fc3983b.el7.centos.noarch

Repositories:
delorean-openstack-tempest-4f97537a5171a8ca4c2d2e8fab4453f794814801

(undercloud) [stack@undercloud-0-trunk cloud]$ openstack overcloud profiles list
+--------------------------------------+-----------+-----------------+-----------------+-------------------+
| Node UUID | Node Name | Provision State | Current Profile | Possible Profiles |
+--------------------------------------+-----------+-----------------+-----------------+-------------------+
| 544dabbe-08f5-459c-a2c9-a09a0207b43b | | available | control | |
| b6419e63-f3a1-474c-b6f1-3dca3efb90a8 | | available | control | |
| bc595640-87c4-43a8-b7fa-ece631a335c1 | | available | control | |
| 6a5e63c8-899e-4433-9b17-e301678895f5 | | available | compute | |
| b2740053-da04-4930-a79b-347d20c11c87 | | available | compute | |
| 46cfc86a-853e-4b45-b93b-f102cb1a8916 | | available | compute | |
| b7c3cc2b-3024-415d-9b58-ce7f493d584a | | available | compute | |
+--------------------------------------+-----------+-----------------+-----------------+-------------------+

(undercloud) [stack@undercloud-0-trunk ~]$ openstack flavor show compute
+----------------------------+--------------------------------------+
| Field | Value |
+----------------------------+--------------------------------------+
| OS-FLV-DISABLED:disabled | False |
| OS-FLV-EXT-DATA:ephemeral | 0 |
| access_project_ids | None |
| disk | 10 |
| id | ef3483c4-84c1-4f30-a9ef-bd06b7dac619 |
| name | compute |
| os-flavor-access:is_public | True |
| properties | capabilities:profile='compute' |
| ram | 256 |
| rxtx_factor | 1.0 |
| swap | 2048 |
| vcpus | 1 |
+----------------------------+--------------------------------------+

Here are the errors we get when trying to deploy the overcloud:

{u'errors': [u'Error: The control flavor has no profile associated.\nRecommendation: assign a profile with openstack flavor set --property "capabilities:profile"="PROFILE_NAME" control', u'Error: The compute flavor has no profile associated.\nRecommendation: assign a profile with openstack flavor set --property "capabilities:profile"="PROFILE_NAME" compute'], u'warnings': []}

ERRORS
[u'Error: The control flavor has no profile associated.\nRecommendation: assign a profile with openstack flavor set --property "capabilities:profile"="PROFILE_NAME" control', u'Error: The compute flavor has no profile associated.\nRecommendation: assign a profile with openstack flavor set --property "capabilities:profile"="PROFILE_NAME" compute', u'Error: The control flavor has no profile associated.\nRecommendation: assign a profile with openstack flavor set --property "capabilities:profile"="PROFILE_NAME" control', u'Error: The compute flavor has no profile associated.\nRecommendation: assign a profile with openstack flavor set --property "capabilities:profile"="PROFILE_NAME" compute']

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE