In the admin panel, the subnet page shows that the available IP is less than 0

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

Bug Description

We create 5 ports in advance,Then edit the subnet and set the range of the allocation_pools value to 10.10.10.3-10.10.10.4,We will find that the available ip becomes negative

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/649961

Changed in horizon:
status: New → In Progress
Revision history for this message
Akihiro Motoki (amotoki) wrote :

Is this a problem of horizon? If the neutron API returns a negative value, it should be fixed in neutron rather than horizon.

Revision history for this message
pengyuesheng (pengyuesheng) wrote :

No,The result is calculated by horizon, not neutron API returns

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

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

commit 18e9918d320228d4a0551eb9feaaebd5f82c9941
Author: pengyuesheng <email address hidden>
Date: Thu Apr 4 17:55:31 2019 +0800

    Adjusts subnet_free_ips to 0 when it is negative

    In subnet page under admin panel,
    Subnet_free_ips is negative if the subnet's allocation_pools
    range is less than the used IPs of the subnet.
    This patch adjusts subnet_free_ips to 0 when it is negative.

    Change-Id: I3f1441bf5e4eb3017024db2865adf3296127793e
    Closes-Bug: #1823149

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.