Bug 1288522 - [Docs] oadm new-project does not switch to the newly created project
[Docs] oadm new-project does not switch to the newly created project
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2015-12-04 08:44 EST by Jean-Francois Saucier
Modified: 2015-12-04 08:44 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jean-Francois Saucier 2015-12-04 08:44:57 EST
Document URL: 

Section Number and Name: 

Describe the issue: 
At the beginning of this section, we create a project with the "oadm new-project" command. But this command, unlike "oc new-project", do not switch to the newly created project. So if someone don't notice that, they do the following steps in the wrong project.

Suggestions for improvement: 
The upstream documentation (https://github.com/openshift/origin-aggregated-logging/tree/master/deployment) seems to use "oc new-project". I understand the goal using "oadm new-project" was to show that you can specify a node-selector.

So maybe we can just state that we must to an "oc project logging" command after that.

Additional information:

Note You need to log in before you can comment on or make changes to this bug.