Bug 1298713
Summary: | Why does the documentation guide direct you to the output of logs? | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Eric Jones <erjones> |
Component: | Documentation | Assignee: | brice <bfallonf> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Vikram Goyal <vigoyal> |
Severity: | medium | Docs Contact: | Vikram Goyal <vigoyal> |
Priority: | high | ||
Version: | 3.1.0 | CC: | aos-bugs, jokerman, mmccomas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
OpenShift Enterprise 3.1
|
|
Last Closed: | 2016-04-19 01:55:42 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: | |
Embargoed: |
Description
Eric Jones
2016-01-14 19:13:29 UTC
Eric, I talked to the relevant people about this, and took a look myself, and it's a case of misleading words. Checking the output of the logs isn't entirely necessary, and really only contains the steps also found in the docs, but personalised for your cluster. The main reason for checking the logs is to ensure the pod was deployed correctly. This info has been submitted in this PR, which will hopefully merge soon: https://github.com/openshift/openshift-docs/pull/1641 Let me know if there's anything else for this BZ. Brice, I read the proposed changes and they make much more sense, I agree that it seems to have been an issue of misleading words. Thank you for that clarification! This BZ has been fixed in the following section of PR #1641: https://github.com/openshift/openshift-docs/pull/1641/files#diff-0bd2e2c1a5da6f157682d4e95ecea473R280 Moving this to complete. |