yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1154918] Re: legacy_endpoint_id actually stored in 'extra'

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>
Date: Thu, 21 Mar 2013 15:19:58 -0000
Reply-to: Bug 1154918 <1154918@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: keystone
       Status: Fix Committed => Fix Released

** Changed in: keystone
    Milestone: None => grizzly-rc1

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

Title:
  legacy_endpoint_id actually stored in 'extra'

Status in OpenStack Identity (Keystone):
  Fix Released

Bug description:
  Migration 11 creates a column on the endpoint table called
  legacy_endpoint_id, which the v2 controllers attempt to utilize.

  This is the sqlite output for the following command after creating an
  endpoint in v2:

    SELECT legacy_endpoint_id, extra from endpoint;

    |{"legacy_endpoint_id": "0d2d092634534252ace27e1e3c128209"}

  Note that the legacy_endpoint_id is null and the attribute is stashed
  into extra. Extra should be empty, e.g.:

    0d2d092634534252ace27e1e3c128209|{}

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