Back to bug 1318436

Who When What Removed Added
Greg McCullough 2016-03-16 21:22:11 UTC Target Release 5.6.0 5.5.4
Component Automate Provisioning
Greg McCullough 2016-03-16 21:22:57 UTC Status NEW ASSIGNED
Assignee gmccullo bdunne
Chris Pelland 2016-03-17 18:42:48 UTC CC cpelland
Chris Pelland 2016-03-17 18:45:21 UTC Keywords ZStream
Satoe Imaishi 2016-03-18 20:42:28 UTC Status ASSIGNED MODIFIED
Target Release 5.5.4 5.5.3
CC simaishi
Marianne Feifer 2016-03-21 12:38:22 UTC CC mfeifer
Doc Text Cause: problem with the provision checks that run from the fact that the pxe has been ran (30 seconds, and the kickstart can't even run, there is no OS installed on the system, so the system does not have the time to run through the installation of the os before it reaches the wget callback to cloudforms.

Consequence: PXE provision booting up with missing pxe boot entry

Fix: changed code to Wait for the VM to be powered on in the provider


Result: Pxe boot entry added successfully.
Marianne Feifer 2016-03-21 12:39:09 UTC Flags needinfo?(bdunne)
Brandon Dunne 2016-03-21 13:46:35 UTC Doc Text Cause: problem with the provision checks that run from the fact that the pxe has been ran (30 seconds, and the kickstart can't even run, there is no OS installed on the system, so the system does not have the time to run through the installation of the os before it reaches the wget callback to cloudforms.

Consequence: PXE provision booting up with missing pxe boot entry

Fix: changed code to Wait for the VM to be powered on in the provider


Result: Pxe boot entry added successfully.
Cause: When PXE provisioning a VM, we write the PXE boot files, boot the VM, then wait for it to power off. The power off signifies that the installation has completed and the installer has 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.

Consequence: VM booting up for PXE install with missing PXE boot entry

Fix: changed code to Wait for the VM to be powered on in the provider

Result: We now wait for the VM to boot and shut down before cleaning up the PXE files.
Flags needinfo?(bdunne)
Brandon Dunne 2016-03-21 20:38:49 UTC Flags needinfo?(fdewaley)
errata-xmlrpc 2016-03-22 11:01:40 UTC Status MODIFIED ON_QA
John Prause 2016-03-22 12:33:51 UTC Fixed In Version 5.5.3.2
Felix Dewaleyne 2016-03-22 15:29:47 UTC Flags needinfo?(fdewaley)
Felix Dewaleyne 2016-03-22 17:30:33 UTC Flags needinfo?(bdunne)
Brandon Dunne 2016-03-23 18:36:45 UTC Flags needinfo?(bdunne)
dajohnso 2016-03-24 21:12:33 UTC QA Contact dajohnso kzvyahin
Dave Johnson 2016-03-28 14:24:56 UTC QA Contact kzvyahin sshveta
Shveta 2016-03-29 16:38:04 UTC Status ON_QA VERIFIED
Suyog Sainkar 2016-04-07 01:21:04 UTC CC ssainkar
Doc Text Cause: When PXE provisioning a VM, we write the PXE boot files, boot the VM, then wait for it to power off. The power off signifies that the installation has completed and the installer has 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.

Consequence: VM booting up for PXE install with missing PXE boot entry

Fix: changed code to Wait for the VM to be powered on in the provider

Result: We now wait for the VM to boot and shut down before cleaning up the PXE files.
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.
errata-xmlrpc 2016-04-13 03:46:39 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-04-13 18:46:21 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-04-13 14:46:21 UTC

Back to bug 1318436