+++ This bug was initially created as a clone of Bug #1489935 +++ Description of problem: I attempted my fist BM OSP12 bare metal deployment on my cluster that use VLAN tenant networking. This was using the 9-6.1 puddle. As I did with OSP111, I used the network-isolation-no-tunelling.yaml, since it was there. However this seems to reference other yamls which no linger exist. E.G. the first error I got was from network/internal_api.yaml. This didn't exist but the interanl_api_v6.yaml does. I assume this is related to using composable_networks and teh no tunnelling yaml just wasn' t cleaned up. Also have not found documentation on composable networks. Version-Release number of selected component (if applicable): This was using the 9-6.1 puddle. How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Alex Schultz on 2017-09-11 15:15:20 EDT --- Please provide deployment commands, templates and logs. The missing files are generated by the network data so if you aren't properly configuring the roles and networks it could result in these files erroring. Similar to Bug 1488837 --- Additional comment from Steve Reichard on 2017-09-13 12:37:26 EDT --- I redeployed with the 09-08.3 puddle with similar results. Deploy command: #!/bin/bash -x PROJECT=$(basename `dirname $0`) date source stackrc openstack overcloud deploy \ --templates \ --environment-directory /home/stack/mytemplates/env \ --roles-file /home/stack/mytemplates/roles_data.yaml \ --stack ${PROJECT} \ --debug \ --log-file overcloudDeploy.log date Copied the mytemplates subdirectory and log file and a tee of the output of the deploy command to: http://refarch.cloud.lab.eng.bos.redhat.com/pub/tmp/bz1489935/ If you want any other logs, please let me know which or if easier if you want sosreports, let me know which node types to gather. --- Additional comment from Alex Schultz on 2017-09-19 12:46:40 EDT --- Steve, can you take a look at these templates? At first glance it seems to be related to the network refactoring --- Additional comment from Alex Schultz on 2017-09-20 17:43:27 EDT --- In reviewing, I think the file might be wrong and OS::TripleO::Network::Tenant should be set to OS::Heat::None and not ../network/noop.yaml. We have a similar setup in the net-single-nic-with-vlans-no-external.yaml https://github.com/openstack/tripleo-heat-templates/blob/67b14a599689178fbee31068231d636baeacb606/environments/net-single-nic-with-vlans-no-external.yaml#L13 Can you try switching that out and testing it? If that resolves it I can work on fixing this file upstream and doing the appropriate backports.
This issue also exists in OSP11 shipped code. A workaround suggested by Alex worked for me. The workaround was to make the following change in /usr/share/openstack-tripleo-heat-templates/environments/network-isolation-no-tunneling.yaml: OS::TripleO::Network::Tenant: ../network/noop.yaml should become OS::TripleO::Network::Tenant: OS::Heat::None
verified on build 2017-12-06.1
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:0310