Images registration is using old registration technique

Bug #1592543 reported by Matt Borland
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Matt Borland

Bug Description

The Images module is using an experimental version of getResourceType() to register names instead of the .setNames() registry feature.

Tags: angularjs
Changed in horizon:
status: New → Confirmed
milestone: none → newton-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

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

Changed in horizon:
assignee: nobody → Matt Borland (palecrow)
status: Confirmed → In Progress
Matt Borland (palecrow)
tags: added: angularjs
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/329656
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=f85891aa8a3788ef59d14057fc8ceb83dc6bc3f3
Submitter: Jenkins
Branch: master

commit f85891aa8a3788ef59d14057fc8ceb83dc6bc3f3
Author: Matt Borland <email address hidden>
Date: Tue Jun 14 13:54:38 2016 -0600

    Register Image Names via .setNames()

    The Image registry is using an unsupported method of setting values for names.
    This patch fixes that by using the supported .setNames() method.

    Change-Id: I54ea5bea45ce71c8ca60683bcb55aff6d3f5aa9a
    Closes-Bug: 1592543

Changed in horizon:
status: In Progress → Fix Released
Changed in horizon:
importance: Undecided → Low
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/horizon 10.0.0.0b2

This issue was fixed in the openstack/horizon 10.0.0.0b2 development milestone.

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.