[rdo-list] mitaka installation

Mon Jun 20 20:48:51 UTC 2016

Option 1

File bug against packstack , stable release mitaka to https://bugzilla.redhat.com

and wait for better times to come

Option 2

1. packstack --gen-answer-file  answer1.txt

2. Edit answer1.txt

  CONFIG_KEYSTONE_API_VERSION=v3

3.packstack --answer-file=./answer1.txt

It will crash running cinder's puppet , however

# systemctll | grep cinder

will look just fine right after crash

4. Update answer1.txt and set

  CONFIG_CINDER_INSTALL=n

5. packstack --answer-file=./answer1.txt

Up on completion CINDER would work as far as I remember.

This is a hack

Option 3. Read and follow

https://www.linux.com/blog/backport-upstream-commits-stable-rdo-mitaka-release-deployments-keystone-api-v3

This is right way to go which demonstrates  that you are understanding what you are doing.

Regards.

Boris.

-------------------------------------------------------------------------------------------------------------------------------------------------
From: Andrey Shevel <shevel.andrey at gmail.com>
Sent: Monday, June 20, 2016 1:44 PM
To: Boris Derzhavets
Subject: Re: [rdo-list] mitaka installation

Hello colleagues,

I repeated packstack --allinone (mitaka) exactly like described on
https://www.rdoproject.org/install/quickstart/
Packstack quickstart — RDO<https://www.rdoproject.org/install/quickstart/>
www.rdoproject.org
Packstack quickstart: Proof of concept for single node. Packstack is an installation utility that lets you spin up a proof of concept cloud on one node.

on newly created VM and newly installed from scratch (as virtual server) with OS

[root at openstack-test ~]# cat /etc/os-release*
NAME="Scientific Linux"
VERSION="7.2 (Nitrogen)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.2"
PRETTY_NAME="Scientific Linux 7.2 (Nitrogen)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:scientificlinux:scientificlinux:7.2:GA"
HOME_URL="http://www.scientificlinux.org//"
BUG_REPORT_URL="mailto:scientific-linux-devel at listserv.fnal.gov"

I got exactly same errors as before

===================================
Applying 192.168.122.47_amqp.pp
Applying 192.168.122.47_mariadb.pp
192.168.122.47_amqp.pp:                              [ DONE ]
192.168.122.47_mariadb.pp:                           [ DONE ]
Applying 192.168.122.47_apache.pp
192.168.122.47_apache.pp:                            [ DONE ]
Applying 192.168.122.47_keystone.pp
Applying 192.168.122.47_glance.pp
Applying 192.168.122.47_cinder.pp
192.168.122.47_keystone.pp:                       [ ERROR ]
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.122.47_keystone.pp
Error: Could not prefetch keystone_role provider 'openstack': Could
not authenticate
You will find full trace in log
/var/tmp/packstack/20160620-191746-ud6qNn/manifests/192.168.122.47_keystone.pp.log
Please check log file
/var/tmp/packstack/20160620-191746-ud6qNn/openstack-setup.log for more
information
Additional information:
 * A new answerfile was created in: /root/packstack-answers-20160620-191747.txt
 * Time synchronization installation was skipped. Please note that
unsynchronized time on server instances might be problem for some
OpenStack components.
 * File /root/keystonerc_admin has been created on OpenStack client
host 192.168.122.47. To use the command line tools you need to source
the file.
 * To access the OpenStack Dashboard browse to http://192.168.122.47/dashboard .
Please, find your login credentials stored in the keystonerc_admin in
your home directory.
 * To use Nagios, browse to http://192.168.122.47/nagios username:
nagiosadmin, password: 6099599f76754f92

Stop Date & Time =  Mon Jun 20 19:26:39 MSK 2016
==================================

It seems some openstack installation drawback takes place.
Automatically generated packstack-answers file is in the attachment

I did pay also  attention that on the http://trystack.org/ we see
version 'liberty' but not 'mitaka'.

Any comments ?

On Fri, Jun 17, 2016 at 1:35 PM, Boris Derzhavets
<bderzhavets at hotmail.com> wrote:
> I have well tested workaround for CONFIG_KEYSTONE_API_VERSION=v3 based on
>
> back porting 2 recent upstream commits to stable RDO Mitaka.
>
> When you run `packstack --alinone`   Keystone API is v2.0 by default not
> v3.
>
> So you might be focused on v2.0, otherwise let me know.   I have detailed
> notes
>
> been done for back port ( one more time thanks to Javier Pena for upstream
> work )
>
>
> Boris.
> ________________________________
> From: rdo-list-bounces at redhat.com <rdo-list-bounces at redhat.com> on behalf of
> Andrey Shevel <shevel.andrey at gmail.com>
> Sent: Friday, June 17, 2016 4:08 AM
> To: alan.pevec at redhat.com
> Cc: rdo-list
> Subject: Re: [rdo-list] mitaka installation
>
> The file REINSTALL.... is script to reinstall Openstack-mitaka
>
> On Thu, Jun 16, 2016 at 9:39 PM, Alan Pevec <apevec at redhat.com> wrote:
>>> ERROR : Error appeared during Puppet run: 193.124.84.22_keystone.pp
>>> Error: Could not prefetch keystone_role provider 'openstack': Could
>>> not authenticate
>>> You will find full trace in log
>>>
>>> /var/tmp/packstack/20160616-133447-C9hfh9/manifests/193.124.84.22_keystone.pp.log
>>
>> ^ please paste this file so we can see more details about the error
>
>
>
> --
> Andrey Y Shevel

--
Andrey Y Shevel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160620/1ec186b9/attachment.html>