| Summary: | Parameter mismatch in returned parameters caused deadlock | |||
|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Steve Reichard <sreichar> | |
| Component: | aeolus-audrey-agent | Assignee: | Dan Radez <dradez> | |
| Status: | CLOSED ERRATA | QA Contact: | Rehana <aeolus-qa-list> | |
| Severity: | high | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 1.0.0 | CC: | akarol, asettle, cpelland, dajohnso, deltacloud-maint, dgao, dmacpher, dradez, gblomqui, hbrock, jliberma, scollier, whayutin | |
| Target Milestone: | rc | Keywords: | Triaged, ZStream | |
| Target Release: | --- | Flags: | dradez:
needinfo+
|
|
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 824904 (view as bug list) | Environment: | ||
| Last Closed: | 2012-12-04 14:58:26 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 824904 | |||
|
Description
Steve Reichard
2012-03-09 16:51:49 UTC
multi-instance not supported in 1.0 kicking off Greg, we are considering this for Z -- how hard is it to fix? The zstream-able fix here is to force audrey-agent to bail after X number of tries at resolving parameters. Dan Radez claims that this is a low LOE in the 1.0 codebase for Audrey. I'll trust his claim, since he has a much better grasp of that code that I do. Assigned to Dan to patch this for zstream. fixed in b2ff50ae2a4a1b123b96ce18dd7b370bb2fe78bd this add a counter that will bail after a count of apx 10 mins one more update in e3981fd5faf8f304e096d9620628b8ff73463b9b agent version 0.4.8 (In reply to comment #4) > fixed in b2ff50ae2a4a1b123b96ce18dd7b370bb2fe78bd > this add a counter that will bail after a count of apx 10 mins Need some doc to reflect the 10 min timeout. Wes, should the docs to reflect 10min timeout be in the form of release notes (i.e., tech notes in BZ)?
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/RHEA-2012-1516.html |