yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

You traced the event correctly. It comes to the compute service here:

https://github.com/openstack/nova/blob/16.0.0/nova/compute/manager.py#L6958

All that does, however, is refresh the internal newtork info cache for
the instance in the instances_info_caches table.

It doesn't do anything in the guest. Is that what you expected?

** Changed in: nova
       Status: New => Invalid

** Changed in: nova
   Importance: Undecided => Wishlist

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

Title:
  VM port state don't match Neutron's port admin state

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Dear colleagues,

  when I change port admin state to DOWN, this is not reflected
  accordingly on VM's side:

  $ openstack port set --disable n1-lan
  $ openstack port show n1-lan
  [ ... ]
  +-----------------------+------------+
  | Field                 | Value      |
  +-----------------------+------------+
  | admin_state_up        | DOWN       |
  [ ... ]
  +-----------------------+------------+

  root@n1:~# ip a
  [ ... ]
  3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc pfifo_fast state UP group default qlen 1000

  BUT when using "virsh domif-setlink --domain <domID> --interface <MAC>
  --state down" I'm getting correct "NO-CARRIER" signaling on the port:

  3: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1450 qdisc pfifo_fast
  state DOWN group default qlen 1000

  Possibly, Nova misses messages from Neutron about port admin state
  change. Is it bug or feature and can this be fixed?

  My environment:

  Openstack version: Pike
  Host OS: Ubuntu 16.04.3
  Nova: 16.0.0-0ubuntu1~cloud0
  Neutron: 11.0.0-0ubuntu1~cloud0
  Networking: Openvswitch 2.8.0-0ubuntu1~cloud0
  Hypevisor: Libvirt+KVM
  Storage: CEPH 12.2.0-0ubuntu1~cloud0

  Thank you.

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