Metadata widget stopped working

[Julie Gravel]

I tried the "Update Metadata" widget in Admin -> Flavors and Admin -> Images. They both used to display the list of available metadata on the left table. Users can then add them to the Existing Metadata table on the right by clicking on the "+" icon. Now the available metadata no longer shows up on the left table. Instead, there's a message "No available metadata".

Another issue is that the "Other" box is no longer working. I entered a new metadata key into the box and clicked "+". The key was not added to the existing metadata list. It was displayed down in the description area below ( see attachment ).

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 242943f3a8cbf772ce92a00ed2503f059408f678
Author: Travis Tripp <email address hidden>
Date: Tue Jan 13 18:15:45 2015 -0700

    Update Metadata Widget to angular 1.3.7

    Following stopped working with update to angular 1.3.7

     - Available metadata (type a filter to see it)
     - Adding metadata from left to right
     - Existing metadata
     - Saving metadata

    There are numerous things that have changed in angular 1.3.7
    from the previous angular 1.2.x.

    The view of available metadata and existing metadata was affected
    by the array filter no longer handling undefined for the $ input argument.

    The + over and saving metadata were affected by this change:
    !! in filters is now !null
     http://stackoverflow.com/questions/18644412/angularjs-filter-not-null

    ng-pattern changed in 1.3.x

    http://stackoverflow.com/questions/26439161/
    angularjs-validation-behaves-differently-for-1-3-0-and-1-2-6

    It now works in flavors and host aggregates, but still has an issue in images.
    The images issues appears to be unrelated, but caused by a javascript error
    on the images page itself.

    Change-Id: I4a2c9f29fdbc6bfc316e3b3b0000817d1516aaa2
    Partial-Bug: #1410583