Installing a baremetal IPI without provisoningNetwork still initiates "provisioning-interface.service". The cluster gets created fine, but it should not throw the error as it makes confusion.

    always

    1. Deploy a baremetal IPI without provisioningNetwork 
    2. Error appears in the journal
    3.
    

    Error appers in the journal

    When deploying without provisionNetwork, it should not initiate the provisioning-interface.service. 

install-config.yaml:

platform:
  baremetal:
    apiVIP: 10.10.10.55
    ingressVIP: 10.10.10.56
    provisioningNetwork: "Disabled"  <=======
    bootstrapExternalStaticIP: 10.10.10.57
    bootstrapExternalStaticGateway: 10.10.10.1
    bootstrapExternalStaticDNS: 10.50.135.251


Jouranctl:


Mon 2024-04-08 13:56:35 UTC api.test.test init.scope[1]: provisioning-interface.service: Scheduled restart job, restart counter is at 488.
Mon 2024-04-08 13:56:35 UTC api.api.test.test init.scope[1]: Stopped Provisioning interface.
Mon 2024-04-08 13:56:35 UTC api.api.test.test init.scope[1]: Starting Provisioning interface...
Mon 2024-04-08 13:56:35 UTC api.api.test.test provisioning-interface.service[39819]: Error: failed to modify ipv4.addresses: invalid IP address: Invalid IPv4 address ''.
Mon 2024-04-08 13:56:35 UTC api.api.test.test init.scope[1]: provisioning-interface.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Mon 2024-04-08 13:56:35 UTC api.api.test.test init.scope[1]: provisioning-interface.service: Failed with result 'exit-code'.
Mon 2024-04-08 13:56:35 UTC api.api.test.test init.scope[1]: Failed to start Provisioning interface.