Bug 824904
Summary: | Parameter mismatch in returned parameters caused deadlock | ||
---|---|---|---|
Product: | [Retired] CloudForms Cloud Engine | Reporter: | Chris Pelland <cpelland> |
Component: | aeolus-audrey-agent | Assignee: | Greg Blomquist <gblomqui> |
Status: | CLOSED ERRATA | QA Contact: | dgao |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.0.0 | CC: | akarol, cpelland, dajohnso, deltacloud-maint, dradez, gblomqui, hbrock, jliberma, jrd, sachua, scollier, sreichar, whayutin |
Target Milestone: | 1.0.1 | Keywords: | Rebase, Triaged, ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
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.
|
Story Points: | --- |
Clone Of: | 801861 | Environment: | |
Last Closed: | 2012-07-10 07:23:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 801861 | ||
Bug Blocks: |
Description
Chris Pelland
2012-05-24 14:48:17 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: 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. [root@dhcp77-213 ~]# rpm -qa | grep "aeolus-audrey" aeolus-audrey-agent-0.4.9-1.el6_2.noarch 2012-06-19 07:38:12,886 - INFO : audrey:951 Invoked CSClient.get_cs_tooling() 2012-06-19 07:38:12,929 - INFO : audrey:683 Invoked unpack_tooling() 2012-06-19 07:38:12,936 - INFO : audrey:908 Invoked CSClient.get_cs_configs() 2012-06-19 07:38:12,976 - INFO : audrey:1369 No configuration parameters provided. status: 202 . . . 2012-06-19 07:48:18,513 - INFO : audrey:908 Invoked CSClient.get_cs_configs() 2012-06-19 07:48:18,560 - INFO : audrey:1369 No configuration parameters provided. status: 202 Audrey agent exists after 10mins. Verified. 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. http://rhn.redhat.com/errata/RHBA-2012-1063.html |