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.
DescriptionReartes Guillermo
2016-03-06 17:25:53 UTC
Description of problem:
i am executing foreman-debug from a ruby program and i noticed that formeman-debug is givin an exit code of 1, but there was no (known to me) error.
i executed formeman-debug directly from the shell and it also gives an exit code of 1 instead of 0.
Version-Release number of selected component (if applicable):
Satellite 6.1.7
How reproducible:
always
Steps to Reproduce:
1. execute 'foreman-debug'
2. check exit code (echo $?)
Actual results:
# foreman-debug
Exporting tasks, this may take a few minutes.
Copying entire file: /tmp/task-export-1457284097.tar.gz
HOSTNAME: testsat7.example.com
OS: redhat
RELEASE: Red Hat Enterprise Linux Server release 7.2 (Maipo)
FOREMAN: 1.7.2
SATELLITE: 6.1.7
RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
PUPPET: 3.6.2
DENIALS: 25
A debug file has been created: /tmp/foreman-debug-bNhs9.tar.xz (1148640 bytes)
[root@testsat7 ~]# echo $?
1
Expected results:
# echo $?
0
Additional info:
http://projects.theforeman.org/issues/13442
foreman-debug script should return a meaningful exit code
[foreman-installer]# foreman-debug
Processing... (takes a while)Exporting tasks, this may take a few minutes.
HOSTNAME: abc.redhat.com
OS: redhat
RELEASE: Red Hat Enterprise Linux Server release 7.2 (Maipo)
FOREMAN: 1.11.0.9
RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
PUPPET: 3.6.2
DENIALS: 21
A debug file has been created: /tmp/foreman-debug-Qf6yT.tar.xz (955348 bytes)
To upload a tarball to our secure site, please use the -u option.
[root@katello1 foreman-installer]# echo $?
0
VERIFIED with sat62-snap6
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.
https://access.redhat.com/errata/RHBA-2016:1500
Description of problem: i am executing foreman-debug from a ruby program and i noticed that formeman-debug is givin an exit code of 1, but there was no (known to me) error. i executed formeman-debug directly from the shell and it also gives an exit code of 1 instead of 0. Version-Release number of selected component (if applicable): Satellite 6.1.7 How reproducible: always Steps to Reproduce: 1. execute 'foreman-debug' 2. check exit code (echo $?) Actual results: # foreman-debug Exporting tasks, this may take a few minutes. Copying entire file: /tmp/task-export-1457284097.tar.gz HOSTNAME: testsat7.example.com OS: redhat RELEASE: Red Hat Enterprise Linux Server release 7.2 (Maipo) FOREMAN: 1.7.2 SATELLITE: 6.1.7 RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux] PUPPET: 3.6.2 DENIALS: 25 A debug file has been created: /tmp/foreman-debug-bNhs9.tar.xz (1148640 bytes) [root@testsat7 ~]# echo $? 1 Expected results: # echo $? 0 Additional info: http://projects.theforeman.org/issues/13442 foreman-debug script should return a meaningful exit code