Bug 1008326

Summary:	Unclear error message when trying to rollback non-existent patch
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Jan Martiska <jmartisk>
Component:	Patching	Assignee:	Brian Stansberry <brian.stansberry>
Status:	CLOSED EOL	QA Contact:	Jan Martiska <jmartisk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	jason.greene, jawilson, jdoyle, kconner, olubyans, sappleto
Target Milestone:	---
Target Release:	EAP 6.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:49:31 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:

Description Jan Martiska 2013-09-16 07:24:30 UTC

[disconnected /] patch rollback --patch-id=asdfadsf --reset-configuration=false
JBAS016848: Cannot rollback patch (asdfadsf)

When the user tries to rollback an unknown patch ID, the message should be made clearer to say that the patch does not exist (is not installed).

Comment 1 Shaun Appleton 2013-09-25 09:26:13 UTC

To assist in patch identification it would be better if the description of the patch was included as well.

For example

[disconnected /] patch rollback --patch-id=asdfadsf --reset-configuration=false
JBAS016848: Cannot rollback patch (asdfadsf) EJB3 fix see JBPAPP-12345

is better than 

[disconnected /] patch rollback --patch-id=asdfadsf --reset-configuration=false
JBAS016848: Cannot rollback patch (asdfadsf)

Alternatively, 
Make available a list of codes (in the release notes?) so users can tell easily which patch failed.

ie.

 patch code   description
   asdfadsf   EJB3 fix see JBPAPP-12345
   bsdfadsg   HQ fix for durable topics see JBPAPP-98765
...

Comment 7 Dimitris Andreadis 2015-02-03 21:03:19 UTC

re-assign Emanuel's assigned bugs to Brian.