Custom network names prevent deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Steven Hardy |
Bug Description
We have a requirement to use custom network names, for example:
StorageMgmtNe
StorageMgmtAl
StorageMgmtNe
StorageMgmtNe
InternalApiNe
InternalApiAl
InternalApiNe
InternalApiNe
However when we try to deploy with these, we get:
{u'deploy_stdout': u"Matching apachectl 'Server version: Apache/2.4.6 (Red Hat Enterprise Linux)\nServer built: Aug 3 2016 08:33:27'\n", u'deploy_stderr': u'exception: connect |
| | failed\
We are using predictable IP addresses and custom hostname also.
For Red Hat folks please see case number: 01760629
to which I have attached sos reports, templates etc.
Changed in tripleo: | |
milestone: | ocata-3 → ocata-rc1 |
tags: | added: newton-backport-potential |
Changed in tripleo: | |
milestone: | ocata-rc1 → ocata-rc2 |
I think this is because we've mistakenly got some hard-coded references to the default names which crept in via the custom roles rework we (I) did in Newton, in particular I think this is problematic:
https:/ /github. com/openstack/ tripleo- heat-templates/ blob/master/ network/ ports/net_ ip_list_ map.yaml# L69
there may be some others, will try to reproduce and report back.