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

Bug 518236

Summary:	EC2E generated queue names too long
Product:	Red Hat Enterprise MRG	Reporter:	Robert Rati <rrati>
Component:	condor-ec2-enhanced-hooks	Assignee:	Robert Rati <rrati>
Status:	CLOSED ERRATA	QA Contact:	Luigi Toscano <ltoscano>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.1	CC:	lbrindle, ltoscano, matt
Target Milestone:	1.2
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Grid bug fix C: EC2E uses a number of elements to generate a queue name, one of which has an unlimited ID length. SQS queues have a limit of 80 characters. C: It is possible that some ID numbers could use all of the allowed SQS name. F: Names of SQS queues are now auto-generated and use the described structure, which never exceed the 80-character limit. R: The limit can no longer be over-run EC2E uses a number of elements to generate a queue name, one of which has an unlimited ID length. SQS queues have a limit of 80 characters. It is possible that some ID numbers could use all of the allowed SQS name. Names of SQS queues are now auto-generated and use the described structure, which never exceed the 80-character limit.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-03 09:19:12 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:
Bug Blocks:	527551

Description Robert Rati 2009-08-19 15:50:54 UTC

Description of problem:
EC2E uses a number of elements to generate a queue name, one of which is the GlobalJobId from condor.  This ID effectively has no limits as it is partially comprised of user id and FQDN of the schedd.  SQS queues have a limit of 80 chars, so it's possible the GlobalJobId will use up all the SQS name allowed.

Suggest changing from:
<AWS_ID>-<route_queue_name>-<GlobalJobId>[-status]

To:

<AWS_ID>-<ClusterId>-<ProcId>-<QDate>[-status]

Remove the route_queue_name for the time being, as it is really only needed for N:1 functionality.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Robert Rati 2009-08-19 16:55:52 UTC

Fixed in:
condor-ec2-enhanced-hooks-1.0-19

Comment 3 Irina Boverman 2009-10-29 14:29:51 UTC

Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
please see bug summary.

Comment 4 Luigi Toscano 2009-11-05 14:26:36 UTC

Names of SQS queues are now auto-generated and use the described structure, which never exceed the 80-character limit.
Verified on RHEL 5.4, i386/x86_64.
condor-ec2-enhanced-hooks-1.0-19

Changing the status to VERIFIED.

Comment 5 Lana Brindley 2009-11-11 21:21:10 UTC

Release note updated. If any revisions are required, please set the 
"requires_release_notes"  flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

Diffed Contents:
@@ -1 +1,9 @@
-please see bug summary.+Grid bug fix
+
+C: EC2E uses a number of elements to generate a queue name, one of which has an unlimited ID length. SQS queues have a limit of 80 characters. 
+C: It is possible that some ID numbers could use all of the allowed SQS name.
+F: Names of SQS queues are now auto-generated and use the described structure, which never exceed the 80-character limit.
+R: The limit can no longer be over-run
+
+
+EC2E uses a number of elements to generate a queue name, one of which has an unlimited ID length. SQS queues have a limit of 80 characters. It is possible that some ID numbers could use all of the allowed SQS name. Names of SQS queues are now auto-generated and use the described structure, which never exceed the 80-character limit.

Comment 7 errata-xmlrpc 2009-12-03 09:19:12 UTC

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/RHEA-2009-1633.html