Hide Forgot
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:
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.
would like to punt this to mdp3 if we could
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>
Considering this closed since capsules have since been impl. and tested.