yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Also affects: python-keystoneclient
   Importance: Undecided
       Status: New

** Changed in: python-keystoneclient
       Status: New => Confirmed

** Changed in: python-keystoneclient
   Importance: Undecided => Critical

** Also affects: keystone/folsom
   Importance: Undecided
       Status: New

** Changed in: keystone/folsom
       Status: New => Confirmed

** Changed in: keystone
       Status: Incomplete => Invalid

** Changed in: keystone/folsom
   Importance: Undecided => Critical

** No longer affects: nova

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

Title:
  undefined signing_dir does not work

Status in OpenStack Identity (Keystone):
  Invalid
Status in Keystone folsom series:
  Confirmed
Status in Python client library for Keystone:
  Confirmed
Status in openSUSE:
  New

Bug description:
  SUSE's automated system testing found a regression for Folsom from the
  fix of bug 1174608

  first failing:
  http://ci.opensuse.org/view/Cloud/job/openstack-cleanvm/openstack_version=folsom,slave=cloud-cleanvm/79/
  last working:
  http://ci.opensuse.org/view/Cloud/job/openstack-cleanvm/openstack_version=folsom,slave=cloud-cleanvm/77/

  The problem is that signing_dir is no more defined in /etc/nova/api-paste.ini and now defaults to $HOME/keystone-signing
  but the init script does not have HOME setup at all or set to /root and the nova user does not have write-access to the /root/keystone-signing directory.

  The nova-api process should likely use getpwent to determine the real
  home dir instead of relying on $HOME, which is usually not meaningful
  during system startup.

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