yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1444108@xxxxxxxxxxxxxxxxxx>]

[Expired for Keystone because there has been no activity for 60 days.]

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1444108

Title:
  Upgrade of services from Juno to Kilo fails

Status in OpenStack Identity (Keystone):
  Expired

Bug description:
  Steps to reproduce:

  1. Install glance, cinder, nova and keystone services on Stable/Juno branch.
  2. Update the branch to master, do 'sudo python setup.py install’ on all the services  and do a db sync on all the services.
  3. Restart all the services.
  4. The nova and cinder services restart properly. In fact, I am able to do all sanity testing operations. Keystone though intermittently stops working. And doing cinder-list or nova-list gives either http://paste.openstack.org/show/yR4bFyzry9Lrhfp6nPWg/ or gives the listing of the volumes and instances on the host.
  5. What I concluded was that Upgrading from Juno to Kilo has not been documented anywhere yet. I think I might be missing some secret sauce for keystone to start working correctly and stop giving intermittent errors. So, is there an official documentation like the one that exists for Icehouse to Kilo upgrade (http://docs.openstack.org/openstack-ops/content/upgrade-icehouse-juno.html) ? If not, then am I missing something in /etc/keystone/keystone.conf ?

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