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.

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21743 has been resolved.

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

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