[Starlingx-discuss] [Distributed StarlingX - 4.0] Central cloud not becoming active
Hi, We are trying to bring up the starlingx central cloud-4.0 in distributed mode. Version being used in Aug8th 2020 release. Below are the steps followed. 1. Iso installation is done successfully 2. ansible-playbook /usr/share/ansible/stx-ansible/playbooks/bootstrap.yml is run successfully - no errors seen 3. source /etc/platform/openrc - enables keystone admin - no errors see 4. All the system commands required for starlingx central cloud to come up are run successfully - no errors seen 5. Later the node is unlocked, node goes for reboot. After reboot, source /etc/platform/openrc is not running successfully. "Openstack Admin credentials can only be loaded from the active controller" is being displayed Kindly let us know what could be the issue or where to look out for failure logs. One thing I would like to mention, there is already one central cloud up and running in the same subnet "external_oam_subnet: 10.222.22.0/24.", but different node addresses. Can this be the cause of concern. Below is localhost.yaml used for central cloud bring up Regards, Sriram ============= localhost.yaml===================== " distributed_cloud_role: systemcontroller system_mode: duplex #List of DNS servers (public/local), minium 1 server is required, maximum 3 server can be listed dns_servers: - 8.8.8.8 - 4.4.4.4 management_subnet: 10.222.21.0/24 management_start_address: 10.222.21.21 management_end_address: 10.222.21.35 external_oam_subnet: 10.222.22.0/24 external_oam_gateway_address: 10.222.22.254 external_oam_floating_address: 10.222.22.25 external_oam_node_0_address: 10.222.22.26 external_oam_node_1_address: 10.222.22.27 docker_registries: k8s.gcr.io: url: 10.222.22.1:30003/starlingx quay.io: url: 10.222.22.1:30003/starlingx docker.io: url: 10.222.22.1:30003/starlingx gcr.io: url: 10.222.22.1:30003/starlingx defaults: url: 10.222.22.1:30003/starlingx username: admin password: Airvana123! ssl_ca_cert: /home/sysadmin/ca.crt # KUBERNETES PARAMETERS # The apiserver_cert_sans is a list of Subject Alternative Names that will be # applied to apiserver certificate. This value must be a list and each entry # in the list must be a domain name or IP address. #apiserver_cert_sans: # - sysadmin.commscope.com #k8s_root_ca_cert: /home/sysadmin/rootca/rootca.crt #k8s_root_ca_key: /home/sysadmin/rootca/rootca.key # ADMIN CREDENTIALS admin_username: admin admin_password: Airvana123! ansible_become_pass: Airvana123! "
participants (1)
-
Dharwadkar, Sriram