Bug 1277593 - RFE: ironic should take care of setting PXE boot enabled by default on physical nodes
Summary: RFE: ironic should take care of setting PXE boot enabled by default on physic...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ga
: 9.0 (Mitaka)
Assignee: Lucas Alvares Gomes
QA Contact: Toure Dunnon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-03 15:45 UTC by Nicolas Auvray
Modified: 2023-09-14 03:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-13 12:42:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Nicolas Auvray 2015-11-03 15:45:39 UTC
Description of problem:

This is feedback from customer. When deploying a large amount of machines, it could be a real pain to make sure that every node has PXE boot configured by default. Maybe ironic should take care of this through pxe_idrac and pxe_ipmitool driver automatically, rather than setting it up on all nodes manually.


Version-Release number of selected component (if applicable):

python-ironicclient-0.5.1-11.el7ost.noarch


Actual results:

We have to connect to every console manually to change the boot order.


Expected results:

We should have the ability to tell ironic about the configuration of the boot order by default for all nodes.

Comment 2 Lucas Alvares Gomes 2015-11-10 08:56:47 UTC
Ironic already sets the boot mode to PXE (or CDROM in case of virtual media) before starting the deployment (this is done via the management interface). If it's not working then it's a bug.

Comment 3 Lucas Alvares Gomes 2016-05-19 09:54:44 UTC
Hi Nicolas,

Can you elaborate it a bit more? What you mean by "PXE boot configured by default" ? Because Ironic do change the boot device accordingly when deploying a node.

Do you mean something like network boot being disabled in the BIOS/EFI ?!

Comment 5 Angus Thomas 2016-07-13 12:42:21 UTC
I'm closing this, since it hasn't been possible to provide further updates since May. 

If the bug recurs, and can be described in more detail, please re-open this BZ.

Comment 6 Red Hat Bugzilla 2023-09-14 03:12:20 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.