yahoo-eng-team team mailing list archive

[Colleen Murphy <colleen@xxxxxxxxxxx>]

Public bug reported:

Summary:

The keystone-manage command searches for a default keystone.conf
relative to the installed executable [1]. The result is that it will
look in <venv name>/../etc/keystone.conf. Failing to find it there, it
will search the standard oslo.cfg directories: ~/.keystone/, ~/,
/etc/keystone/, /etc/.

I can't find documentation stating keystone.conf should live at <venv
name>/../etc/keystone.conf. I can find documentation saying it should
live in the etc/ directory of the keystone source directory[2], and I
can find documentation saying it should live in one of the oslo.cfg
directories[3]. If keystone-manage searched for keystone.conf relative
to the python source file keystone/cmd/manage.py rather than the
installed binary, the instructions at [2] would work correctly and [3]
would still work as a fallback.

Steps to reproduce:

1) Follow the "Developing with Keystone" instructions
(http://docs.openstack.org/developer/keystone/developing.html), copying
etc/keystone.conf.sample to etc/keystone.conf.

2) Change the database connection string in etc/keystone.conf to
sqlite:///keystone2.db

3) Run a keystone-manage db_sync

Expected result:

A sqlite database is created in the current working directory called
keystone2.db

Actual result:

A sqlite database is created in the current working directory called
keystone.db.

[1] http://git.openstack.org/cgit/openstack/keystone/tree/keystone/cmd/manage.py#n23
[2] http://docs.openstack.org/developer/keystone/developing.html#configuring-keystone
[3] http://docs.openstack.org/developer/keystone/configuration.html#configuration-files

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1561099

Title:
  keystone-manage looks for default_config_files in the wrong place

Status in OpenStack Identity (keystone):
  New

Bug description:
  Summary:

  The keystone-manage command searches for a default keystone.conf
  relative to the installed executable [1]. The result is that it will
  look in <venv name>/../etc/keystone.conf. Failing to find it there, it
  will search the standard oslo.cfg directories: ~/.keystone/, ~/,
  /etc/keystone/, /etc/.

  I can't find documentation stating keystone.conf should live at <venv
  name>/../etc/keystone.conf. I can find documentation saying it should
  live in the etc/ directory of the keystone source directory[2], and I
  can find documentation saying it should live in one of the oslo.cfg
  directories[3]. If keystone-manage searched for keystone.conf relative
  to the python source file keystone/cmd/manage.py rather than the
  installed binary, the instructions at [2] would work correctly and [3]
  would still work as a fallback.

  Steps to reproduce:

  1) Follow the "Developing with Keystone" instructions
  (http://docs.openstack.org/developer/keystone/developing.html),
  copying etc/keystone.conf.sample to etc/keystone.conf.

  2) Change the database connection string in etc/keystone.conf to
  sqlite:///keystone2.db

  3) Run a keystone-manage db_sync

  Expected result:

  A sqlite database is created in the current working directory called
  keystone2.db

  Actual result:

  A sqlite database is created in the current working directory called
  keystone.db.

  [1] http://git.openstack.org/cgit/openstack/keystone/tree/keystone/cmd/manage.py#n23
  [2] http://docs.openstack.org/developer/keystone/developing.html#configuring-keystone
  [3] http://docs.openstack.org/developer/keystone/configuration.html#configuration-files

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1561099/+subscriptions