Customer tries to add a node to a hosted cluster using Infrastructure operator (AKA). 
- The agent is added manually with a live ISO, the agent is created, it is approved; however, in phase 5/9, after reboot, it seems to lose the IP address that is created in the nmstate config and gets stuck in a loop reaching ignition.    

- OCP --> 4.17
- ACM --> v2.12.2
- MCE --> v2.7.3    

1. The nmstateconfig has a label configured that correctly points to the infraenv.
2. The customer is adding a host through “Host Inventory”.
   - “Add Host” under wave1 infraenv
   - Discover using ISO
   - Downloaded ISO and boot the baremetal node with the ISO
3. The host booted with the ISO and has the proper bond configured. 
4. The customer approved the node, and it became available.
5. The customer increase the nodepool from ACM web console. It process further until 5/9(rebooting) 
6. Node rebooted, but when it came up, it was throwing the ignition error 7. In the error, it seems it was not able to reach its own DNS:
---
dial tcp: lookup ignition-server-wave1-wave1.apps.hubtst.test.hcscint.net on [::1]:538. 
---
8. The node was not pingable. It seems it lost the network config.    

    1.
    2.
    3.