Red Hat Bugzilla – Bug 1306022
HA | IPv6 | External LB | Deployment fails with error: Openstack Failed to parse: 2620:52:0:23a9:0:0:0:20:35357
Last modified: 2016-02-18 11:53:04 EST
Description of problem: During post config the following error shows up: ERROR: openstack Failed to parse: 2620:52:0:23a9:0:0:0:20:35357 When using the external lb, the KeystoneAdminApiNetwork is set to internal_api in the ServiceNetMap compared to the default one that's got KeystoneAdminApiNetwork set on ctlplane. Looks similar to in https://bugzilla.redhat.com/show_bug.cgi?id=1299604 Actual Results: Deploying templates in the directory /usr/share/openstack-tripleo-heat-templates /home/stack/.ssh/known_hosts updated. Original contents retained as /home/stack/.ssh/known_hosts.old ERROR: openstack Failed to parse: 2620:52:0:23a9:0:0:0:20:35357 Expected Results: Overcloud successfully deployed with no errors. openstack-puppet-modules-2015.1.8-49.el7ost.noarch
i think this error is coming from either python-rdomanager-oscplugin or os-cloud-config. can you confirm what versions you have of those, please attach output of rpm -qa from the undercloud
likely the error is coming from os-cloud-config when it tries to do the keystone post-config. When Keystone is on the internal_api and that network is ipv6, os-cloud-config is probably assuming ipv4 somewhere.
[stack@puma42 ~]$ rpm -qa | grep python-rdomanager-oscplugin python-rdomanager-oscplugin-0.0.10-27.el7ost.noarch [stack@puma42 ~]$ rpm -qa | grep os-cloud-config os-cloud-config-0.2.8-13.el7ost.noarch
(In reply to Leonid Natapov from comment #4) > [stack@puma42 ~]$ rpm -qa | grep python-rdomanager-oscplugin > python-rdomanager-oscplugin-0.0.10-27.el7ost.noarch > [stack@puma42 ~]$ rpm -qa | grep os-cloud-config > os-cloud-config-0.2.8-13.el7ost.noarch thanks, i think i see what the problem is, i posted a couple of patches
os-cloud-config-0.2.8-14.el7ost.noarch fixed. No parsing error.
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/RHBA-2016-0264.html