[OCP 4.12] no ignition embedded on node inspection of baremetal node

Node booted for inspection doesn't present the static network configuration set neither is possible to access it using ssh using the cluster key. Also appears on the login screen the message "Ignition: no config provided by user":

~~~
Red Hat Enterprise Linux CoreOS 412.86.202308081039-0 (Ootpa) 4.12
Ignition: ran on 2024/03/12 10:36:51 UTC (this boot)
Ignition: no config provided by user.[0m
SSH host key: SHA256:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA (ECDSA)
SSH host key: SHA256:BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB (ED25519)
SSH host key: SHA256:CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC (RSA)
ens5f0: 192.168.0.100 fe80::0000:0000:000:1001
ens5f1: 192.168.0.10 fe80::0000:0000:000:2001
localhost login:
~~~

Openshift 4.12.35

Always in this cluster, but not able to reproduce on a lab

    1. Deploy bmh with this template:
~~~
apiVersion: v1
kind: Secret
metadata:
 name: worker1-network-config-secret
 namespace: openshift-machine-api
type: Opaque
stringData:
  nmstate: |
    interfaces:
    - name: ens5f0
      type: ethernet
      state: up
      ipv4:
        enabled: false
    - name: ens5f0.2
      type: vlan
      state: up
      vlan:
        base-iface: ens5f0
        id: 2
      ipv4:
        address:
        - ip: 192.168.0.25
          prefix-length: 26
        enabled: true
    dns-resolver:
      config:
        server:
        - 192.168.0.2
    routes:
      config:
      - destination: 0.0.0.0/0
        next-hop-address: 192.168.0.1
        next-hop-interface: ens5f0.2
---
apiVersion: v1
kind: Secret
metadata:
  name: worker1-bmc-secret
  namespace: openshift-machine-api
type: Opaque
data:
  username: AAAAA(in base64)
  password: BBBBB(in base64)
---
apiVersion: metal3.io/v1alpha1
kind: BareMetalHost
metadata:
  name: worker1
  namespace: openshift-machine-api
spec:
  online: True
  bootMACAddress: 00:11:22:33:44:55
  bootMode: legacy
  bmc:
    address: ipmi://192.168.1.41
    credentialsName: worker1-bmc-secret
    disableCertificateVerification: True
  rootDeviceHints:
    deviceName: "/dev/sda"
  preprovisioningNetworkDataName: worker1-network-config-secret
~~~

     2. Fail
    3.
    

Provision failed with timeout    

Node provisioned as expected

There is a catch of the node boot logs using a redirection of the journal and the rd logs directly to the console and then a redirection of this through a serial port and to a file (worker-1-boot.logs).
Also cluster must-gather is available.