Bug 475586
Summary: | amazon_gahp fails when user data file is empty | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Robert Rati <rrati> |
Component: | grid | Assignee: | Matthew Farrellee <matt> |
Status: | CLOSED ERRATA | QA Contact: | Jeff Needle <jneedle> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 1.0 | CC: | matt |
Target Milestone: | 1.1 | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-02-04 16:06:24 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: |
Description
Robert Rati
2008-12-09 18:05:52 UTC
gahp-client.cpp:303 will EXCEPT the gridmanager is the gahp it is communicating with crashes, which is happening here. Interesting part of the log is why the gahp is crashing, apparently a seg fault with the stack... 12/9 12:54:44 [16937] (3033.0) gm state change: GM_CREATE_KEYPAIR -> GM_START_VM 12/9 12:54:44 [16937] GAHP[16951] <- 'AMAZON_VM_START 14 /tmp/cert-B4R2HOPR74CAW5EGDKWTQEUND6EX6Y2G.pem /tmp/pk-B4R2HOPR74CAW5EGDKWTQEUND6EX6Y2G.pem ami-6240a40b SSH_north-08.lab.bos.redhat.com,north-14.lab.bos.redhat.com,north-15.lab.bos.redhat.com_ha-schedd@#3033.0#1228845269 NULL /tmp/aws-keys-19528 m1.small' 12/9 12:54:44 [16937] GAHP[16951] -> 'S' 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> Stack dump for process 16951 at timestamp 1228845284 (12 frames) 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp(dprintf_dump_stack+0xc0)[0x588d33] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp[0x589006] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /lib64/libpthread.so.0[0x308ca0de70] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp[0x4e8f8f] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp(AmazonVMStart::gsoapRequest()+0x3a8)[0x4eac66] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp(AmazonRequest::SendRequest()+0x57)[0x4e58a3] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp(AmazonVMStart::workerFunction(char**, int, MyString&)+0x39e)[0x4e74ba] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp(executeWorkerFunc(char const*, char**, int, MyString&)+0x8e)[0x4e209c] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp[0x4de743] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /usr/sbin/amazon_gahp[0x4df0d0] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /lib64/libpthread.so.0[0x308ca062f7] 12/9 12:54:44 [16937] GAHP[16951] (stderr) -> /lib64/libc.so.6(clone+0x6d)[0x33cf8d1b6d] The amazon_gahp will index an array at -1 when the user data file is empty. This is fixed for 7.2.0-0.10. To reproduce you need a valid cert and pk. # amazon_gahp $GahpVersion 0.0.2 Feb 15 2008 Condor\ AMAZONGAHP $ AMAZON_VM_START 0 /tmp/cert-B4R2HOPR74CAW5EGDKWTQEUND6EX6Y2G.pem /tmp/pk-B4R2HOPR74CAW5EGDKWTQEUND6EX6Y2G.pem ami-ID KEY NULL /dev/null TYPE S Stack dump for process 6116 at timestamp 1228864098 (12 frames) amazon_gahp(dprintf_dump_stack+0xc0)[0x588d33] amazon_gahp[0x589006] /lib64/libpthread.so.0[0x308ca0de70] amazon_gahp[0x4e8f8f] amazon_gahp(_ZN13AmazonVMStart12gsoapRequestEv+0x3a8)[0x4eac66] amazon_gahp(_ZN13AmazonRequest11SendRequestEv+0x57)[0x4e58a3] amazon_gahp(_ZN13AmazonVMStart14workerFunctionEPPciR8MyString+0x39e)[0x4e74ba] amazon_gahp(_Z17executeWorkerFuncPKcPPciR8MyString+0x8e)[0x4e209c] amazon_gahp[0x4de743] amazon_gahp[0x4df0d0] /lib64/libpthread.so.0[0x308ca062f7] /lib64/libc.so.6(clone+0x6d)[0x33cf8d1b6d] Segmentation fault (core dumped) An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0036.html |