Bug 712263

Summary:	Topic export ignores failure to retrieve a topic.
Product:	[Other] Topic Tool	Reporter:	Stephen Gordon <sgordon>
Component:	cli-Topic_Tool	Assignee:	Stephen Gordon <sgordon>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.0.x	CC:	topic-tool-list
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	topic-tool-0.0.8-0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-29 04:26:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Stephen Gordon 2011-06-10 01:58:40 UTC

Description of problem:

Tool gracefully ignores the fact that a topic could not be read (sometimes due to a validity issue) and keeps on retrieving subsequent topics:

[Fatal Error] :234:6: The element type "step" must be terminated by the matching end-tag "</step>".
ERROR: Unable to load topic (http://topicrepo.englab.bne.redhat.com/TopicRepository/Tasks/IPA/Installing_the_IPA_Server.xml).
ERROR: Unable to parse 'Installation_Guide_Export/en-US/Infrastructure.xml'.

Ideally I think we want to allow this but keep track of which topics couldn't be read and display a list at the end of the run to highlight that it wasn't successful.

Comment 1 Stephen Gordon 2011-09-06 07:19:07 UTC

Committed revision 69970.

Comment 2 Stephen Gordon 2011-09-06 07:20:43 UTC

In the end went with the simpler mechanism of just reporting the first failure encountered and then ending the export as failed.