| Summary: | Need updated qpid debug logging in foreman-debug | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Mike McCune <mmccune> | ||||
| Component: | Pulp | Assignee: | Mike McCune <mmccune> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Sachin Ghai <sghai> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1.6 | CC: | adahms, cwelton, sghai, xdmoon | ||||
| Target Milestone: | Unspecified | ||||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Additional logging information has been added to foreman-debug to improve response time for debugging Qpid errors.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-01-28 07:25:38 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Mike McCune
2016-01-21 16:57:36 UTC
This is an offshoot of this very high-priority bz: https://bugzilla.redhat.com/show_bug.cgi?id=1288223 Verified with 6.1.6 "Compose 7" I can see qpid-core-dump script and can see foreman-debug updated with additional qpid related information along with following: - pulp-running_tasks - mongo-reserved_resource - mongo-task_status - mongo-reserved_resources - qpid-rpm-qa - qpid-stat-c - qpid-stat-q - qpid-stat-resource_manager - qpid-stat-u [root@ibm-x3250m4-07 foreman-debug-QpXzE]# type qpid-core-dump qpid-core-dump is /usr/bin/qpid-core-dump Please see the attached screenshot for verification. Created attachment 1118700 [details]
foreman-debug containing qpid logs and location to new script "qpic-core-dump"
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-2016:0076 |