Description of problem: We're telling users a sync was successful even if there's no way it could be. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a child node from parent but don't actually complete process on child side (i.e., run node-install) -- or assure there's something that causes the install to fail on child. 2. katello --user admin --password admin node sync --id 1 3. View results. Actual results: [root@ibm-x3500m4-01 ~]# katello --user admin --password admin node --help Usage: katello options node command Supported Commands: add_environment add an environment list list all known nodes remove_environment remove an environment sync Sync a node Options: -h, --help show this help message and exit [root@ibm-x3500m4-01 ~]# katello --user admin --password admin node sync --id 1 Sync Complete Expected results: The text implies that we're performing some sort of sync against child node - but if nothing is taking place and/or if it failed, we shouldn't just say "sync complete". Additional info:
I don't think this is really a 'high' priority, but will take a look.
*** Bug 1017921 has been marked as a duplicate of this bug. ***
katello-cli pull request: https://github.com/Katello/katello-cli/pull/109 The the output should now be similar to the following: katello> node sync --org ACME_Corporation --environment dev --id 1 Sync of environment [ dev ] completed successfully. # if the child node was down (e.g. httpd not running on node) katello> node sync --org ACME_Corporation --environment dev --id 1 Sync of environment [ dev ] failed:[Errno 111] Connection refused
QA Verified in Satellite-6.0.2-RHEL-6-20131021.0
This was verified and delivered with MDP2. Closing it out.