Bug 1512553

Summary: External loadbalancer topology cannot be deploye with external-loadbalancer-vip.yaml template
Product: Red Hat OpenStack Reporter: Marian Krcmarik <mkrcmari>
Component: openstack-tripleo-heat-templatesAssignee: Emilien Macchi <emacchi>
Status: CLOSED DUPLICATE QA Contact: Gurenko Alex <agurenko>
Severity: high Docs Contact:
Priority: unspecified    
Version: 12.0 (Pike)CC: mburns, michele, rhel-osp-director-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-16 13:48:26 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 Marian Krcmarik 2017-11-13 13:56:19 UTC 
Description of problem:
Overcloud deployment fails on references to non-existing templates in tht, The template external-loadbalancer-vip.yaml from tht is being used as part of overcloud deploy command, That template has references to files:
  OS::TripleO::Network::Ports::ExternalVipPort: ../network/ports/external.yaml
  OS::TripleO::Network::Ports::InternalApiVipPort: ../network/ports/internal_api.yaml
  OS::TripleO::Network::Ports::StorageVipPort: ../network/ports/storage.yaml
  OS::TripleO::Network::Ports::StorageMgmtVipPort: ../network/ports/storage_mgmt.yaml
  OS::TripleO::Network::Ports::RedisVipPort: ../network/ports/vip.yaml
  OS::TripleO::Controller::Ports::ExternalPort: ../network/ports/external_from_pool.yaml
  OS::TripleO::Controller::Ports::InternalApiPort: ../network/ports/internal_api_from_pool.yaml
  OS::TripleO::Controller::Ports::StoragePort: ../network/ports/storage_from_pool.yaml
  OS::TripleO::Controller::Ports::StorageMgmtPort: ../network/ports/storage_mgmt_from_pool.yaml
OS::TripleO::Controller::Ports::TenantPort: ../network/ports/tenant_from_pool.yaml

These templates do not exist anymore on OSP12 and are supposed to be generated automatically so probably it should be deleted.

Version-Release number of selected component (if applicable):
openstack-tripleo-heat-templates-7.0.3-0.20171024200825.el7ost.noarch

How reproducible:
Always

Steps to Reproduce:
1. deploy overcloud with external loadbalancer topology using template from tht - external-loadbalancer-vip.yaml

Actual results:
Could not fetch contents for file:///usr/share/openstack-tripleo-heat-templates/network/ports/storage.yaml

Expected results:
overcloud deployed

Additional info:
Comment 1 Michele Baldessari 2017-11-14 20:06:54 UTC 
So one of the related changed could be:
    Render port templates via j2
                     
    Remove these from the j2 excludes and instead render all the networks
    to avoid duplication.
                     
    Change-Id: Id8e14e06ffe959c50456b4c88fef306046a8b478
    Partially-Implements: blueprint composable-networks


Problem is it just moved the port rendering to j2. As a matter of fact if you run
'openstack overcloud plan export overcloud', you'll see that the ports are there.

So am wondering wth is going on here tbh. Can you upload the tar.gz produced via 'openstack overcloud plan export overcloud' and give me a ping?
Comment 2 Marian Krcmarik 2017-11-16 13:48:26 UTC 

*** This bug has been marked as a duplicate of bug 1510419 ***