Red Hat Bugzilla – Bug 832425
SAM cli headpin Version command returns exitCode as 1 even after successful completion of command
Last modified: 2016-04-25 20:54:25 EDT
Description of problem: The newly added headpin -u admin -p admin version -v has exitCode as 1 Version-Release number of selected component (if applicable): [root@dell-pesc1425-01 ~]# rpm -qa | grep katello katello-cli-common-0.3.5-2.el6_2.noarch katello-selinux-0.2.4-1.el6_2.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-glue-candlepin-0.3.2-1.el6_2.noarch katello-certs-tools-1.1.5-1.el6_2.noarch katello-configure-0.3.7-1.el6_2.noarch katello-headpin-all-0.2.12-2.el6_2.noarch katello-cli-headpin-0.2.2-1.el6_2.noarch katello-common-0.3.2-1.el6_2.noarch katello-headpin-0.2.12-2.el6_2.noarch How reproducible: Automation JAVA_ClI code is executed on the SAM server Steps to Reproduce: The test report attached: http://pastebin.test.redhat.com/93090 Actual results: The return exit code for successful execution is 1. Expected results: The return exit code for successful execution should be 0 since all the other commmands return 1 after successful completion Additional info: cloning the bug for CFSE since the code is shared with katello
appears to have been fixed as of commit 9e0fe023bf11eb7c614f345becac960504476c57
VERIFIED with rpms: [root@nec-em16 ~]# rpm -qa | grep katello katello-cli-common-0.2.45-1.fc16.noarch katello-glue-foreman-0.2.50-1.fc16.noarch katello-glue-pulp-0.2.50-1.fc16.noarch katello-selinux-0.2.6-1.fc16.noarch katello-certs-tools-1.1.6-1.fc16.noarch katello-configure-0.2.32-1.fc16.noarch katello-glue-candlepin-0.2.50-1.fc16.noarch katello-all-0.2.53-1.fc16.noarch katello-common-0.2.50-1.fc16.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-cli-0.2.45-1.fc16.noarch katello-0.2.50-1.fc16.noarch katello-repos-0.2.7-1.fc16.noarch [root@nec-em16 ~]# katello -u admin -p admin version Headpin Unknown [root@nec-em16 ~]# echo $? 0 THe exitCode for successful execution of command is 0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0544.html