Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 916457

Summary: caroniad:1030:main:IndexError: list index out of range
Product: Red Hat Enterprise MRG Reporter: Stanislav Graf <sgraf>
Component: condor-ec2-enhancedAssignee: grid-maint-list <grid-maint-list>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.3CC: ltoscano, matt, rrati
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-26 20:03:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stanislav Graf 2013-02-28 06:09:14 UTC
Description of problem:
On 2 machines I can see:
-----
Subject: [Condor] Problem hostname: caroniad
 exited (1)
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

This is an automated email from the Condor system
on machine "hostname".  Do not reply.

"/usr/sbin/caroniad" on "hostname" exited with status 1.
Condor will automatically restart this process in 10 seconds.

*** Last 20 line(s) of file /var/log/condor/CaroniaLog:
02/27 19:08:21 INFO: Starting up
02/27 19:26:04 INFO: Starting up
02/27 19:43:44 INFO: Starting up
02/27 20:01:25 INFO: Starting up
02/27 20:19:08 INFO: Starting up
02/27 20:36:48 INFO: Starting up
02/27 20:54:31 INFO: Starting up
02/27 21:12:13 INFO: Starting up
02/27 21:29:56 INFO: Starting up
02/27 21:47:36 INFO: Starting up
02/27 22:05:19 INFO: Starting up
02/27 22:23:01 INFO: Starting up
02/27 22:40:44 INFO: Starting up
02/27 22:58:27 INFO: Starting up
02/27 23:16:09 INFO: Starting up
02/27 23:33:52 INFO: Starting up
02/27 23:51:34 INFO: Starting up
02/28 00:09:17 INFO: Starting up
02/28 00:26:59 INFO: Starting up
02/28 00:44:40 INFO: Starting up
*** End of file CaroniaLog
-----

And on one machine there is additional crash:
-----
Subject: [abrt] full crash report
Message-ID: <512eeed4.MX6gpjLhu80/1Msm%user@localhost>
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

abrt_version:   2.0.8
cmdline:        /usr/bin/python /usr/sbin/caroniad
executable:     /usr/sbin/caroniad
kernel:         2.6.32-358.0.1.el6.i686
time:           Thu 28 Feb 2013 12:44:40 AM EST
uid:            0
username:       root

sosreport.tar.xz: Binary file, 502300 bytes

backtrace:
:caroniad:1030:main:IndexError: list index out of range
:
:Traceback (most recent call last):
:  File "/usr/sbin/caroniad", line 1158, in <module>
:    sys.exit(main())
:  File "/usr/sbin/caroniad", line 1030, in main
:    file.write(base64.decodestring(user_data[1]))
:IndexError: list index out of range
:
:Local variables in innermost frame:
:argv: ['/usr/sbin/caroniad']
:listen_socket: None
:log_name: 'caroniad'
:debug_logging: False
:private_key_file: '/root/.ec2/rsa_key'
:share_data: None
:args: []
:sock: None
:user_data: ['']
:conf_file: '/etc/condor/caroniad.conf'
:base_logger: <logging.Logger instance at 0x95a4f6c>
:pidfile: ''
:file: <open file '/root/data', mode 'w' at 0x9578a70>
:daemon_mode: 0
:opts: []
:size: 1000000
-----

Version-Release number of selected component (if applicable):
# rpm -qf /usr/sbin/caroniad
condor-ec2-enhanced-1.3.0-1.el6.noarch

How reproducible:
I don't know.

Steps to Reproduce:
1. It was in my logfile after doing install/upgrade/downgrade tests
  
Actual results:
"/usr/sbin/caroniad" on "hostname" exited with status 1.
caroniad:1030:main:IndexError: list index out of range

Expected results:
no exiting with status 1
no crash

Additional info:

Comment 1 Luigi Toscano 2013-02-28 10:35:05 UTC
Maybe related/connected to https://bugzilla.redhat.com/show_bug.cgi?id=783464 ? If I understand it correctly it's the same case (caroniad running on a non-AMI), and it does not handle gracefully the shutdown. But in this case it seems that the caroniad is (correctly?) restarting over and over as it can't contact the EC2 services, while in the other bug the stack trace came from a signal from condor_master because caroniad was "stale" without restarting.

Comment 2 Anne-Louise Tangring 2016-05-26 20:03:58 UTC
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.