📦
CHI-in-a-box
  • What is CHI-in-a-Box?
  • Before You Begin
    • Assumed Knowledge
    • Hosts and Services
    • Network Overview
    • CC-Ansible
    • The site configuration
      • inventory
      • defaults.yml
      • passwords.yml
      • certificates/
      • node_custom_config/ (optional)
      • post-deploy.yml (optional)
    • How Deployment Works
    • Security considerations
  • Setup Guides
    • Evaluation Site
      • Bring up the Control Plane
    • Production Baremetal
      • Baremetal QuickStart
      • Host Networking Configuration
    • Troubleshooting
      • Networking
    • Verification Checklist
    • Dev-in-a-Box
    • Edge-in-a-Box
  • Reference
    • Chameleon Identity Federation
    • Ironic Flat Networking
    • Ironic Multi-Tenant Networking
    • Glance Image Storage
    • Resource Reservation
      • Default Resource Properties
    • Monitoring
      • IPMI Metrics
      • SNMP Metrics
  • Example Deployments
    • ARM/x86 mixed architecture
    • Edge computing/container testbed
  • Operations
    • Hardware management
    • Certificate management
    • Chameleon tools
      • Hammers 🔨
        • maintenance_reservation
      • Disk image subscription
      • Usage reporting
    • Troubleshooting
      • Known issues
        • Neutron (networking)
        • Nova (KVM)
        • Ironic (bare metal)
      • Instance networking diagnostics
      • Security incident triage
      • Troublesome Hardware
    • Alert runbooks
      • Cron Job No Recent Success
      • Instance Failure
      • Image Cache Space
      • Ironic Node Error State
      • Jupyter Server Launch Failure
      • MySQL Host Down
      • MySQL Replication Error
      • Node Exporter Down
      • Node Network Bridge Down
      • Node Network Bridge Low Traffic
      • Nova Ironic Instance Launch Failure
      • OpenStack API Down
      • PeriodicTask No Recent Success
      • Portal Down
      • Precis Parsed Events Low
      • Provider Conflict
      • Runbook Template
    • User support guide
    • Upgrading to a new Release
  • Development
    • Developing OpenStack Services
    • Dev-in-a-box
Powered by GitBook
On this page
Edit on GitHub
  1. Operations
  2. Troubleshooting
  3. Known issues

Nova (KVM)

Can't rename a Nova hypervisor node

If the hostname on a Nova compute node changes, it can be very difficult to figure out how to "flush out" the old hostname. The system will cache it in some unexpected places. The following procedures should wipe it out. Importantly, existing service containers must be stopped and removed in order to prompt a recreate; otherwise the container will still have the hostname it was originally created with, which will be stale.

Ensure you have already set the hostname to its new value.

Run the following on the compute node:

for c in $(sudo docker container ls -a --filter name=nova --format "{{.Names}}"); do
  sudo docker stop $c && sudo docker rm $c
done

Run the following on the control node:

export OS_COMPUTE_API_VERSION=2.53
for uuid in $(openstack compute service list --service nova-compute -f value -c ID); do
  openstack compute service delete $uuid
  openstack resource provider delete $uuid
done

Finally, run the following on the deploy node:

./cc-ansible upgrade --tags nova
PreviousNeutron (networking)NextIronic (bare metal)

Last updated 2 years ago