Bug 1540493
| Summary: | [RFE] include passenger-memory-stats & passenger-status in foreman-debug | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Evgeni Golov <egolov> | |
| Component: | Foreman Debug | Assignee: | Lukas Zapletal <lzap> | |
| Status: | CLOSED ERRATA | QA Contact: | Ranjan Kumar <rankumar> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.2.0 | CC: | bkearney, mmccune, pcreech, rankumar | |
| Target Milestone: | Unspecified | Keywords: | FutureFeature | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | foreman-1.15.6.41-1 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1572290 (view as bug list) | Environment: | ||
| Last Closed: | 2018-06-19 20:17:00 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
|
Description
Evgeni Golov
2018-01-31 08:43:30 UTC
Created from redmine issue http://projects.theforeman.org/issues/19497 Upstream bug assigned to None Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19497 has been resolved. Verified! on Satellite 6.3.2 1.0 @satellite 6.3 snap 2.0 Steps: 1. Built 6.3 2. Generate foreman-debug 3. Extract the same 4. #cd <foreman-debug>; ls -lrt passenger* -rw-r--r--. 1 root root 123 May 29 14:11 passenger_status_requests -rw-r--r--. 1 root root 719 May 29 14:11 passenger_status_pool -rw-r--r--. 1 root root 2927 May 29 14:11 passenger_status_backtraces -rw-r--r--. 1 root root 2244 May 29 14:11 passenger_memory Behavior: The file passenger_memory & passenger_status* is present in foreman-debug. 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-2018:1950 |