Hi, While deploying tripleo on pre-deployed nodes I am facing an issue:
"2018-09-10 17:15:57,822 ERROR: 92948 -- ERROR configuring mysql_init_tasks"
logs attached: http://paste.openstack.org/show/729756/
@akari I have made a pre-provisioned deployment according to your specs (i.e. 2 NICs per server, no network isolation or VLAN). Since this method requires an uninterrupted SSH connection between undercloud and overcloud servers during deployment, l used NIC1 for SSH and NIC2 for provisioning and overcloud traffics.
My local environment:
Networks
Network 1: 192.168.100.0/24 (isolated for SSH connection only)
Network 2: 192.168.24.0/24 (must be routable for external traffic)
Undercloud
NIC1: 192.168.100.2
NIC2: 192.168.24.2
Controller
NIC1: 192.168.100.3
NIC2: 192.168.24.3
Compute
NIC1: 192.168.100.4
NIC2: 192.168.24.4
You would need to pass the following environment files along with others to the CLI (See bottom). All files and folders are placed under the /home/stack directory.
ctlplane-assignments.yaml (change IPs to your local settings)
resource_registry:
OS::TripleO::DeployedServer::ControlPlanePort: /usr/share/openstack-tripleo-heat-templates/deployed-server/deployed-neutron-port.yaml
parameter_defaults:
DeployedServerPortMap:
controller-ctlplane:
fixed_ips:
- ip_address: 192.168.24.3 # nic2 address of pre-configured controller node
subnets:
- cidr: 24
compute-ctlplane:
fixed_ips:
- ip_address: 192.168.24.4 # nic 2 address of pre-configured compute node
subnets:
- cidr: 24
network-environment.yaml (change IPs to your local settings)
resource_registry:
OS::TripleO::ControllerDeployedServer::Net::SoftwareConfig: /home/stack/nic-configs/controller.yaml
OS::TripleO::ComputeDeployedServer::Net::SoftwareConfig: /home/stack/nic-configs/compute.yaml
parameter_defaults:
ControlPlaneSubnetCidr: '24'
ControlPlaneDefaultRoute: 192.168.24.2 # undercloud local_ip
ExternalInterfaceDefaultRoute: 192.168.24.1 # Network 2 gateway
EC2MetadataIp: 192.168.24.2 # undercloud local_ip
NeutronExternalNetworkBridge: "''"
NeutronNetworkType: 'vxlan'
NeutronTunnelTypes: 'vxlan'
nic-configs/controller.yaml
heat_template_version: queens
description: >
Software Config to drive os-net-config to configure ovs bridge on NIC2 for the Controller role.
parameters:
ControlPlaneIp:
default: ''
description: IP address/subnet on the ctlplane network
type: string
StorageIpSubnet:
default: ''
description: IP address/subnet on the storage network
type: string
StorageMgmtIpSubnet:
default: ''
description: IP address/subnet on the storage_mgmt network
type: string
InternalApiIpSubnet:
default: ''
description: IP address/subnet on the internal_api network
type: string
TenantIpSubnet:
default: ''
description: IP address/subnet on the tenant network
type: string
ExternalIpSubnet:
default: ''
description: IP address/subnet on the external network
type: string
ManagementIpSubnet:
default: ''
description: IP address/subnet on the management network
type: string
StorageNetworkVlanID:
default: 30
description: Vlan ID for the storage network traffic.
type: number
StorageMgmtNetworkVlanID:
default: 40
description: Vlan ID for the storage_mgmt network traffic.
type: number
InternalApiNetworkVlanID:
default: 20
description: Vlan ID for the internal_api network traffic.
type: number
TenantNetworkVlanID:
default: 50
description: Vlan ID for the tenant network traffic.
type: number
ExternalNetworkVlanID:
default: 10
description: Vlan ID for the external network traffic.
type: number
ManagementNetworkVlanID:
default: 60
description: Vlan ID for the management network traffic.
type: number
ControlPlaneSubnetCidr:
default: '24'
description: The subnet CIDR of the control plane network.
type: string
ControlPlaneDefaultRoute:
description: The default route of the control plane network.
type: string
ExternalInterfaceDefaultRoute:
default: '10.0.0.1'
description: default route for the external network
type: string
DnsServers:
default: []
description: A list of DNS servers (2 max for some implementations) that will be added to resolv.conf.
type: comma_delimited_list
EC2MetadataIp ...Thanks for the detailed answer tried the stepshowever it gets stcuk in deployment step 3: os-collect-config logs: http://paste.openstack.org/show/730173/ ps - eaf show: keystone proces
You would need to delete previous stacks from the undercloud with openstack overcloud delete overcloud before redeploy anew. Otherwise, the new templates will not be applied properly. Also, your pre-provisioned nodes should be in "brand-new" state to avoid conflicts from previous configurations.
By "fresh booted up servers" you meant freshly installed OS not just a reboot, right? If you get an error you should be able to find some traces from the undercloud or the controller in overcloud. The last resort is to grep haproxy and error from the /var/log and see if you can find something there.
Asked: 2018-09-10 05:59:27 -0500
Seen: 76 times
Last updated: Sep 13
Step 2 is for cluster configuration, including for Pacemaker, HAProxy , Galera/MySQL, etc. How many controller node(s) did you have? Did you use any custom roles or composable services? If using the default controller role (i.e. monolithic), It has to be either 1 or 3 controller nodes with Tripleo.
I have only one controller.. with configuration as http://paste.openstack.org/show/729571/ also i used test-net.yaml for static ip configuration
Before we go further, first I want to make sure if you have configured the switch properly. If you have two NICs for each overcloud node, you need to set trunk ports for the NICs that carry VLAN traffics, if you choose to use network isolation.
Bear in mind that some "not-so-smart" switches require you to manually setup each VLAN ID for trunk ports. You may check with your switch manual for that.
In my case, I used NIC1 on a native vlan for undercloud control plane traffic and NIC2 for all VLANs traffics (including the external/floating IP network) on my overcloud nodes. Without knowing your network setup, the config files may not work.