Bug 1021046

Summary:	provided contextual feedback on successful addition/removal of environment from child node.
Product:	Red Hat Satellite	Reporter:	Corey Welton <cwelton>
Component:	Hammer	Assignee:	Petr Chalupa <pchalupa>
Status:	CLOSED UPSTREAM	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.2	CC:	bbuckingham, bkearney, omaciel, tsanders
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-25 20:37:23 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 Corey Welton 2013-10-18 20:59:13 UTC

Description of problem:
When user adds or removes an environment from a child node, no status is returned to the screen, other than a carriage return. If user does something triggering an error (i.e., trying to add an env that already exists), text is returned. 

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


How reproducible:


Steps to Reproduce:
1. [root@qe-blade-09 ~]# katello --user admin --password admin node remove_environment --environment Library --id 1 
2. [root@qe-blade-09 ~]# katello --user admin --password admin node add_environment --environment Library --id 3 

Actual results:
A carriage return, but no context

Expected results:
Some sort of valid result

Additional info:

Comment 1 RHEL Program Management 2013-10-18 21:05:02 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Mike McCune 2013-10-22 03:47:32 UTC

would like to punt this to mdp3 if we could

Comment 6 Brad Buckingham 2014-06-25 21:29:38 UTC

Moving this one to ON_QA for verification.

The CLI has since moved to hammer and the concept of a node has been renamed as 'capsule'.  With the new implementation, the results should now look similar to:

hammer> capsule content add-lifecycle-environment --id 2 --lifecycle-environment-id 6
Lifecycle environment successfully added to the capsule
hammer> capsule content remove-lifecycle-environment --id 2 --lifecycle-environment-id 6
Lifecycle environment successfully removed from the capsule
hammer>

Comment 7 Corey Welton 2014-07-25 20:37:23 UTC

Considering this closed since capsules have since been impl. and tested.