Skip to content

Latest commit

 

History

History
218 lines (196 loc) · 7.43 KB

FAQ.md

File metadata and controls

218 lines (196 loc) · 7.43 KB

FAQ

  1. How to see DCHP Requests and Response between nodes and undercloud VM
  • Command to check on jumphost
tcpdump -i br-provision -v -s 1500 '((port 67 or port 68) and (udp[8:1] = 0x1))'
  • Command to check on undercloud VM
tcpdump -i br-ctlplane -vvv -s 1500 '((port 67 or port 68) and (udp[8:1] = 0x1))'
  • Check logs on the undercloud VM
sudo journalctl -u openstack-ironic-inspector-dnsmasq
  1. Steps to recover a node from clean_failed state
openstack baremetal node list
openstack baremetal node maintenance unset <node_uuid> 
ironic --ironic-api-version 1.16 node-set-provision-state <node_uuid> manage
ironic --ironic-api-version 1.16 node-set-provision-state <node_uuid> provide
openstack baremetal node list
  1. How to run deployment script in debug mode
/var/lib/contrail_cloud/scripts/control-hosts-deploy.sh -d
  1. Steps to add contrail controller if not deployed
Login to undercloud
openstack baremetal node delete <cc_node_id>
Login to control host using 'contrail' user on which cc did not get deployed
sudo -i
virsh undefine contrail-controller 
vbmc delete contrail-controller
vbmc start contrail-controller
Remove CC information from the facts,
/var/lib/contrail_cloud/facts.d/<control_host_ip>.fact
/var/lib/contrail_cloud/facts.d/control_vms.yml

Re-run the deployment scripts from the jumphost

/var/lib/contrail_cloud/scripts/control-hosts-deploy.sh 
/var/lib/contrail_cloud/scripts/control-vms-deploy.sh 
/var/lib/contrail_cloud/scripts/openstack-deploy.sh
  1. Steps to upgrade CC to minor releases, run following on jumphost
yum update -y
/var/lib/contrail_cloud/contrail_cloud_installer.sh
/var/lib/contrail_cloud/scripts/install_contrail_cloud_manager.sh
  1. Cleanup the overcloud, step by step from jumphost
/var/lib/contrail_cloud/scripts/openstack-deploy.sh -c
/var/lib/contrail_cloud/scripts/storage-nodes-assign.sh -c
/var/lib/contrail_cloud/scripts/compute-nodes-assign.sh -c
/var/lib/contrail_cloud/scripts/control-vms-deploy.sh -c
/var/lib/contrail_cloud/scripts/control-hosts-deploy.sh -c
/var/lib/contrail_cloud/scripts/inventory-assign.sh -c
  1. How do I get license keys to test in my lab
You can request for Contrail Cloud activation keys by sending an
e-mail to [email protected]

  1. Calculate CEPH PG

  2. Add new compute nodes

Update inventory.yml && run /var/lib/contrail_cloud/scripts/inventory-assign.sh
Update compute-nodes.yml with new nodes && run /var/lib/contrail_cloud/scripts/compute-nodes-assign.sh
Run /var/lib/contrail_cloud/scripts/openstack-deploy.sh
  1. Add new storage nodes
Update inventory.yml && run /var/lib/contrail_cloud/scripts/inventory-assign.sh
Update storage-nodes.yml with new nodes && run /var/lib/contrail_cloud/scripts/storage-nodes-assign.sh
Run /var/lib/contrail_cloud/scripts/openstack-deploy.sh
  1. Scale down compute nodes
Update compute-nodes.yml, under the compute which you want to remove with below line

status: "deleting"

Run /var/lib/contrail_cloud/scripts/compute-remove.sh
  1. Debugging Mistral
  • Run below commands on undercloud VM
source ~/stackrc
openstack workflow execution list | grep "ERROR" << Get UUID of the FAILED workflow execution
openstack workflow execution show <UUID>         << Failed Task
openstack workflow execution output show <UUID>
openstack workflow definition show <Task_Name>   << Provides full workflow definition
tailf /var/log/mistral/executor.log              << Log file
  1. Accessing deployment command history

Check file on undercloud VM

cat /home/stack/.tripleo/history
  1. Accessing logs for Baremetal node provisioning

Check logs on undercloud VM

sudo journalctl -u openstack-ironic-conductor -u openstack-ironic-api
  1. Check CEPH deployment logs

Check file on undercloud VM

tailf /var/log/mistral/ceph-install-workflow.log
  1. Reboot undercloud VM

Check if autostart is enabled for the undercloud, if not enable it

As contrail user on jumphost, `ssh undercloud sudo shutdown -h`
sudo virsh destroy undercloud
sudo shutdown -r 0
  1. Restart ironic services
sudo systemctl restart ironic-neutron-agent.service
sudo systemctl restart openstack-ironic-conductor.service
sudo systemctl restart openstack-ironic-inspector-dnsmasq.service
sudo systemctl restart openstack-ironic-inspector.service
  1. Set password for overcloud image for debugging purpose
virt-customize -a images/overcloud-full.qcow2 --root-password password:pass0123
  1. Move node from clean_failed to clean abort state
openstack baremetal node list
ironic --ironic-api-version 1.16 node-set-provision-state UUID abort
  1. Move node from clean_failed to manageable state
openstack baremetal node list
ironic node-set-maintenance UUID on
ironic --ironic-api-version 1.16 node-set-provision-state UUID abort
ironic node-set-maintenance UUID off
ironic node-set-provision-state UUID manage
  1. ccloud CLI extension
ssh undercloud
source stackrc
openstack ccloud nodemap hosts
openstack ccloud nodemap list
openstack ccloud nodemap show <host-name>
  1. Removing existing hosts from satellite
./satellite6hosts.py --user <key> --password <passwd> delete --host <host-fqdn-name>
  1. Idm commands
ipa user-find admin
ipa host-find --all

global
  dns: "192.168.213.1"

idm:
  enable: true
  otp: "9MdXwcTuGhart5d7EL9JrGoXEijh245NvqF5wyLUrBNm"
  #idm_server_ip - idm ip address
  idm_server_ip: "192.168.213.2"

Reference

CC13 Deployment Guide

vBMC

Ironic state diagram

Troubleshooting