Description of problem: Overcloud deployment fails when deploying with external load balacer templates. Getting following error: 2016-03-14 15:26:40 [StorageMgmtPort]: CREATE_COMPLETE state changed 2016-03-14 15:26:40 [StoragePort]: CREATE_COMPLETE state changed 2016-03-14 15:26:40 [InternalApiPort]: CREATE_COMPLETE state changed 2016-03-14 15:26:41 [ExternalPort]: CREATE_COMPLETE state changed 2016-03-14 15:28:21 [UpdateDeployment]: SIGNAL_IN_PROGRESS Signal: deployment succeeded 2016-03-14 15:28:21 [UpdateDeployment]: CREATE_COMPLETE state changed 2016-03-14 15:28:21 [overcloud-Controller-j3s2i2v2owzf-0-ukrrm45rycr6]: CREATE_FAILED Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:22 [0]: CREATE_FAILED resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:34 [2]: CREATE_FAILED resources[2]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:34 [UpdateDeployment]: SIGNAL_IN_PROGRESS Signal: deployment succeeded 2016-03-14 15:28:34 [UpdateDeployment]: CREATE_COMPLETE state changed 2016-03-14 15:28:34 [overcloud-Controller-j3s2i2v2owzf-2-imhrbrpsthgj]: CREATE_FAILED Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:34 [2]: CREATE_FAILED resources[2]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:43 [UpdateDeployment]: SIGNAL_IN_PROGRESS Signal: deployment succeeded 2016-03-14 15:28:44 [1]: CREATE_FAILED resources[1]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:44 [UpdateDeployment]: CREATE_COMPLETE state changed 2016-03-14 15:28:44 [overcloud-Controller-j3s2i2v2owzf-1-ljkpggjqp4a5]: CREATE_FAILED Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:45 [overcloud-Controller-j3s2i2v2owzf]: UPDATE_FAILED resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:46 [Controller]: CREATE_FAILED resources.Controller: resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-03-14 15:28:47 [overcloud]: CREATE_FAILED Resource CREATE failed: resources.Controller: resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. Stack overcloud CREATE_FAILED Heat Stack create failed. The deployment command I use: openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml --control-scale 3 --compute-scale 1 --ntp-server 10.11.160.238 -e /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip.yaml -e external-lb.yaml Without external load balancer deploys fine. The deployment command I use without ex-lb: openstack overcloud deploy --templates -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml --control-scale 3 --compute-scale 1 --ntp-server 10.11.160.238 Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.Deploy overcloud with external load balancer. 2. 3. Actual results: Deployment fails. Expected results: Deployment succeeds. Additional info: openstack-tripleo-heat-templates-0.8.10-2.el7ost.noarch openstack-tripleo-puppet-elements-0.0.4-1.el7ost.noarch openstack-puppet-modules-7.0.13-1.el7ost.noarch
In /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip.yaml there is a reference to a ManagementPort which is not activated by default: OS::TripleO::Controller::Ports::ManagementPort: ../network/ports/management_from_pool.yaml I was able to get past this error by commenting out the line mentioned above.
Thanks Marius, as per comment #2 we should indeed comment that line and the sample IPs provided at [1] for consistency. I think we might also add the commented lines in external-loadbalancer-vip-v6.yaml https://github.com/openstack/tripleo-heat-templates/blob/master/environments/external-loadbalancer-vip.yaml#L38-L39
openstack-tripleo-heat-templates-0.8.14-1.el7ost problematic lines were commented as requsted in /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip ex-lb can be deployed. OS::TripleO::Controller::Ports::StorageMgmtPort: ../network/ports/storage_mgmt_from_pool.yaml OS::TripleO::Controller::Ports::TenantPort: ../network/ports/tenant_from_pool.yaml # Management network is optional and disabled by default #OS::TripleO::Controller::Ports::ManagementPort: ../network/ports/management_from_pool.yaml
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. https://rhn.redhat.com/errata/RHEA-2016-0604.html