On "Manage QoS Spec Association" form, enter '*<>%' when creating a key, the error messages is shown

Bug #1822734 reported by pengyuesheng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Undecided
pengyuesheng

Bug Description

On "Manage QoS Spec Association" form, enter '*<>%' when creating a key, the error messages is shown

Changed in horizon:
assignee: nobody → pengyuesheng (pengyuesheng)
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/649239

Changed in horizon:
status: New → In Progress
Changed in horizon:
assignee: pengyuesheng (pengyuesheng) → Ivan Kolodyazhny (e0ne)
Changed in horizon:
assignee: Ivan Kolodyazhny (e0ne) → pengyuesheng (pengyuesheng)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.opendev.org/649239
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a6fae3b1090542e19fc90797ea4396d455b8b206
Submitter: Zuul
Branch: master

commit a6fae3b1090542e19fc90797ea4396d455b8b206
Author: pengyuesheng <email address hidden>
Date: Tue Apr 2 15:30:57 2019 +0800

    Check if the key meets the cinder API validation

    In create qos spec form under the volume type panel,
    if the key does not match the regex,
    it would failed to create qos spec

    This patch implements the regex validation for the spec in qos_specs as
    implemented in cinder[1].
    [1] https://github.com/openstack/cinder/blob/master/cinder/api/validation/parameter_types.py#L150

    Change-Id: I295541ab3adb16b28ffe69cae1cfb48a3daf7d31
    Closes-Bug: #1822734

Changed in horizon:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 16.0.0.0b1

This issue was fixed in the openstack/horizon 16.0.0.0b1 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.