← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1397675] [NEW] Updating admin_state_up for port with vnic_type doesn't have affect

 

Public bug reported:

Updating admin_state_up for port with binding:vnic_type='direct' doesn't
have affect:


Version
=======
RHEL7.0
openstack-neutron-2014.2-11.el7ost

How to reproduce
===============

1. Make sure you have a connectivity to the Instance with the port
attached

2. Run
#neutron port-update --admin_state_up=False <port-id>

3. Check connectivity - there is still connectivity to the Instance.

Expected resule
==============
When updating the port admin_state_up to False there should no connectivity to the instance and when updating 
admin_state_up to True there should be connectivity to the Instance.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: pci-passthrough

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1397675

Title:
  Updating admin_state_up  for port with vnic_type doesn't have affect

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Updating admin_state_up for port with binding:vnic_type='direct'
  doesn't have affect:

  
  Version
  =======
  RHEL7.0
  openstack-neutron-2014.2-11.el7ost

  How to reproduce
  ===============

  1. Make sure you have a connectivity to the Instance with the port
  attached

  2. Run
  #neutron port-update --admin_state_up=False <port-id>

  3. Check connectivity - there is still connectivity to the Instance.

  Expected resule
  ==============
  When updating the port admin_state_up to False there should no connectivity to the instance and when updating 
  admin_state_up to True there should be connectivity to the Instance.

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


Follow ups

References