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.

Bug 1542407

Summary: [RFE] Update foreman-debug to collect logs in 6.2.z
Product: Red Hat Satellite Reporter: Nikhil Kathole <nkathole>
Component: Satellite MaintainAssignee: Anurag Patel <apatel>
Status: CLOSED ERRATA QA Contact: Nikhil Kathole <nkathole>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2.13CC: apatel, bbuckingham, bkearney, bmidwood, inecas, kgaikwad, mmccune, rochacbruno, sghai, zhunting
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-1.11.0.89-1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1538640 Environment:
Last Closed: 2018-05-21 20:16:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1538640    
Bug Blocks:    

Comment 1 Nikhil Kathole 2018-02-06 10:14:56 UTC
Foreman-debug does not collect /var/log/foreman-maintain/foreman-maintain.log in satellite 6.2.

# rpm -q satellite
satellite-6.2.14-4.0.el7sat.noarch

When customer will perform upgrade from 6.2.z to satellite 6.3 using foreman-maintain and if faced some issue, foreman-debug should collect foreman-maintain logs.

Comment 3 Satellite Program 2018-02-06 11:17:46 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21743 has been resolved.

Comment 5 Nikhil Kathole 2018-04-20 09:35:22 UTC
VERIFIED

# rpm -q satellite
satellite-6.2.15-1.0.el7sat.noarch

# rpm -qa | grep foreman-debug
foreman-debug-1.11.0.89-1.el7sat.noarch

# foreman-debug
Processing... (takes a while)Exporting tasks, this may take a few minutes.
Copying entire file: /tmp/task-export-1524211142.tar.gz


 HOSTNAME: dell-per630-fc-03.rhts.eng.bos.redhat.com
       OS: redhat
  RELEASE: Red Hat Enterprise Linux Server release 7.5 (Maipo)
  FOREMAN: 1.11.0.89
     RUBY: ruby 2.0.0p648 (2015-12-16) [x86_64-linux]
   PUPPET: 3.8.6
  DENIALS: 0


A debug file has been created: /tmp/foreman-debug-FOxwQ.tar.xz (1149060 bytes)

To upload a tarball to our secure site, please use the -u option.

# tar -tvf /tmp/foreman-debug-FOxwQ.tar.xz | grep foreman-maintain
drwxr-xr-x root/root         0 2018-04-20 03:56 foreman-debug-FOxwQ/var/log/foreman-maintain/
-rw-r--r-- root/root      2766 2018-04-20 03:56 foreman-debug-FOxwQ/var/log/foreman-maintain/foreman-maintain.log

Comment 9 errata-xmlrpc 2018-05-21 20:16:43 UTC
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-2018:1672