Issue #1889
closed
Goferd stops logging after yum operation.
Added by jortel@redhat.com over 8 years ago. Updated over 5 years ago.
Description
The RHSM product-id (YUM) plugin completely re-configures the root logger. As a result, goferd stops logging to syslog after the pulp (gofer) plugin performs a yum operation. A bug has been filed against RHSM https://bugzilla.redhat.com/show_bug.cgi?id=1334916.
Updated by jortel@redhat.com over 8 years ago
May also fix: https://bugzilla.redhat.com/show_bug.cgi?id=1288462
Updated by jortel@redhat.com over 8 years ago
- Tracker changed from Task to Issue
- Subject changed from The RPM handler needs to use rpmtools in a child process to The RPM handler needs to mitigate the RHSM reconfiguring the root logger
- Priority changed from Normal to High
- Severity set to 2. Medium
- Triaged set to Yes
The RHSM YUM plugins reconfigure the root logger. As a result, goferd stops logging to syslog immediately after the RPM handler uses YUM. The workaround for this would be to have the Yum class in rpmtools capture the state of root logger configuration on construction and restore it in close(). Bugs have been filed against RHSM. If they are fixed, we can do nothing in Pulp.
Filed Upstream:
Updated by semyers over 8 years ago
- Platform Release changed from 2.8.4 to 2.8.5
Updated by semyers over 8 years ago
- Platform Release changed from 2.8.5 to 2.8.6
Updated by jortel@redhat.com over 8 years ago
- Subject changed from The RPM handler needs to mitigate the RHSM reconfiguring the root logger to Goferd stops logging after yum operation.
- Description updated (diff)
- Status changed from ASSIGNED to NEW
- Assignee deleted (
jortel@redhat.com)
Updated by mhrivnak about 8 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jortel@redhat.com
- Sprint/Milestone changed from 26 to 27
Updated by jortel@redhat.com about 8 years ago
EL7 bugzilla is at VERIFIED
EL6 bugzilla is at MODIFIED
Updated by jortel@redhat.com about 8 years ago
- Sprint/Milestone changed from 27 to 28
Updated by jortel@redhat.com about 8 years ago
RHEL 7 bugzilla is CLOSED-ERRATA but the RHEL 6 bugzilla is at MODIFIED.
Do we need to continue tracking this? I vote NO.
Updated by mhrivnak about 8 years ago
I agree that we can close this. There's not much value in us mirroring the el6 BZ's progress from modified through release. Perhaps closed-wontfix is appropriate for this redmine issue, since pulp is not taking any corrective action? We ensured that it's getting fixed elsewhere. What do you think?
Updated by jortel@redhat.com about 8 years ago
mhrivnak wrote:
I agree that we can close this. There's not much value in us mirroring the el6 BZ's progress from modified through release. Perhaps closed-wontfix is appropriate for this redmine issue, since pulp is not taking any corrective action? We ensured that it's getting fixed elsewhere. What do you think?
Agreed.
Updated by jortel@redhat.com about 8 years ago
- Status changed from ASSIGNED to CLOSED - WONTFIX
Fixed upstream in RHSM.
Updated by bmbouter about 8 years ago
- Status changed from CLOSED - WONTFIX to CLOSED - CURRENTRELEASE
Since this was fixed and that fix is available, I changed its closed state to CURRENTRELEASE
.