+++ This bug was initially created as a clone of Bug #227321 +++ Description of problem: Searching pages in the Guide searched the content in Yelp out rather than the content in the Guide. Version-Release number of selected component (if applicable): Deployment_Guide-en-US-5.0.0-19 RHEL5-Server-20070203.nightly How reproducible: Always Steps to Reproduce: 1.Log in system with any locale. 2.Load Red Hat Enterprise Linux Deployment Guide from system --> Documents. 3.Search pages with some keywords in the search bar. Actual results: You will find the content you searched out is from Yelp rather than from the Guide Expected results: The content you searched out is expected from the Guide. Additional info: -- Additional comment from mhideo on 2007-03-06 21:22 EST -- John, will the OMF files fix this? -- Additional comment from pm-rhel on 2007-03-21 18:15 EST -- This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. -- Additional comment from ddomingo on 2007-03-21 19:44 EST -- reassigning to mhideo for processing, jha for QA Michael, John, please let me know if there's anything needed from me for this. thanks! -- Additional comment from mhideo on 2007-08-17 10:58 EST -- Won't be able to address this until we have the package in Fedora. -------------- issue existing on following RPM: Global_File_System-en-US-5.1.0-4
Reassigning to mhideo. Problem appears to be production/RPM issue.
Removing automation notification
Moving Status to 'Assigned'
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. This request will be reviewed for a future Red Hat Enterprise Linux release.
i'm not sure why this bug is still open, seeing as BZ#227321 tracks this issue already. resolving bug as a duplicate of BZ#227321. *** This bug has been marked as a duplicate of 227321 ***