Bug 1436872 - Overcloud deployment fails when increasing number of predictable IP addresses
Summary: Overcloud deployment fails when increasing number of predictable IP addresses
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-mistral
Version: 10.0 (Newton)
Hardware: All
OS: Linux
medium
medium
Target Milestone: z5
: 10.0 (Newton)
Assignee: RHOS Maint
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1465513 1465515 1465518
TreeView+ depends on / blocked
 
Reported: 2017-03-28 22:09 UTC by nalmond
Modified: 2020-12-14 08:25 UTC (History)
15 users (show)

Fixed In Version: openstack-mistral-3.0.2-12.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1465513 1465515 1465518 (view as bug list)
Environment:
Last Closed: 2017-09-28 16:37:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 473813 0 None None None 2017-06-13 12:50:53 UTC
OpenStack gerrit 473814 0 None None None 2017-06-13 12:51:43 UTC
OpenStack gerrit 473815 0 None None None 2017-06-13 12:53:42 UTC
Red Hat Knowledge Base (Solution) 3232241 0 None None None 2017-11-04 18:06:24 UTC
Red Hat Product Errata RHBA-2017:2824 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 Bug Fix and Enhancement Advisory 2017-09-28 20:34:18 UTC

Description nalmond 2017-03-28 22:09:48 UTC
Description of problem:
When deploying an overcloud with a large number (in this case 117) of predictable IP addresses in the network-environment.yaml, the deployment fails with 'CREATE_FAILED  Resource CREATE failed: resources[0]: Property error: resources.NetworkConfig.properties: Property ControlPlaneDefaultRoute not assigned' despite ControlPlaneDefaultRoute being defined. When using a smaller number (in this case 59) of predictable IP addresses, the deployment is successful.

How reproducible:
Every time there are a large number of predictable IP addresses

Steps to Reproduce:
1. Create heat templates including a large network-environment.yaml
2. Attempt to deploy

Actual results:
Deploy fails with: 'CREATE_FAILED  Resource CREATE failed: resources[0]: Property error: resources.NetworkConfig.properties: Property ControlPlaneDefaultRoute not assigned'

Expected results:
Deploy succeeds

Additional info:
Upon further investigation, this error is seen in /var/log/mistral/api.log just before the deploy fails:
2017-03-22 13:47:02.851 5076 ERROR oslo_db.sqlalchemy.exc_filters DataError: (1406, u"Data too long for column 'variables' at row 1")

A workaround was to change the column type from text to longtext. After doing this, the larger deployment succeeded.

MariaDB [mistral]> SELECT DATA_TYPE FROM INFORMATION_SCHEMA.COLUMNS WHERE table_name = 'environments_v2' AND COLUMN_NAME = 'variables';
+-----------+
| DATA_TYPE |
+-----------+
| text      |
+-----------+

MariaDB [mistral]> ALTER TABLE environments_v2 MODIFY variables LONGTEXT;

Comment 3 Dan Sneddon 2017-06-08 17:32:23 UTC
In this case, the symptom is the failure when using a large number of predictable IPs, but the cause is that the field type doesn't provide enough space for all the data.

So the fix needs to be applied in the Mistral database.

Comment 4 Ryan Brady 2017-06-20 12:19:42 UTC
The fix for this has been landed in upstream mistral in master, ocata and newton.

Comment 10 errata-xmlrpc 2017-09-28 16:37:35 UTC
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:2824


Note You need to log in before you can comment on or make changes to this bug.