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.
Description of problem:
The latest version of pulp has switched to using syslog, but it is not including an rsyslog configuration file to redirect info to /var/log/pulp/ -- all logs are written to /var/log/messages which is different than any of the other services.
Further, the pulp-server package still owns various logfiles in the /var/log/pulp folder, but none of them are written to, since everything is going through syslog to /var/log/messages
Version-Release number of selected component (if applicable):
[root@satellite ~]# rpm -qa | grep pulp | sort
createrepo-0.9.9-21.2.pulp.el6sat.noarch
m2crypto-0.21.1.pulp-8.el6sat.x86_64
mod_wsgi-3.4-1.pulp.el6sat.x86_64
pulp-katello-plugins-0.3-1.el6sat.noarch
pulp-nodes-common-2.4.0-0.16.beta.el6sat.noarch
pulp-nodes-parent-2.4.0-0.16.beta.el6sat.noarch
pulp-puppet-plugins-2.4.0-0.16.beta.el6sat.noarch
pulp-puppet-tools-2.4.0-0.16.beta.el6sat.noarch
pulp-rpm-plugins-2.4.0-0.16.beta.el6sat.noarch
pulp-selinux-2.3.1-1.el6.noarch
pulp-server-2.4.0-0.16.beta.el6sat.noarch
python-isodate-0.5.0-1.pulp.el6sat.noarch
python-kombu-3.0.15-5.pulp.el6sat.noarch
python-pulp-bindings-2.4.0-0.16.beta.el6sat.noarch
python-pulp-common-2.4.0-0.16.beta.el6sat.noarch
python-pulp-puppet-common-2.4.0-0.16.beta.el6sat.noarch
python-pulp-rpm-common-2.4.0-0.16.beta.el6sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Run pulp
Actual results:
Logs go to /var/log/messages
/var/log/pulp/*.log are empty
Expected results:
/var/log/pulp/ should have files written to it
Additional info:
Here is a sample /etc/rsyslog.d/pulp.conf that could be used to redirect things:
:syslogtag, startswith, "pulp" /var/log/pulp/pulp.log
& ~
It could possibly be improved with additional filters and redirects to mimic the previous behavior of the existing logfiles:
celerybeat.log
reserved_resource_worker-0.log
reserved_resource_worker-1.log
reserved_resource_worker-2.log
reserved_resource_worker-3.log
resource_manager.log
Comment 1RHEL Program Management
2014-05-20 21:05:15 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Adding this functionality would allow for the pulp specific logging to be provided in its own logfile, whilst being minimally disruptive to an existing rsyslog configuration.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.