Troubleshooting
Installation
Section titled “Installation”| Symptom | Cause and fix |
|---|---|
no published RPM release is pinned |
the checkout is older than the tag rocky10.2-rpms-2026.1. Clone the release tag, or use --rpm-source build or --repo-url |
| The download or a verification fails | nothing was installed. Check the network and re-run; it never switches to building |
Switching the package set of a running cloud is an upgrade |
the host was deployed from another RPM set. HAGISTACK does not upgrade |
A warning that delorean-component-* repositories are enabled |
disable them: dnf config-manager --set-disabled 'delorean-component-*'. Otherwise the install is no longer one release |
It stops without an error: line |
the last ==> line of the output is the phase that failed |
INCOMPLETE — these phases were skipped |
fix the cause shown for those phases and re-run |
Horizon cannot be reached
Section titled “Horizon cannot be reached”-
The URL is
http://MGMT_IP/dashboard/(the trailing/dashboard/is needed). -
Check httpd on the controller:
Terminal window systemctl status httpdcurl -s -o /dev/null -w '%{http_code}\n' http://MGMT_IP/dashboard/auth/login/200means Horizon answers. -
Check that the browser reaches port 80 of the management IP. With
firewalldactive, open 80/tcp (HAGISTACK configures no firewall). -
The password is
OS_PASSWORDin/etc/hagistack/admin-openrc. -
sudo ./tests-horizon-login.shchecks the sign-in from the command line.
A VM does not boot (ERROR)
Section titled “A VM does not boot (ERROR)”openstack server show VM_NAME -c status -c faultopenstack compute service listopenstack hypervisor listfault |
Fix |
|---|---|
No valid host was found |
no running compute service, or not enough free resources. Check that nova-compute is up. A controller alone cannot boot VMs until a compute node is added |
Refusing to bind port … no OVN chassis for host |
the Nova host name and the OVN chassis name disagree. Make every host name unique and stable, then re-run |
Logs on the compute node:
journalctl -u openstack-nova-compute -n 200journalctl -u neutron-ovn-metadata-agent -n 100SSH does not connect
Section titled “SSH does not connect”-
Is the VM
ACTIVE? -
Did cloud-init get the key? Check the boot log:
Terminal window openstack console log show VM_NAME | tail -40 -
Does the security group have an ingress rule for TCP 22 (Your first VM)?
-
Check the path. A floating IP is not reachable from the physical LAN as it is: connect to the tenant address from the metadata namespace, or give the host’s
br-exthe gateway address (Your first VM). -
The user is
cirros, the key/etc/hagistack/hagistack-key.
Adding a compute node
Section titled “Adding a compute node”See the troubleshooting for adding a compute node.
Collecting information
Section titled “Collecting information”When you report a problem, include no passwords or keys. Do not share admin-openrc, secrets.env, compute-secrets.env or hagistack-key.
sudo ./hagistack statusjournalctl -u UNIT_NAME -n 200 --no-pager