Bug 608693

Summary:	RHTSupport plugin outputs wrong URI to case
Product:	Red Hat Enterprise Linux 6	Reporter:	Michal Nowak <mnowak>
Component:	abrt	Assignee:	Denys Vlasenko <dvlasenk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michal Nowak <mnowak>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.0	CC:	ahecox, dvlasenk, gavin, jmoskovc, kklic, npajkovs, ohudlick, rvokal
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	abrt-1.1.8-2.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-10 19:33:20 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 Michal Nowak 2010-06-28 13:43:32 UTC

Description of problem:

abrt-1.1.7-2.el6.x86_64

When I reported a case. abrt said:

"""
Case created: http://support-services-devel.gss.redhat.com:8080/Strata/cases/00014501, but report attachment failed:...
"""

Link named "http://support-services-devel.gss.redhat.com:8080/Strata/cases/00014501," points to "http://support-services-devel.gss.redhat.com:8080/Strata/cases/00014501," but it should to "http://support-services-devel.gss.redhat.com:8080/Strata/cases/00014501" (w/o the ',').

Comment 1 RHEL Program Management 2010-06-28 14:03:01 UTC

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 2 Jiri Moskovcak 2010-06-28 19:11:31 UTC

Probably the GUI problem, the ',' should be stripped when looking for a url in the text.

Comment 3 Denys Vlasenko 2010-06-29 14:00:28 UTC

Fixed in git, will be in abrt-1.1.8

Comment 7 releng-rhel@redhat.com 2010-11-10 19:33:20 UTC

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.