Bug 1593882

Summary:	Environment file fixed-ip-vips-v6.yaml has incorrect setting for RedisVipPort
Product:	Red Hat OpenStack	Reporter:	Dan Sneddon <dsneddon>
Component:	openstack-tripleo-heat-templates	Assignee:	Dan Sneddon <dsneddon>
Status:	CLOSED ERRATA	QA Contact:	bjacot
Severity:	medium	Docs Contact:
Priority:	medium
Version:	13.0 (Queens)	CC:	bfournie, dpeacock, dsneddon, joflynn, jschluet, mburns
Target Milestone:	z2	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-8.0.4-3.el7ost	Doc Type:	Bug Fix
Doc Text:	Some previous versions of the tripleo-heat-templates contained an error in a setting for the Redis VIP port in the environment file fixed-ips-v6.yaml. If the file fixed-ips-v6.yaml is included on the deployment command line after network-isolation-v6.yaml, the Redis service is placed on the Control Plane network rather than the correct IPv6 network. The file environments/fixed-ips-v6.yaml now contains the correct reference to network/ports/vip_v6.yaml, instead of network/ports/vip.yaml. The fixed-ips-v6.yaml environment file now contains the correct resource registry entries and the Redis VIP will be created with an IPv6 address regardless of the order of the included environment files.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-08-29 16:37:32 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:

Description Dan Sneddon 2018-06-21 18:36:46 UTC

Description of problem:
The included environment file environments/fixed-ip-vips.yaml has an incorrect setting for RedisVipPort. The setting is:

   OS::TripleO::Network::Ports::RedisVipPort: ../network/ports/vip.yaml

But it should be:

   OS::TripleO::Network::Ports::RedisVipPort: ../network/ports/vip-v6.yaml



Version-Release number of selected component (if applicable):
This affects OSP 13 as well as OSP 12

How reproducible:
100%

Steps to Reproduce:
1. Deploy with "-e environments/network-isolation-v6.yaml" before "-e environments/fixed-ip-vips.yaml"
2.
3.

Actual results:
The incorrect Redis VIP setting in fixed-ip-vips.yaml will take precedence if included after network-isolation-v6.yaml, and will cause the redis VIP to fail.

Expected results:
The Redis VIP should be vip-v6.yaml, and not vip.yaml

Additional info:
A quick workaround is to include network-isolation-v6.yaml *after* fixed-ip-vips.yaml.

Comment 1 Dan Sneddon 2018-06-21 18:39:08 UTC

Correction: the file in error is fixed-ip-vips-v6.yaml, not fixed-ip-vips.yaml.

Comment 11 bjacot 2018-08-07 14:21:18 UTC

Verified:

[root@undercloud-0 environments]# cat /etc/yum.repos.d/latest-installed 
13   -p 2018-07-30.2
[root@undercloud-0 environments]# cat fixed-ip-vips-v6.yaml | grep vip
  OS::TripleO::Network::Ports::RedisVipPort: ../network/ports/vip_v6.yaml

Comment 12 Joanne O'Flynn 2018-08-15 08:07:24 UTC

This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible.

If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-".


To add draft documentation text:

* Select the documentation type from the "Doc Type" drop down field.

* A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.

Comment 14 errata-xmlrpc 2018-08-29 16:37:32 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-2018:2574