Bug 1721595

Summary: Undercloud update fails when public_host set to IPv6 with Lookup of key vswitch::ovs::package_ensure
Product: Red Hat OpenStack Reporter: Gurenko Alex <agurenko>
Component: instack-undercloudAssignee: Alex Schultz <aschultz>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: aschultz, jslagle, mburns, mcornea, slinaber
Target Milestone: z7Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: instack-undercloud-8.4.7-10.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-10 13:05:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1695460, 1696332, 1699972    
Attachments:
Description Flags
/etc/puppet/hieradata/puppet-stack-config.yaml none

Description Gurenko Alex 2019-06-18 16:08:51 UTC
Description of problem: When setting undercloud_public_host to IPv6 address and running openstack undercloud install, configuration update fails.


Version-Release number of selected component (if applicable):

OSP13
Puddle: 2019-06-13.2

How reproducible:


Steps to Reproduce:
1. set undercloud_public_host to IPv6 address
2. run openstack undercloud install


Actual results:

2019-06-18 19:01:28,111 INFO: dib-run-parts Tue Jun 18 19:01:28 IDT 2019 Running /usr/libexec/os-refresh-config/configure.d/50-puppet-stack-config
2019-06-18 19:01:28,115 INFO: + set -o pipefail
2019-06-18 19:01:28,116 INFO: + puppet_apply puppet apply --summarize --detailed-exitcodes /etc/puppet/manifests/puppet-stack-config.pp
2019-06-18 19:01:28,116 INFO: + set +e
2019-06-18 19:01:28,116 INFO: + puppet apply --summarize --detailed-exitcodes /etc/puppet/manifests/puppet-stack-config.pp
2019-06-18 19:01:35,420 INFO: Notice: hiera(): Cannot load backend module_data: cannot load such file -- hiera/backend/module_data_backend
2019-06-18 19:01:35,422 INFO: Error: Evaluation Error: Error while evaluating a Function Call, Lookup of key 'vswitch::ovs::package_ensure' failed: (<unknown>): found unexpected ':' while scanning a plain scalar at line 13 column 34 in (<unknown>): found unexpected ':' while scanning a plain scalar at line 13 column 34 at /etc/puppet/modules/tripleo/manifests/network/os_net_config.pp:22:3 on node undercloud-0.redhat.local
2019-06-18 19:01:35,466 INFO: + rc=1
2019-06-18 19:01:35,466 INFO: + set -e
2019-06-18 19:01:35,466 INFO: + echo 'puppet apply exited with exit code 1'
2019-06-18 19:01:35,467 INFO: puppet apply exited with exit code 1
2019-06-18 19:01:35,467 INFO: + '[' 1 '!=' 2 -a 1 '!=' 0 ']'
2019-06-18 19:01:35,467 INFO: + exit 1
2019-06-18 19:01:35,467 INFO: [2019-06-18 19:01:35,467] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit status 1]
2019-06-18 19:01:35,467 INFO:
2019-06-18 19:01:35,467 INFO: [2019-06-18 19:01:35,467] (os-refresh-config) [ERROR] Aborting...
2019-06-18 19:01:35,476 DEBUG: An exception occurred
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 2432, in install
_run_orc(instack_env)
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1610, in _run_orc
_run_live_command(args, instack_env, 'os-refresh-config')
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 673, in _run_live_command
raise RuntimeError('%s failed. See log for details.' % name)
RuntimeError: os-refresh-config failed. See log for details.
2019-06-18 19:01:35,477 ERROR:
#############################################################################
Undercloud install failed.
Reason: os-refresh-config failed. See log for details.
See the previous output for details about what went wrong.  The full install
log can be found at /home/stack/.instack/install-undercloud.log.
#############################################################################
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 2432, in install
_run_orc(instack_env)
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 1610, in _run_orc
_run_live_command(args, instack_env, 'os-refresh-config')
File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 673, in _run_live_command
raise RuntimeError('%s failed. See log for details.' % name)
RuntimeError: os-refresh-config failed. See log for details.
Command 'instack-install-undercloud' returned non-zero exit status 1

Expected results:

Undercloud configuration updated successfully, endpoints are switched to IPv6

Additional info:

Comment 1 Marius Cornea 2019-06-19 14:10:12 UTC
The same issue occurs on fresh undercloud deployments:

2019-06-19 10:09:52,313 INFO: Error: Evaluation Error: Error while evaluating a Function Call, Lookup of key 'vswitch::ovs::package_ensure' failed: (<unknown>): found unexpected ':' while scanning a plain scalar at line 13 column 34 in (<unknown>): found unexpected ':' while scanning a plain scalar at line 13 column 34 at /etc/puppet/modules/tripleo/manifests/network/os_net_config.pp:22:3 on node undercloud-0.redhat.local

Comment 2 Marius Cornea 2019-06-19 14:17:39 UTC
Created attachment 1582262 [details]
/etc/puppet/hieradata/puppet-stack-config.yaml

Attaching /etc/puppet/hieradata/puppet-stack-config.yaml

Comment 3 Alex Schultz 2019-06-19 14:19:43 UTC
controller_public_host_wrapped: [2001:db8::2] needs to be quoted because yaml interprets this as an array

Comment 8 Gurenko Alex 2019-07-03 16:34:52 UTC
Verified on puddle 2019-06-28.1

[stack@undercloud-0 ~]$ rpm -q instack-undercloud
instack-undercloud-8.4.7-10.el7ost.noarch

Comment 10 errata-xmlrpc 2019-07-10 13:05:56 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-2019:1738