Only relevant logs provided here for the sake of brevity). Ironic Python Agent: (I can provide the full log on request. ![]() =Ironic conductor (power-on) 13:07:18.541 INFO Successfully set node ea6f8eda-402c-4fb0-a2c4-61c83bc73f97 power state to power on by rebooting.Ġ20-02-18 13:07:18.560 INFO Node ea6f8eda-402c-4fb0-a2c4-61c83bc73f97 moved to provision state "wait call-back" from state "deploying" target provision state is "active" =Ironic conductor (before power-on) 13:06:33.261 DEBUG iDeploy boot mode is uefi for ea6f8eda-402c-4fb0-a2c4-61c83bc73f97 Here are the important snippets from the ironic conductor and the IPA that I've managed to narrow down. Lately, I'm having this weird "Failed to create config drive on disk" issue and it is happening only with BIOS images on certain baremetal nodes. Our approach so far is to configure all the baremetal nodes in CSM UEFI mode so that both BIOS and UEFI images can be run.Īnd things have worked fairly well with this. We have a medium-large ironic installation where the baremetal nodes are constantly doing provisionings and deprovisionings.We test a variety of images (Ubuntu, RedHat, Windows, etc.) in both BIOS and UEFI modes. I'd very much appreciate some help on this. ![]() Next message (by thread): Fw: : Failed to create config drive on disk.Previous message (by thread): proposal to make Kevin Carter core.: Failed to create config drive on disk fsbiz at fsbiz at
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |