The Bare Metal provisioning service now wipes a disk's metadata before partitioning and writing an image into it. This ensures that the new image boots normally. In previous releases, the Bare Metal provisioning service didn't remove old metadata before starting work on a device, which made it possible for a deployment to fail.
DescriptionGonéri Le Bouder
2016-02-22 21:56:42 UTC
Created attachment 1129508[details]
grub error silently ignored
Description of problem:
Ironic does not clean properly an existing partition table before the deployment and this create a conflict during the new partition creation.
Version-Release number of selected component (if applicable):
How reproducible:
1. Inject an image on the root disk, like ipxe.usb or ipxe.iso
2. Try to deploy a system on the node using Ironic
3. Deployment succeed
4. Node reboots and boot fails
Actual results:
Node should boot after deployment.
Expected results:
Additional info:
Hi! Ironic does clean the partition before deploying. Could you please provide ironic-conductor logs to see if something went wrong during this process?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHEA-2016-2948.html
Created attachment 1129508 [details] grub error silently ignored Description of problem: Ironic does not clean properly an existing partition table before the deployment and this create a conflict during the new partition creation. Version-Release number of selected component (if applicable): How reproducible: 1. Inject an image on the root disk, like ipxe.usb or ipxe.iso 2. Try to deploy a system on the node using Ironic 3. Deployment succeed 4. Node reboots and boot fails Actual results: Node should boot after deployment. Expected results: Additional info: