Bug 1306888 - Registering overcloud nodes with username and password is deprecated
Summary: Registering overcloud nodes with username and password is deprecated
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 10.0 (Newton)
Assignee: Angus Thomas
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-12 01:41 UTC by David Hill
Modified: 2016-10-14 19:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 19:57:09 UTC
Target Upstream Version:

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

Description David Hill 2016-02-12 01:41:39 UTC 
Description of problem:
Registering overcloud nodes with username and password is deprecated as per the error message I get when trying to register my replicator nodes with RHN.  This make most of the document here [1] confusing .  Reg-user and Reg-password isn't listed in the appendix [2].   Also, auto_attach cannot be used if pool_id is set and reg-org is mandatory... Perhaps more documentation could be generated in order to avoid confusing people.

[1] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/sect-Advanced-Scenario_3_Using_the_CLI_to_Create_an_Advanced_Overcloud_with_Ceph_Nodes.html
[2] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html/Director_Installation_and_Usage/appe-Deployment_Parameters.html

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


How reproducible:
Always

Steps to Reproduce:
1. Docs
2.
3.

Actual results:
Fails

Expected results:
Should be easy

Additional info:
Comment 2 Mike Burns 2016-04-07 21:11:06 UTC 
This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.
Note You need to log in before you can comment on or make changes to this bug.