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.

This was discussed thoroughly during the beta process. It was agreed that the best solution is for satellite as a downstream product to have the rsyslog rule. The rhel maintainer of rsyslog advised us very strongly against having the upstream pulp project add an rsyslog rule by default.

The log files we do ship with would contain data if pulp worker processes fail during startup. We are also limited by a quirk in the celery library that it requires us to provide it with a log file on startup, even if we don't want to use it.

Are you ok with closing this, or would you like to re-open that discussion?

I will close this and add the comment to the sat6 bug. Thanks.