← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1487005] Re: unable to modify 'Allocation Pools' after creating a subnet

 

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

commit fb804ac4ada82c862905a1f24069ee78c6e8fe4e
Author: Bo Wang <bo.wang@xxxxxxxxxxxx>
Date:   Mon Jan 4 21:02:44 2016 +0800

    Fix workflow bug in "Create Network" dialog
    
    In "Subnet Info" tab, the button "Next" will hide and
    button "Create" will show if checked Disable Gateway.
    Because value of hide_tab is undefined but transformed to
    hide_tab = ['undefined'] in js code.
    
    Remove unused ',' which will introduce empty element in list:
    String(['a', 'b',]).split(,) --> ['a', 'b', '']
    
    Switching field "address_source" should not trigger
    field "gateway_ip" show/disappear.
    
    Closes-Bug: #1487005
    Closes-Bug: #1530729
    Closes-Bug: #1569942
    Change-Id: If9e417e151e11c8ee46ded50ee3ee8108ed777a4


** Changed in: horizon
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1487005

Title:
  unable to modify 'Allocation Pools' after creating a subnet

Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  Modifying subnet 'Allocation Pools' is impossible after creating via
  Horizon GUI

  From nuetron CLI works:
  neutron subnet-update ce373461-08a4-4974-95d0-75ebf328a62f --allocation-pool 'start=192.168.1.10,end=192.168.1.254'


  1.Create a network
  2. create a subnet
  3. check the disable gateway
  4. edit the subnet: project --> newly created network --> click edit subnet in the relevant subnet
  4. change the  'Allocation Pools' so it will start valid from 192.168.1.2-192.168.1.254
  5. click save
  6. save message success - but in fact nothing has changed, the Allocation pools did not change

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1487005/+subscriptions


References