Back to bug 801861

Who When What Removed Added
wes hayutin 2012-03-12 20:02:28 UTC CC whayutin
wes hayutin 2012-04-30 16:34:42 UTC Severity unspecified high
Hugh Brock 2012-05-07 15:20:58 UTC Keywords Triaged
CC hbrock
Hugh Brock 2012-05-08 17:02:15 UTC Flags needinfo?(gblomqui)
Greg Blomquist 2012-05-11 14:37:55 UTC Status NEW ASSIGNED
Assignee gblomqui dradez
Flags needinfo?(gblomqui)
Dan Radez 2012-05-24 02:21:37 UTC Status ASSIGNED VERIFIED
Dan Radez 2012-05-24 02:22:08 UTC Status VERIFIED ON_QA
wes hayutin 2012-05-24 13:07:21 UTC CC dajohnso
Greg Blomquist 2012-05-24 13:46:12 UTC CC gblomqui
Flags needinfo?(whayutin)
Chris Pelland 2012-05-24 14:47:04 UTC Keywords ZStream
CC cpelland
Chris Pelland 2012-05-24 14:48:17 UTC Blocks 824904
Dan Macpherson 2012-05-29 05:18:25 UTC CC dmacpher
Dan Radez 2012-05-31 19:38:22 UTC Component aeolus-configserver aeolus-audrey-agent
Assignee dradez gblomqui
QA Contact dgao aeolus-qa-list
Dan Radez 2012-06-05 13:36:52 UTC CC dradez
Assignee gblomqui dradez
Dan Radez 2012-06-11 13:39:01 UTC Flags needinfo?(whayutin) needinfo+
Alexandra 2012-11-19 04:09:06 UTC Status ON_QA VERIFIED
CC dgao
CC asettle
Doc Text A faulty application blueprint can lock instances in a boot state. For example an application blueprint with a mistyped parameter name fails due to Audrey Configuration Server being unable to find the correct runtime configuration settings. The Audrey Configuration Server uses a ten minute timeout to bypass any errors with application blueprints. This allows the instances to boot without runtime configuration. Ensure to verify all application blueprints before launch to avoid this issue. A faulty Application Blueprint was locking instances in a boot state.
For example an Application Blueprint with a mistyped parameter name failed due to Audrey Configuration Server being unable to find the correct runtime configuration settings.
This bug fix enables Audrey Configuration Server to use a ten minute time-out to bypass any errors with Application Blueprints. This allows the instances to boot without runtime configuration. Ensure to verify all Application Blueprints before launch to avoid this issue.
Dan Macpherson 2012-11-28 16:06:15 UTC Doc Text A faulty Application Blueprint was locking instances in a boot state.
For example an Application Blueprint with a mistyped parameter name failed due to Audrey Configuration Server being unable to find the correct runtime configuration settings.
This bug fix enables Audrey Configuration Server to use a ten minute time-out to bypass any errors with Application Blueprints. This allows the instances to boot without runtime configuration. Ensure to verify all Application Blueprints before launch to avoid this issue.
A faulty Application Blueprint locked instances in a boot state. For example an Application Blueprint with a mistyped parameter name failed due to Audrey Configuration Server being unable to find the correct runtime configuration settings. This bug fix enables Audrey Configuration Server to use a ten minute time-out to bypass any errors with Application Blueprints. This allows the instances to boot without runtime configuration. Ensure to verify all Application Blueprints before launch to avoid this issue.
errata-xmlrpc 2012-12-04 01:06:55 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2012-12-04 14:58:26 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2012-12-04 09:58:26 UTC

Back to bug 801861