Hi, it would be good if you can confirm whether this behaviour affects icehouse or trunk as well. Several bugs concerning nova/neutron communication as well as ovs agent handling of ports have been fixed during the last two release cycle. While the stable team did a great job in back-porting those fixes, some were not applied because they were too extensive. Are these "leftover" ports only present on the OVS agent, or do you see them in neutron as well? In the former case the problem might be mitigated as suggested by Martinx.
Another thing to check is whether these ports are wired or not. If they are on the "dead" VLAN (4095), then they're not wired, and while they surely represent a nuisance they will not be harmful. As Havana is now approaching EOL [1], I would focus on establishing whether this behaviour affects more recent releases as well. Regards, Salvatore [1] https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2Fhavana_releases On 28 August 2014 04:14, Martinx - ジェームズ <[email protected]> wrote: > Sometimes I need to run "sudo service neutron-ovs-cleanup restart ; sudo > reboot", on both Network Node and/or at the Compute Nodes too... > Rebooting alone isn't allways enough... > > > On 27 August 2014 20:37, 严超 <[email protected]> wrote: > >> Same questions here. I sometimes use ovs-vsctl command before manually. >> >> *Best Regards！* >> >> >> *Chao Yan--------------**My twitter：Andy Yan @yanchao727 >> <https://twitter.com/yanchao727>* >> >> >> *My Weibo：http://weibo.com/herewearenow >> <http://weibo.com/herewearenow>--------------* >> >> >> 2014-08-28 5:26 GMT+08:00 Sławek Kapłoński <[email protected]>: >> >>> Hello, >>> >>> I'm using Openstack havana release with neutron. Neutron is with ML2 >>> plugin >>> and ovs_agents on hosts. Today I found that if for some reason compute >>> host is >>> for example rebooted and before restartt there was some instances on >>> host than >>> after restart instances are in state "SHUTOFF" and are not configured in >>> virsh >>> on compute host but nova-compute not remove ports from openvswitch br-int >>> bridge and I ovs agent see those ports are still configured on host. >>> Is it known bug maybe? Maybe someone of You know some solution of that? >>> Thanks >>> in advance for any info about that. >>> >>> -- >>> Pozdrawiam, >>> Sławek Kapłoński >>> [email protected] >>> >>> -- >>> Klucz GPG można pobrać ze strony: >>> http://kaplonski.pl/files/slawek_kaplonski.pub.key >>> -- >>> My public GPG key can be downloaded from: >>> http://kaplonski.pl/files/slawek_kaplonski.pub.key >>> _______________________________________________ >>> Mailing list: >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> Post to : [email protected] >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >> >> _______________________________________________ >> Mailing list: >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> Post to : [email protected] >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> >> > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
