Description of problem: Many distros create and distribute images based on the v1.0.0 code from iPXE (stable release). This version does not support the --autofree flag that we use in our boot.ipxe template and the boot will fail. Version-Release number of selected component (if applicable): How reproducible: Always if using an stable release of the iPXE image Steps to Reproduce: 1. Copy a iPXE ROM built from the v1.0.0 tag to the tftp directory 2. Boot an image 3. Actual results: Boot will fail when iPXE try to chainload to the linux kernel Expected results: Boot to succeed Additional info: While using --autofree may be a good practice (it frees the image after chainloading) it's not mandatory and by removing it we will get a much support for people using the stable version of iPXE and it will continue to work with the images built from the master.
NEEDINFO: Lucas This bug is marked for inclusion in RHBA-2015:21553 [1] but does not currently contain draft documentation text. To ensure the timely release of this advisory, please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field. For further information on this process, refer to "Describing Errata Release and Technical Notes for Engineers" [2]. Thank you for your assistance! [1] https://errata.devel.redhat.com/advisory/21553 [2] https://engineering.redhat.com/docs/en-US/Policy/70.ecs/html/Describing_Errata_Release_and_Technical_Notes_for_Engineers/index.html
Hi Lucinda, I think that it would be good to include this bug in the advisory text as far as I understand it (do we have a guide about what should be included and what not ? ).
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://access.redhat.com/errata/RHBA-2015:1864