Bug 1318436 - PXE provision booting up with missing pxe boot entry
Summary: PXE provision booting up with missing pxe boot entry
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.5.0
Hardware: All
OS: All
unspecified
high
Target Milestone: GA
: 5.5.3
Assignee: Brandon Dunne
QA Contact: Shveta
URL:
Whiteboard:
Depends On: 1318019
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-16 21:21 UTC by Greg McCullough
Modified: 2019-10-10 11:34 UTC (History)
12 users (show)

Fixed In Version: 5.5.3.2
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Management Engine, the VM booted up for PXE install with missing PXE boot entry. This was because when PXE provisioning a VM, we wrote the PXE boot files, boot the VM, then wait for it to power off. The power off signified that the installation was complete and the installer shut down the guest. Sometimes providers are slow enough that we can request the power on, refresh the provider (a very heavy operation for collecting the power state of the new VM), and the VMs power state is off because it has not yet powered on. The state machine logic has changed to now only look at the power state on the provider (much faster), and sit in a loop waiting for the VM to boot before moving on to the next "wait_for_power_off" state. This fix changes the code to wait for the VM to be powered on in the provider. As a result, we now wait for the VM to boot and shut down before cleaning up the PXE files.
Clone Of: 1318019
Environment:
Last Closed: 2016-04-13 18:46:21 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
hotfix bz1318436.tar (21.00 KB, application/x-tar)
2016-03-17 20:51 UTC, Greg McCullough 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0616 0 normal SHIPPED_LIVE CFME 5.5.3 bug fixes and enhancement update 2016-04-13 22:38:44 UTC

Comment 1 Greg McCullough 2016-03-17 20:51:11 UTC 
Created attachment 1137511 [details]
hotfix bz1318436.tar
Comment 5 Brandon Dunne 2016-03-21 20:38:49 UTC 
It looks like there may be some other issue affecting us...
[----] E, [2016-03-21T13:33:36.761454 #2829:ca7998] ERROR -- : Q-task_id([miq_provision_5000000000930]) <AutomationEngine> Method exec failed because (Errno::EMFILE:Too many open files)

Are there too many files open on the system?
Comment 7 Felix Dewaleyne 2016-03-22 15:29:47 UTC 
(In reply to Brandon Dunne from comment #5)
> It looks like there may be some other issue affecting us...
> [----] E, [2016-03-21T13:33:36.761454 #2829:ca7998] ERROR -- :
> Q-task_id([miq_provision_5000000000930]) <AutomationEngine> Method exec
> failed because (Errno::EMFILE:Too many open files)
> 
> Are there too many files open on the system?

that didn't seem to happen after he restored the vmdb. are we sure this isn't caused by the patch?
Comment 9 CFME Bot 2016-03-22 20:55:44 UTC 
https://github.com/ManageIQ/manageiq/pull/7483
Comment 11 Shveta 2016-03-29 16:38:04 UTC 
Verified PXE provisioning .
Vm is provisioned successfully.
Build : 5.5.3.2.20160318152106_92d2d67
Comment 13 errata-xmlrpc 2016-04-13 18:46:21 UTC 
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-2016:0616
Note You need to log in before you can comment on or make changes to this bug.