Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 1RHEL 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.
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>