RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1032564 - Technical notes link is broken https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.5_Technical_Notes/index.html
Summary: Technical notes link is broken https://access.redhat.com/site/documentation/e...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: Documentation
Version: 6.5
Hardware: s390x
OS: All
unspecified
high
Target Milestone: rc
: ---
Assignee: Eliska Slobodova
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1004793
TreeView+ depends on / blocked
 
Reported: 2013-11-20 12:00 UTC by IBM Bug Proxy
Modified: 2014-10-04 16:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-22 11:26:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
redhat release notes (127.97 KB, application/zip)
2013-11-20 12:15 UTC, IBM Bug Proxy
no flags Details


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 100164 0 None None None Never

Description IBM Bug Proxy 2013-11-20 12:00:54 UTC

Comment 1 IBM Bug Proxy 2013-11-20 12:00:59 UTC
Problem Description
------------------------------
The issue is observed in  RHEL6.5 on cd release notes 

Technical link  https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.5_Technical_Notes/index.html  mentioned in the release notes is broken  

[root@r3530053 Red_Hat_Enterprise_Linux-Release_Notes-6-en-US-5]# cd
[root@r3530053 ~]# cat /etc/issue
Red Hat Enterprise Linux Server release 6.5 (Santiago)
Kernel \r on an \m

[root@r3530053 ~]# uname -a
Linux r3530053.boeblingen.de.ibm.com 2.6.32-431.el6.s390x #1 SMP Sun Nov 10 22:21:52 EST 2013 s390x s390x s390x GNU/Linux
[root@r3530053 ~]# rpm -qa | grep -i release
Red_Hat_Enterprise_Linux-Release_Notes-6-en-US-5-2.el6.noarch
redhat-release-server-6Server-6.5.0.1.el6.s390x
[root@r3530053 ~]#

Please find the attached on CD release notes directory

Comment 2 IBM Bug Proxy 2013-11-20 12:15:22 UTC
Created attachment 826595 [details]
redhat release notes

Comment 4 Eliska Slobodova 2013-11-20 14:13:00 UTC
Hello,

Please note that the Technical Notes are not yet available. The book will appear online upon GA.

Comment 5 Eliska Slobodova 2013-11-22 11:26:07 UTC
Closing as the problem should no longer occur. Please re-open if you still encounter it.

Comment 6 IBM Bug Proxy 2013-12-03 09:20:30 UTC
------- Comment From igangadh.com 2013-12-03 09:13 EDT-------
Able to view technical notes hence closing this bugzilla


Note You need to log in before you can comment on or make changes to this bug.