Hi, With my nic configs I get the following error
2018-07-26 16:42:49Z [overcloud.ComputeGammaV3.0.NetworkConfig]: CREATE_FAILED resources.NetworkConfig: Parameter 'InternalApiNetworkVlanID' is invalid: could not convert string to float: 2018-07-26 16:42:49Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED Resource CREATE failed: resources.NetworkConfig: Parameter 'InternalApiNetworkVlanID' is invalid: could not convert string to float: 2018-07-26 16:42:50Z [overcloud.ComputeGammaV3.0]: CREATE_FAILED resources.NetworkConfig: resources[0].Parameter 'InternalApiNetworkVlanID' is invalid: could not convert string to float: 2018-07-26 16:42:50Z [overcloud.ComputeGammaV3]: UPDATE_FAILED Resource CREATE failed: resources.NetworkConfig: resources[0].Parameter 'InternalApiNetworkVlanID' is invalid: could not convert string to float: 2018-07-26 16:42:51Z [overcloud.ComputeGammaV3]: CREATE_FAILED resources.ComputeGammaV3: Resource CREATE failed: resources.NetworkConfig: resources[0].Parameter 'InternalApiNetworkVlanID' is invalid: could not convert string to float: 2018-07-26 16:42:51Z [overcloud]: CREATE_FAILED Resource CREATE failed: resources.ComputeGammaV3: Resource CREATE failed: resources.NetworkConfig: resources[0].Parameter 'InternalApiNetworkVlanID' is invalid: could not convert string to float: 2018-07-26 16:42:51Z [overcloud.ComputeGammaV3.0.NetIpMap]: CREATE_COMPLETE state changed Stack overcloud CREATE_FAILED overcloud.ComputeGammaV3.0.NetworkConfig: resource_type: OS::TripleO::ComputeGammaV3::Net::SoftwareConfig physical_resource_id: status: CREATE_FAILED status_reason: | resources.NetworkConfig: Parameter 'InternalApiNetworkVlanID' is invalid: could not convert string to float: Heat Stack create failed. Heat Stack create failed. (undercloud) [stack@staging-director ~]$ packet_write_wait: Connection to 192.168.50.30 port 22: Broken pipe The parameter is defined as following in nic config file InternalApiNetworkVlanID: default: '' description: Vlan ID for the internal_api network traffic. type: number I worked fine when I was using RHOSP11(Ocata) The custom_network_data.yaml defines the internal network as following - name: InternalApi name_lower: internal_api vip: true vlan: 711 ip_subnet: '172.16.2.0/24' allocation_pools: [{'start': '172.16.2.4', 'end': '172.16.2.250'}] Samuel On Fri, Jul 27, 2018 at 7:41 PM, James Slagle <james.sla...@gmail.com> wrote: > On Thu, Jul 26, 2018 at 4:58 AM, Samuel Monderer > <smonde...@vasonanetworks.com> wrote: > > Hi James, > > > > I understand the network-environment.yaml will also be generated. > > What do you mean by rendered path? Will it be > > "usr/share/openstack-tripleo-heat-templates/network/ports/"? > > Yes, the rendered path is the path that the jinja2 templating process > creates. > > > By the way I didn't find any other place in my templates where I refer to > > these files? > > What about custom nic configs is there also a jinja2 process to create > them? > > No. custom nic configs are by definition, custom to the environment > you are deploying. Only you know how to properly define what newtork > configurations needs applying. > > Our sample nic configs are generated from jinja2 now. For example: > tripleo-heat-templates/network/config/single-nic-vlans/role.role.j2.yaml > > If you wanted to follow that pattern such that your custom nic config > templates were generated, you could do that >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev