Bug 809010 - Link to documentation are not found
Summary: Link to documentation are not found
Keywords:
Status: CLOSED DUPLICATE of bug 790695
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Clayton Coleman
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-02 08:32 UTC by Ioan Albescu
Modified: 2015-05-15 01:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-04 04:46:48 UTC
Target Upstream Version:

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

Description Ioan Albescu 2012-04-02 08:32:22 UTC 
Description of problem:

Link to documentation are not found

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Loggin into account on https://openshift.redhat.com
2. Go to "My account" https://openshift.redhat.com/app/account
3. Try to view "See the User Guide for information about adding your own domain names to an application." which have following link: https://docs.redhat.com/docs/en-US/OpenShift_Express/2.0/html/User_Guide/sect-User_Guide-Working_With_Domains.html

  
Actual results:

link is not found

Expected results:

documentation page to be display
Additional info:
Comment 1 David O'Brien 2012-04-02 12:14:04 UTC 
Hi Ioan

This would be the result of looking at the "Preview" page of openshift.redhat.com, and a few of those links haven't been updated yet. The section you are referring to is located here:

http://docs.redhat.com/docs/en-US/OpenShift/2.0/html-single/User_Guide/index.html#sect-User_Guide-Working_With_Domains

I've reassigned this to the website team to update the links.

thanks
David
Comment 2 Xiaoli Tian 2012-04-04 04:46:48 UTC 
This is not an bug now since the production is updated.

*** This bug has been marked as a duplicate of bug 790695 ***
Note You need to log in before you can comment on or make changes to this bug.