Bug 1045531 - erratum link in rhos 4.0 Tech Notes is broken
Summary: erratum link in rhos 4.0 Tech Notes is broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Technical_Notes
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z1
: 4.0
Assignee: Bruce Reeler
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 1049118
TreeView+ depends on / blocked
 
Reported: 2013-12-20 16:37 UTC by Scott Lewis
Modified: 2014-10-30 22:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-09 23:32:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Scott Lewis 2013-12-20 16:37:20 UTC 
Technical notes link to erratum is broken:

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/4/html/Technical_Notes/chap-RHEA-2013-15776-02.html#sect-RHEA-2013-15776-02-General

just before Section 1.1. shows: The bugs contained in this chapter are addressed by advisory RHEA-2013:15776-02. Further information about this advisory is available at https://rhn.redhat.com/errata/RHEA-2013-15776-02.html. 

should be: ...   http://rhn.redhat.com/errata/RHEA-2013-1859.html
Comment 1 Summer Long 2014-01-20 00:38:06 UTC 
Assigning to Bruce Reeler as 'finalizing' author for Technical Notes.
Comment 2 Bruce Reeler 2014-01-21 00:02:31 UTC 
At release time, the numbers for the errata advisories all change when they go public. In this case, the advisory number changed from RHEA-2013:15776 to RHEA-2013:1859. 
NOTE: The version numbers (such as the 02 at the end of RHEA-2013:15776-02) must also be dropped.

When building the Tech Notes, this change has to be reflected throughout, i.e. in the XML file names, <xi:includes, headings etc. 

Changed the file names to 2013:1859 and the link in comment 0 to point to the correct URL.

Set mlopes as gerrit reviewer.
Note You need to log in before you can comment on or make changes to this bug.