Description of problem: While attempting an overcloud deployment with RH OSP 8 OSP-d, I would see a create_failed result from the heat stack with several errors referencing: The Referenced Attribute (ManagementPort ip_subnet) is incorrect I used the default network-isolation.yaml content and the default network-environment.yaml files from /usr/share/openstack-tripleo-heat-templates as my starting point for my templates. The Management network was left disabled with the ports pointing to network/ports/noop.yaml. Similar to this community tripleo bug. https://bugs.launchpad.net/tripleo/+bug/1575622 Version-Release number of selected component (if applicable): RH OSP 8 My deploy command: openstack overcloud deploy --templates \ -e /home/stack/templates/network-environment.yaml \ -e /home/stack/templates/limits.yaml \ -e /home/stack/templates/firstboot-environment.yaml \ --control-flavor control \ --compute-flavor compute \ --control-scale 1 \ --compute-scale 2 \ --ceph-storage-scale 0 \ --ntp-server time.nist.gov \ --neutron-tunnel-types vxlan \ --neutron-network-type vxlan \ --neutron-bridge-mappings datacentre:br-ex,isolated:br-isolated \ --neutron-network-vlan-ranges datacentre:1:1000,isolated:1:1000 How reproducible: Consistently reproducable on my virtual environment when using the templates at the link below. https://gitlab.consulting.redhat.com/kejones/director-templates/tree/master/NGC_NAPS_dv-8.0 Steps to Reproduce: 1. Do all steps necessary before overcloud deployment 2. Run deploy command above 2. Watch deploy output to see failure Actual results: CREATE_FAILED with errors below 2016-05-07 15:55:22 [NetIpMap]: CREATE_IN_PROGRESS state changed 2016-05-07 15:55:24 [NetIpMap]: CREATE_COMPLETE state changed 2016-05-07 15:55:45 [UpdateDeployment]: SIGNAL_IN_PROGRESS Signal: deployment succeeded 2016-05-07 15:55:46 [0]: CREATE_FAILED resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-05-07 15:55:46 [UpdateDeployment]: CREATE_COMPLETE state changed 2016-05-07 15:55:46 [overcloud-Compute-o2xmkcq4vxh3-0-sxg2jyxwxed3]: CREATE_FAILED Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-05-07 15:55:49 [UpdateDeployment]: SIGNAL_IN_PROGRESS Signal: deployment succeeded 2016-05-07 15:55:50 [UpdateDeployment]: CREATE_COMPLETE state changed 2016-05-07 15:55:50 [overcloud-Compute-o2xmkcq4vxh3-1-uxfky3rreiku]: CREATE_FAILED Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-05-07 15:55:51 [1]: CREATE_FAILED resources[1]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-05-07 15:55:52 [Compute]: CREATE_FAILED resources.Compute: resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-05-07 15:55:52 [overcloud-Compute-o2xmkcq4vxh3]: UPDATE_FAILED resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-05-07 15:55:54 [UpdateDeployment]: SIGNAL_IN_PROGRESS Signal: deployment succeeded 2016-05-07 15:55:54 [UpdateDeployment]: CREATE_COMPLETE state changed 2016-05-07 15:55:54 [overcloud-Controller-l5jv7tinzuqn-0-5ufs7led63kf]: CREATE_FAILED Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. 2016-05-07 15:55:55 [0]: CREATE_FAILED resources[0]: Resource CREATE failed: The Referenced Attribute (ManagementPort ip_subnet) is incorrect. Expected results: Expect successful deployment Additional info: ControlPlaneSubnetCidr is set as a number in the provided network-environment.yaml file. ControlPlaneSubnetCidr: 24 If you set it as a string, you get past this error. ControlPlaneSubnetCidr: '24'
We are seeing as well..any work around for this..? Thanks
The workaround is as follows. ControlPlaneSubnetCidr is set as a number in the provided network-environment.yaml file. ControlPlaneSubnetCidr: 24 If you set it as a string, you get past this error. ControlPlaneSubnetCidr: '24' Sorry I wasn't more clear of this in the original description.
Hi, I confirm the issue and the workaround. Thanks for reporting it. Regards,
I am no longer seeing this in Newton onwards.
There is a fix for 9+. Working on a backport to 8.
*** Bug 1328149 has been marked as a duplicate of this bug. ***
Build of 2017-05-08.1 deployed successfully. [stack@undercloud-0 ~]$ grep ControlPlaneSubnetCidr /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml ControlPlaneSubnetCidr: '24'
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://access.redhat.com/errata/RHBA-2017:1250