Bug 1322123

Summary: [DOCS] content missing on Getting Started With Containers
Product: Red Hat Enterprise Linux 7 Reporter: David Darrah/Red Hat QE <ddarrah>
Component: doc-RHEL-AtomicAssignee: Chris Negus <cnegus>
Status: CLOSED CURRENTRELEASE QA Contact: Vikram Goyal <vigoyal>
Severity: high Docs Contact: Vikram Goyal <vigoyal>
Priority: high    
Version: 7.2CC: cnegus, ddarrah, miabbott, vigoyal, yruseva, zdover
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1320339 Environment:
Last Closed: 2016-06-10 01:23:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Darrah/Red Hat QE 2016-03-29 20:51:05 UTC 
In Section "2.4 EXPLORING KUBERNETES PODS" of "Getting started with Containers", the first paragraph seems to reference a following command and then not provide it:

If something goes wrong along the way, there are several ways to determine what happened. One thing you can do is to examine services inside of the containers. To do that, you can look at the logs inside the container to see what happened. Run the following command (replacing the last argument with the pod name you want to examine).

<seems like there should be a command here>

Another problem that people have had comes from forgetting to disable firewalld. If firewalld is active, it could block access to ports when a service tries to access them between your containers. Make sure you have run systemctl stop firewalld ; systemctl disable firewalld on your host. 
....

In case it is a rendering issue, I am using firefox 45.0.1 on fedora.
Comment 2 Chris Negus 2016-06-02 20:33:27 UTC 
I added an example of the "kubectl logs" command. I'll add a comment here when the document is published on the portal.
Comment 3 Chris Negus 2016-06-09 03:51:05 UTC 
I've pushed the fix. It is now ready for publishing. Once it is published, it will appear here: https://access.redhat.com/documentation/en/red-hat-enterprise-linux-atomic-host/version-7/getting-started-with-containers/#get_started_orchestrating_containers_with_kubernetes
Comment 4 Vikram Goyal 2016-06-10 01:23:51 UTC 
Thanks Chris.

This is now pushed live and can be verified here [1].

Moving this bug to CLOSED-->CURRENTRELEASE.

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