legacy_endpoint_id actually stored in 'extra'

Bug #1154918 reported by Dolph Mathews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Low
Dolph Mathews

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|{}

Dolph Mathews (dolph)
tags: added: grizzly-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to keystone (master)

Fix proposed to branch: master
Review: https://review.openstack.org/24397

Changed in keystone:
assignee: nobody → Dolph Mathews (dolph)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to keystone (master)

Reviewed: https://review.openstack.org/24397
Committed: http://github.com/openstack/keystone/commit/85910ce347e618d604a7421e95e5984c13f73f10
Submitter: Jenkins
Branch: master

commit 85910ce347e618d604a7421e95e5984c13f73f10
Author: Dolph Mathews <email address hidden>
Date: Wed Mar 13 21:46:27 2013 -0500

    Utilize legacy_endpoint_id column (bug 1154918)

    This column was created in migration 11 but isn't used because it wasn't
    added to the model definition. Attempting to store data here ended up
    putting it into 'extra'.

    Change-Id: I02680b5213f09fe3cddcf5365104554d3e6d6b8a

Changed in keystone:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
tags: removed: grizzly-rc-potential
Thierry Carrez (ttx)
Changed in keystone:
milestone: none → grizzly-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in keystone:
milestone: grizzly-rc1 → 2013.1
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.