Bug 1576740

Thanks Pavel, easy fix and backport as well.

http://projects.theforeman.org/issues/23556

The configuration with syslog is worth creating an upstream ticket, no BZ needed tho.

http://projects.theforeman.org/issues/23557

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

In Satellite 6.4, I'm not able to find the qdrouterd.log file

# cat /etc/qpid-dispatch/qdrouterd.conf
...
log {
    module: DEFAULT
    enable: info+
    timestamp: true
    output: /var/log/qdrouterd/qdrouterd.log
}
...
# foreman-debug
# tar -xf /var/tmp/foreman-debug-ykEFS.tar.xz
# find foreman-debug-ykEFS/ -name qdrouterd.log
<No result>
# find /var -name qdrouterd.log
<No result>

I just shutdown my Sat, can you verify this:

grep qrouterd.log /usr/share/foreman/script/foreman-debug.d/*

There was a change apparently which is adding:

/var/log/qdrouterd/qdrouterd.log

It was merged here:

https://github.com/theforeman/foreman-packaging/pull/2468/files

Maybe we missed cherry-pick?

Hi Lukas, there are still no results showing after running the command.

# grep qrouterd.log /usr/share/foreman/script/foreman-debug.d/*

Ok thanks, looks like it's katello version is 3.6.0

I am closing the bug unless there was some issue on the rel-eng side. Chris, can you confirm the bit landed in the snap correctly? I am currently unable to upgrade my snap due to other issue.

Sorry for the confusion, ignore comment 9.

Chris, I please retest with next snap.

I can confirm the logfile is not collected by Sat 6.3.2:

[root@pmoravec-sat63 ~]# rpm -q satellite katello
satellite-6.3.2-1.el7sat.noarch
katello-3.4.5-18.el7sat.noarch
[root@pmoravec-sat63 ~]# grep -r qdrouterd $(rpm -ql katello-debug foreman-debug) | sort -u
/usr/share/foreman/script/foreman-debug.d/katello-debug.sh:  add_files /etc/qpid-dispatch/qdrouterd.conf
[root@pmoravec-sat63 ~]# 

and generated foreman-debug does contain only the config file.

So if the fix was added to RC1, then we / engineering should file BZ against RCM. Until that, the bug is still valid - foreman-debug shipped to customers still do not collect the logfile (and that is what matters to CEE).

Pavel, this is ON_QA for Satellite 6.4. I am not sure how rel-engs want to handle 6.3, it was not yet assigned into any errata. This is 6.4+6.3 BZ.

(In reply to Lukas Zapletal from comment #10)
> Sorry for the confusion, ignore comment 9.
> 
> Chris, I please retest with next snap.

Hey Lukas, I'm still getting the same results using Satellite 6.4.0 snap 9.0

Chris,

the file requested in BZ *is* being collected:

[root@next ~]# grep -n qdrouterd.log /usr/share/foreman/script/foreman-debug.d/katello-debug.sh 
79:  add_files /var/log/qdrouterd/qdrouterd.log

But it does not exist:

[root@next ~]# ls /var/log/qdrouterd/qdrouterd.log
ls: cannot access /var/log/qdrouterd/qdrouterd.log: No such file or directory

If you create a dummy contents debug/sosreport *will* collect it. Therefore IMHO this BZ is VERIFIED.

Why qrouterd is not configured for this file is another story, but this BZ is IMHO solved and closed.

[root@next ~]# grep output /etc/qpid-dispatch/qdrouterd.conf 
    output: syslog

Maybe pmoravec knows.

For the record, I was testing this with Satellite 6.4 and this seems to be correct - long term we want EVERYTHING to be in syslog. That is collected by debug script. For 6.4 this is IMHO VERIFIED.

I guess this needs to by cherrypicked into 6.3 and QAacked there tho.

On ony Sat or Caps 6.3 I tried, I see:

$ grep output /etc/qpid-dispatch/qdrouterd.conf
    output: /var/log/qdrouterd/qdrouterd.log
$

So the BZ is 6.3 related _only_, if 6.4 and onwards will log to syslog only.

(lzap, does it make sense to remove collecting the file from upstream foreman/katello-debug? as it seems to be ridiculous? I didnt know the recent change is about to be changed back :-S)

OK Thanks! I am not against but I won't do this :-)

We can move to VERIFIED and wait for 6.3 errata then.

(In reply to Lukas Zapletal from comment #15)
> Chris,
> 
> the file requested in BZ *is* being collected:
> 
> [root@next ~]# grep -n qdrouterd.log
> /usr/share/foreman/script/foreman-debug.d/katello-debug.sh 
> 79:  add_files /var/log/qdrouterd/qdrouterd.log
> 
> But it does not exist:
> 
> [root@next ~]# ls /var/log/qdrouterd/qdrouterd.log
> ls: cannot access /var/log/qdrouterd/qdrouterd.log: No such file or directory
> 
> If you create a dummy contents debug/sosreport *will* collect it. Therefore
> IMHO this BZ is VERIFIED.
> 
> Why qrouterd is not configured for this file is another story, but this BZ
> is IMHO solved and closed.
> 
> [root@next ~]# grep output /etc/qpid-dispatch/qdrouterd.conf 
>     output: syslog
> 
> Maybe pmoravec knows.

Oh ok, thanks for the clarification.

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/RHSA-2018:2927