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.
Correction: the file in error is fixed-ip-vips-v6.yaml, not fixed-ip-vips.yaml.
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
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.
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