Running custom IPA in an environment where thereis no DHCP - preprovisioning image

[agewagra]

Metal3 docs mentions that preprovisioning image is used to add preprovisioning network data to bmh. This enables each host to use its own deploy ramdisk image customised with an appropriate network configuration.

Docs:
https://github.com/metal3-io/metal3-docs/blob/main/design/baremetal-operator/image-builder-integration.md

What is expected to happen:
The network data should be applied on the baremetal server in the inspecting phase with IPA.

Issue:
IPA is still waiting for DHCP to assign an IP to the server. We confirmed that the network data is added in the iso image in the /openstack/latest/network_data.json. But there is no way to disable waiting for DHCP from IPA.

Is there any way to disable DHCP or generate customized initramfs and kernel files from the source code of IPA by disabling DHCP?

[metal3-io-bot]

This issue is currently awaiting triage.
If Metal3.io contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Rozzii]

Please take a look of my comment on the related Issue: metal3-io/baremetal-operator#1664 (comment)
/triage needs-information

[agewagra]

Duplicate of this issue : metal3-io/baremetal-operator#1664