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.

Description of problem:
Enabling debug log level in candlepin via 

hammer admin logging --all --level-debug

(or via relevant component only) has no effect. The tool adds to /etc/candlepin/candlepin.conf:

log4j.logger.org.candlepin.servlet.filter=DEBUG

which has no effect (even after tomcat restart). The tool shall uncomment existing (or add a new one) line:

log4j.logger.org.candlepin=DEBUG


Version-Release number of selected component (if applicable):
Sat6.5
tfm-rubygem-hammer_cli_foreman_admin-0.0.8-3.el7sat.noarch
tfm-rubygem-hammer_cli-0.15.1.2-1.el7sat.noarch


How reproducible:
100%


Steps to Reproduce:
1.
hammer admin logging --all --level-debug
service tomcat restart

2. Trigger some subscription activity (attach a pool to a Content Host, register a C.H.,..)
3.
grep DEBUG /var/log/candlepin/candlepin.log


Actual results:
3. shows nothing


Expected results:
3. to show debug statements


Additional info:

Hi Lukáš,

could you please take a look at this bug since you're maintainer of hammer-cli-foreman-admin plugin which enables logging for candlepin.

Currently I see enabling here [1].

But I'm not sure if this is the correct way, since candlepin allows set it in different ways [2] [3].

[1] - https://github.com/theforeman/hammer-cli-foreman-admin/blob/6770df60a7dc9b8c65459dd76ea2dd813cf81a99/config/cli.modules.d/foreman_admin_logging_katello.yml#L33
[2] - https://www.candlepinproject.org/docs/candlepin/logging.html (Our Customization section)
[3] - https://www.candlepinproject.org/docs/candlepin/configuration.html (Logging section)

Hmmm, apologies for the late response but BZ hasn't been sending NEEDINFO emails for a while. Lemme see...

Oleh, what Pavel says it's correct this is a "tree" of nodes and we want to set it on the top level. Here is the fix:

https://github.com/theforeman/hammer-cli-foreman-admin/pull/9

ON_QA Verified

@Satellite 6.7.0 Snap 4.0

Steps/Observation:

 Able to enable/disable the debug level

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-2020:1455