keystone install problem

Bug #1710008 reported by Ramesh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-training-labs
Invalid
Undecided
Roger Luethi

Bug Description

Following error occurs from setup_keystone.sh

sudo keystone-manage credential_setup \
    --keystone-user keystone \
    --keystone-group keystone

Log info below:

nitializing Fernet key repositories.
2017-08-06 08:49:07.525 12779 INFO keystone.token.providers.fernet.utils [-] [fernet_tokens] key_repository does not appear to exist; attempting to create it
2017-08-06 08:49:07.540 12779 INFO keystone.token.providers.fernet.utils [-] Created a new key: /etc/keystone/fernet-keys/0
2017-08-06 08:49:07.551 12779 INFO keystone.token.providers.fernet.utils [-] Starting key rotation with 1 key files: ['/etc/keystone/fernet-keys/0']
2017-08-06 08:49:07.558 12779 INFO keystone.token.providers.fernet.utils [-] Current primary key is: 0
2017-08-06 08:49:07.568 12779 INFO keystone.token.providers.fernet.utils [-] Next primary key will be: 1
2017-08-06 08:49:07.573 12779 INFO keystone.token.providers.fernet.utils [-] Promoted key 0 to be the primary: 1
2017-08-06 08:49:07.580 12779 INFO keystone.token.providers.fernet.utils [-] Created a new key: /etc/keystone/fernet-keys/0
usage: keystone-manage [bootstrap|db_sync|db_version|domain_config_upload|fernet_rotate|fernet_setup|mapping_purge|mapping_engine|pki_setup|saml_idp_metadata|ssl_setup|token_flush]
keystone-manage: error: argument command: invalid choice: 'credential_setup' (choose from 'bootstrap', 'db_sync', 'db_version', 'domain_config_upload', 'fernet_rotate', 'fernet_setup', 'mapping_purge', 'mapping_engine', 'pki_setup', 'saml_idp_metadata', 'ssl_setup', 'token_flush')

Tags: keystone
Revision history for this message
Roger Luethi (rl-o) wrote :

I assume you downloaded the software from https://docs.openstack.org/training_labs/. Which version did you download?

Revision history for this message
Roger Luethi (rl-o) wrote :

I just remembered where I have seen this error before.

Check out the last line in the log you quoted: keystone-manage complains that 'credential_setup' is an invalid choice. That choice was introduced with Newton. The keystone-manage executable belongs to the keystone package. An earlier line of the same log file would tell you that an old version (say, 9.2.0) of keystone was installed. For Ocata it should be 11.0.0, 9.2 was Mitaka.

So, I guess you ran Ocata scripts on a Mitaka basedisk. This would happen if you copied the config files from Mitaka to an Ocata training-labs. Is OPENSTACK_RELEASE in config/openstack of your Ocata directory mitaka?

Can you please confirm?

Changed in labs:
assignee: nobody → Roger Luethi (rl-o)
Roger Luethi (rl-o)
Changed in labs:
status: New → In Progress
Revision history for this message
Ramesh (srame) wrote :

Thanks for the response. Yes, it looks like it is trying with 9.2.0 - not sure which configuration file is being used? Am not able to find it.Trying to find that out. Appreciate any help on this.

Revision history for this message
Roger Luethi (rl-o) wrote :

All configuration files are in labs/osbash/config. The configuration file named "openstack" contains a variable "OPENSTACK_RELEASE" which configures which basedisk is used (or which OpenStack release is downloaded and installed if the basedisk does not exist).

The configuration files ("opentack" and others) must match the version of the scripts in labs/osbash/scripts. Otherwise, the scripts may fail (as you experienced).

You seem to have configuration files (at least "openstack", maybe others) from a Newton training-labs copied into a Ocata training-labs configuration directory. Try using all the original, unchanged files from the archive you downloaded. Then it should work.

Revision history for this message
Roger Luethi (rl-o) wrote :

I opened bug 1710125 to track efforts to prevent this problem from reoccurring.

Revision history for this message
Roger Luethi (rl-o) wrote :

This was a good report, but it is not a bug as such. Closing.

Changed in labs:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.