Changing of port Admin State doesn't work correctly

Bug #1634480 reported by Ilya Bumarskov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel NSX-T plugin
Invalid
Medium
Igor Zinovik

Bug Description

Fuel 9.1 with NSX-t plugin 1.0.0 build#10.17.2016

Steps to reproduce:
   - Create env with vCenter and DVS plugin
   - Add following nodes:
         * Controller
         * Controller
         * Controller
         * Compute, cinder
         * Compute-vmware, cinder-vmware
   - Configure VMware vCenter Settings. Add 2 vSphere clusters and configure Nova Compute instances on controllers and compute-vmware.
   - Deploy env
   - Login to Horizon
   - Create instance run ping to external net (ping 8.8.8.8)
   - Navigate to Admin > System > Networks
   - Choose any netwrok
   - Try to change admin state for port

Observed behaviour:
There is three various scenarios
1) If port was attached to instance after changing state it becomes "deatached"
2) If port was attached to dhcp it becomes "deatached" and new port with "network:dhcp" attached device will be created.
3) If port was attached to router_interface we can't change admin state (Error: Failed to update port)

summary: - Changing the port admin state doesn't work correctly
+ Changing of port Admin State doesn't work correctly
Changed in fuel-plugin-nsx-t:
importance: Undecided → Low
milestone: none → 1.0.0
importance: Low → Medium
assignee: nobody → Igor Zinovik (izinovik)
Revision history for this message
Igor Zinovik (izinovik) wrote :

Looks like there is a limitation in NSX Manager which does not allow to change logical port state.

Snippet from neutron-server.log:
...
2016-10-18 14:56:22.716 6960 ERROR neutron.api.v2.resource ManagerError: Unexpected error from backend manager (['172.16.0.249']) for PUT api/v1/logical-ports/3879d6fd-8b21-4b22-a184-2f92a4b26936 : admin_status DOWN is not supported for Lo
gical port attached to a Logical Router Port or a Bridge Endpoint. LogicalPort id : 3879d6fd-8b21-4b22-a184-2f92a4b26936

Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

Can't reproduce this bug with NSX-t 1.0.0 build#76.

Changed in fuel-plugin-nsx-t:
status: New → Invalid
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.