65535 should be a valid port for security groups

Bug #956683 reported by Greg Althaus on 2012-03-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Low
Greg Althaus

Bug Description

The range 1..65535 can not be entered in the security port group field currently.

Python's range test is inclusive to exclusive and so 65535 is currently excluded.

Changed in horizon:
assignee: nobody → Greg Althaus (gregory-althaus)

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

Changed in horizon:
status: New → In Progress

Reviewed: https://review.openstack.org/5443
Committed: http://github.com/openstack/horizon/commit/fd3bb97a8a7b803a3eaa6a83fbf016b1979daf72
Submitter: Jenkins
Branch: master

commit fd3bb97a8a7b803a3eaa6a83fbf016b1979daf72
Author: Greg Althaus <email address hidden>
Date: Thu Mar 15 21:25:06 2012 -0700

    Port validation should include 65535

    Python's range test in inclusive to exclusive.
    Update 65535 to 65536.

    bug 956683

    Change-Id: I1e22c045ab659c8a303e9fe3823236fe3e114feb

Changed in horizon:
status: In Progress → Fix Committed
Devin Carlen (devcamcar) on 2012-03-16
Changed in horizon:
importance: Undecided → Low
milestone: none → essex-rc1
Thierry Carrez (ttx) on 2012-03-20
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in horizon:
milestone: essex-rc1 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers