Skip to content

Troubleshooting the install

Symptom Fix
The machine boots the installer again after the install The stick is still in, or first in the boot order. Remove it, or choose Stratum (disk 1) in the firmware’s boot menu.
A disk is refused The message names the reason and the fix. A disk without a hardware ID cannot be used; in a VM, give it a serial number.
The install failed The screen shows the failed step and the tool’s output. enter goes back to the review to try again. The screen says what state the disks are in; l shows the log.
The review refuses a disk that holds an old install The wipe of the other disks is on by default. If you turned it off with w, turn it on again, or wipe the disk yourself.
A static address is refused Another host answers for it: the screen names its MAC. Choose another address.
  • Wait a minute or two after boot: the release images load first.

  • On the node’s console:

    Terminal window
    systemctl status stratum-payload-load stratum-installer
    journalctl -u stratum-payload-load -u stratum-installer -b
  • The management NIC has no IPv4 address: check ip addr and nmcli connection show oob. The service waits up to 5 minutes for one, then tries again, so it keeps waiting.

  • From the workstation: the address is right, and port 9443/tcp is open in the firewall zone of that NIC (firewall-cmd --get-active-zones).

  • The release images did not load: stratum-installer payload load on the node loads them again and prints what failed.

Message Fix
401 INSTALL_CODE_WRONG The code changes at every boot. Read it again on the console, or cat /run/stratum-installer/install-code on the node.
429 TOO_MANY_ATTEMPTS Too many wrong codes: wait for the time given (up to 5 minutes).
not the pinned fingerprint The node’s address changed and it made a new certificate, or the target is another machine. Read the fingerprint on the console again.

stratum-installer report gives the failed step, named as a person would say it (“Preparing storage”), and the error. On a single node a re-run is safe: fix the configuration (config set or apply) and run stratum-installer install again, or use Retry install in the web installer. If the install finished but the cloud was not ready in time, stratum-installer recheck-readiness waits again without installing. To report a problem, stratum-installer diagnostics -o diagnostics.tgz saves the logs, the report and the hardware, with secrets removed.

What Where on the node
Stage 1’s log, kept from the install medium /var/log/stratum/install-stage1.log
The full install log /var/log/stratum/install.log
The install job journalctl -u stratum-installer-job.service
The install service journalctl -u stratum-installer
Loading the release images journalctl -u stratum-payload-load
  • A failed stage 2: change the configuration and install again. No reinstall is needed.
  • Anything else, including a finished install: boot the ISO and install again. The old disks hold data, so the installer asks you to confirm: each OS disk by name, and the other disks with one phrase (wipe 3 disks). The other disks, such as the other half of an old mirror, are wiped by default.