OKD 4.22 IPI on OpenStack generates cloud-init instead of Ignition JSON (bootstrap fails)

[dennyboy73]

Describe the bug

When deploying OKD 4.22 on OpenStack 2025.1 using IPI, the installer generates a cloud-init file (#cloud-config) instead of a proper Ignition JSON file for the bootstrap VM. The file is only 162 bytes (should be ~300KB) and starts with #cloud-config instead of {.

As a result, the bootstrap VM never starts the control plane. It sits at a login prompt and bootkube.service never starts. The installation times out waiting for the Kubernetes API.

Error from logs:
text

error at line 1 col 2: invalid character '#' looking for beginning of value
failed to fetch config: config is not valid
Ignition failed: config is not valid

Expected:
json

{
"ignition": {
"version": "3.2.0"
},
...
}

Actual:
yaml

#cloud-config
users:

• name: core
  ssh_authorized_keys:
  • ssh-rsa AAAAB3NzaC1yc2EAAA...

Version

OKD: 4.22.0-okd-scos.0 OpenStack: 2025.1 Epoxy (Kolla-Ansible) Install method: IPI (OpenStack)

Reproducibility

100% - reproducible every time on this OpenStack environment.

Log Bundle

Full logs available upon request. I can provide:

Bootstrap VM console log

install-config.yaml

bootstrap.ign (invalid file)

nova-compute.log

neutron logs