Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 726322 (rhel58rtt)

Summary: [TRACKER] RHEL 5.8 RTT tracker
Product: Red Hat Enterprise Linux 5 Reporter: Alexander Todorov <atodorov>
Component: distributionAssignee: RHEL Program Management <pm-rhel>
Status: CLOSED WONTFIX QA Contact: Ondrej Hudlicky <ohudlick>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.8CC: jstodola, mbanas, mganisin, pholica
Target Milestone: rcKeywords: Tracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-27 07:29:16 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:
Bug Depends On: 218666, 248125, 550844, 634923, 746673, 748733, 750230, 750249, 750251, 750283, 750456, 752493, 752507, 754119, 754962, 755031, 755959, 756304, 756330, 756707, 758106, 759155, 759162, 759384, 761359, 761391, 761522, 765818, 765887, 767612, 768003, 768134, 768140, 768308, 768904, 769287, 769294, 771901, 771903, 772182, 772613, 772921, 781313, 782148, 782767, 784202, 785078, 843305, 848617    
Bug Blocks:    

Description Alexander Todorov 2011-07-28 08:40:45 UTC 
This is a tracker bug. Nothing to fix here.
Comment 1 Alexander Todorov 2011-10-25 08:20:56 UTC 
*** Bug 748734 has been marked as a duplicate of this bug. ***
Comment 4 RHEL Program Management 2022-04-27 07:29:16 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.