Another +1 for the secret key problem. I also work around it with install automation.
-Chris
> On Apr 3, 2017, at 5:52 PM, Brian Moss <email address hidden> wrote:
>
> Hi Thiago, good idea. I think it is useful to have the user run the
> command manually the first time so they understand the process. No
> reason they can't have it running automatically after that though. I'll
> add a note to that section.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1663485
>
> Title:
> Document Nova v2 Cells and Placement API
>
> Status in openstack-manuals:
> Fix Released
>
> Bug description:
> During an Installation Guide CentOS install, attempting to launch an
> instance hits this issue:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1405098
>
> It appears that we need to document how to add a cell manually in the
> Install Guide.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-manuals/+bug/1663485/+subscriptions
Another +1 for the secret key problem. I also work around it with install automation.
-Chris
> On Apr 3, 2017, at 5:52 PM, Brian Moss <email address hidden> wrote: /bugs.launchpad .net/bugs/ 1663485 /bugzilla. redhat. com/show_ bug.cgi? id=1405098 /bugs.launchpad .net/openstack- manuals/ +bug/1663485/ +subscriptions
>
> Hi Thiago, good idea. I think it is useful to have the user run the
> command manually the first time so they understand the process. No
> reason they can't have it running automatically after that though. I'll
> add a note to that section.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Document Nova v2 Cells and Placement API
>
> Status in openstack-manuals:
> Fix Released
>
> Bug description:
> During an Installation Guide CentOS install, attempting to launch an
> instance hits this issue:
>
> https:/
>
> It appears that we need to document how to add a cell manually in the
> Install Guide.
>
> To manage notifications about this bug go to:
> https:/