Public bug reported: Creating a multisegment network and then updating the vlan segmenetation ID of only one of the segment succeeds but it doesn't update. When a show of the network is done we observe that netowrk segment id is not updated.
Expected Behavior: A user should expect an error if update is not supported (or) the update should succeed correctly. In the above scenario, we don't see either of them occurring. Furthermore, this would also mean that when plugin calls update_precommit and update_post commit, it sets the data present in database from create in call context instead of setting the user provided data in the context. Also there were no ports created in the network. Output of the commands to reproduce are available at : http://paste.openstack.org/show/749350/ Openstack version: master Deployment: devstack Distro: Ubuntu ** Affects: neutron Importance: Undecided Status: New ** Tags: mutlsegment networks update ** Summary changed: - updating multisegment network does not raise error and it dosen't work + updating multisegment network segmentation id does not raise error and although the update succeeds it doesn't work ** Tags added: mutlsegment networks ** Tags added: update -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1824988 Title: updating multisegment network segmentation id does not raise error and although the update succeeds it doesn't work Status in neutron: New Bug description: Creating a multisegment network and then updating the vlan segmenetation ID of only one of the segment succeeds but it doesn't update. When a show of the network is done we observe that netowrk segment id is not updated. Expected Behavior: A user should expect an error if update is not supported (or) the update should succeed correctly. In the above scenario, we don't see either of them occurring. Furthermore, this would also mean that when plugin calls update_precommit and update_post commit, it sets the data present in database from create in call context instead of setting the user provided data in the context. Also there were no ports created in the network. Output of the commands to reproduce are available at : http://paste.openstack.org/show/749350/ Openstack version: master Deployment: devstack Distro: Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1824988/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
