Bug 1320227 - [DOCS] link to 'kube-files.tar' is dead in the "Atomic Host 7 Getting Started with Containers Guide"
Summary: [DOCS] link to 'kube-files.tar' is dead in the "Atomic Host 7 Getting Started...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-RHEL-Atomic
Version: 7.2
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Chris Negus
QA Contact: Vikram Goyal
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 15:26 UTC by Micah Abbott
Modified: 2019-03-06 01:32 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-24 05:59:36 UTC
Target Upstream Version:

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

Description Micah Abbott 2016-03-22 15:26:54 UTC 
The link to 'kube-files.tar
Comment 1 Micah Abbott 2016-03-22 15:29:06 UTC 
(In reply to Micah Abbott from comment #0)
> The link to 'kube-files.tar

https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#launching_services_replication_controllers_and_container_pods_with_kubernetes

The link to 'kube-files.tar' at the end of section 3.7 does not work.  When I follow the link, I get an error:

File not found."


This is a problem if a customer is trying to follow the guide and expecting to be able to download the files related to the guide.
Comment 3 Vikram Goyal 2016-03-23 23:50:47 UTC 
Thanks for filing this Micah!

I am looking into it.
Comment 4 Vikram Goyal 2016-03-24 05:59:36 UTC 
Chris has made the fix for these files by putting the right links for the kube_files

This can be verified here [1].

Moving this to CLOSED-->CURRENTRELEASE.

[1] https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#creating_a_kubernetes_cluster_to_run_docker_formatted_container_images
Note You need to log in before you can comment on or make changes to this bug.