[Bug 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..
Used neutron 1:2014.1.5-0ubuntu4 from trusty-proposed, confirmed that didn't have such problem. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1393391 Title: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port- update_fanout.. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1393391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..
Corey, Thank you very much for your efforts. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1393391 Title: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port- update_fanout.. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1393391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..
Corey, Thanks for looking at it, I will keep watching it for the new updates and please help to update it if there is any news, thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1393391 Title: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port- update_fanout.. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1393391/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
Hi Corey, Thanks for the fixing. And I am using 'sudo adt-run neutron -U --apt-pocket=proposed --- qemu adt-trusty-amd64-cloud.img -d -o /tmp/neutron/' for running the pkgtest. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
Hello all, After reproducing the test on my environment, the error is reported as: The following packages have unmet dependencies: neutron-plugin-hyperv : Depends: neutron-common (= 1:2014.1.5-0ubuntu1) but 1:2014.1.5-0ubuntu2 is to be installed adt-run: & apt0t-hyperv-plugin: - - - - - - - - - - stderr - - - - - - - - - - E: Unable to correct problems, you have held broken packages. It seems unrelated with the neutron fix in the patch but other dependency problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
Hi Serge, Brian, Thanks for looking at it, could the auto package tests re-run again or some other approach to identify the failure, since I can't see how this simple fix can break brocade-plugin showed in http://autopkgtest.ubuntu.com/packages/n/neutron/trusty/armhf/, plus if it has passed the -proposal which if running the neutron tests, it should be work for -updates as well. brocade-plugin FAIL non-zero exit status 1 Thanks guys. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
Ah, maybe I could reproduce here https://wiki.ubuntu.com/ProposedMigration#autopkgtests -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
Used neutron 1:2014.1.5-0ubuntu2 and oslo.messaging 1.3.0-0ubuntu1.4 from trusty-proposed, confirmed that didn't have such problem. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Patch added: "backport-1318721-trusty-juno.debdiff" https://bugs.launchpad.net/neutron/+bug/1318721/+attachment/4546091/+files/backport-1318721-trusty-juno.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Patch added: "backport-1318721-trusty-icehouse-neutron.debdiff" https://bugs.launchpad.net/neutron/+bug/1318721/+attachment/4546093/+files/backport-1318721-trusty-icehouse-neutron.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Patch added: "backport-1318721-trusty-icehouse.debdiff" https://bugs.launchpad.net/neutron/+bug/1318721/+attachment/4546092/+files/backport-1318721-trusty-icehouse.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Branch linked: lp:~xianghui/ubuntu/trusty/neutron/lp1318721 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1318721] Re: RPC timeout in all neutron agents
** Branch linked: lp:~xianghui/ubuntu/trusty/oslo.messaging/lp1318721 ** Branch unlinked: lp:ubuntu/trusty-proposed/oslo.messaging -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1318721 Title: RPC timeout in all neutron agents To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1318721/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1513367] [NEW] qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled
Public bug reported: This bug is seperate from bug https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532 to focus on the error. I have been trying to redeploy the environment, for this time, the error is not about kvm-spice, it is qemu-system-x86_64 got the same problem. Due to /usr/bin/qemu-system-x86_64 is a bin file, I am not able to put the strace there. And I don't know why suddenly /usr/bin/kvm-spice has been replaced by /usr/bin/qemu-systerm-x86_64. 2015-11-05 15:36:15.491 DEBUG nova.compute.utils [req-b292f304-014b-479f-af5d-38b96309f78f admin admin] [instance: 3dceb341-643d-492a-8a47-8154da341c02] internal error: Process exited prior to exec: libvirt: error : unable to set AppArmor profile 'libvirt-3dceb341-643d-492a-8a47-8154da341c02' for '/usr/bin/qemu-system-x86_64': No such file or directory from (pid=12236) notify_about_instance_usage /opt/stack/nova/nova/compute/utils.py:284 2015-11-05 15:36:15.492 DEBUG nova.compute.manager [req-b292f304-014b-479f-af5d-38b96309f78f admin admin] [instance: 3dceb341-643d-492a-8a47-8154da341c02] Build of instance 3dceb341-643d-492a-8a47-8154da341c02 was re-scheduled: internal error: Process exited prior to exec: libvirt: error : unable to set AppArmor profile 'libvirt-3dceb341-643d-492a-8a47-8154da341c02' for '/usr/bin/qemu-system-x86_64': No such file or directory Let me know what's the next step for further analysis. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1513367 Title: qemu-system-x86_64/kvm-spice failed to boot a vm with appmor enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1513367/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405588] Re: database connection failed (Protocol error)
** Description changed: Versions: root@juju-xh-machine-5:~# dpkg -l|grep openvswitch ii openvswitch-common 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch common components ii openvswitch-switch 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch switch implementations root@juju-xh-machine-5:~# uname -a Linux juju-precise-machine-5 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@juju-xh-machine-5:~# cat /etc/issue Ubuntu 14.04.1 LTS \n \l + + root@juju-precise-machine-5:/var/log/neutron# dpkg -l|grep neutron + ii neutron-common 1:2014.1.3-0ubuntu1.1 all Neutron is a virtual network service for Openstack - common + ii neutron-plugin-ml2 1:2014.1.3-0ubuntu1.1 all Neutron is a virtual network service for Openstack - ML2 plugin + ii neutron-plugin-openvswitch-agent 1:2014.1.3-0ubuntu1.1 all Neutron is a virtual network service for Openstack - Open vSwitch plugin agent + ii python-neutron 1:2014.1.3-0ubuntu1.1 all Neutron is a virutal network service for Openstack - Python Erros: root@juju-xh-machine-5:~# ovs-vsctl show 2014-12-25T09:26:56Z|1|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (Protocol error) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (Protocol error) root@juju-precise-machine-5:~# tail -f /var/log/neutron/openvswitch-agent.log 2014-12-25 09:37:03.990 20991 ERROR neutron.agent.linux.ovsdb_monitor [-] Error received from ovsdb monitor: ovsdb-client: unix:/var/run/openvswitch/db.sock: receive failed (End of file) 2014-12-25 09:44:53.796 20991 ERROR neutron.agent.linux.ovsdb_monitor [-] Error received from ovsdb monitor: 2014-12-25T09:44:53Z|1|fatal_signal|WARN|terminating with signal 15 (Terminated) Workaround: restart openvswitch-switch But ovs-vsctl will get this error every several minutes, this caused neutron-plugin-openvswitch-agent keep reporting errors since ovs-vsctl is wrong. + + The root cause is : + Neutron agent will call ovs monitor to get interfaces info, but ovs monitor process will be respawned every 'respawn_interval' minutes due to get error output 'sudo: unable to resolve host juju-precise-machine-5' when running command 'sudo neutron-rootwrap /etc/neutron/rootwrap.conf ovsdb-client monitor Interface name,ofport --format=json', after several times the ovs db socket is reconnected for multiple times, however, some of them are not released well, and it goes to the maxim limit of socket number, which leads to connect to ovsdb server failed. + + Currently, one possible fix in code is to add hostname to /etc/hosts + followed by 127.0.0.1 or localhost to avoid the error 'sudo: unable to + resolve host juju-precise-machine-5' in openvswitch charm. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1405588 Title: database connection failed (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1405588/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405588] Re: database connection failed (Protocol error)
** Also affects: quantum-gateway (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: nova-compute (Juju Charms Collection) Importance: Undecided Status: New ** Changed in: quantum-gateway (Juju Charms Collection) Importance: Undecided = Critical ** Changed in: nova-compute (Juju Charms Collection) Importance: Undecided = Critical ** Also affects: neutron-openvswitch (Juju Charms Collection) Importance: Undecided Status: New ** Changed in: neutron-openvswitch (Juju Charms Collection) Importance: Undecided = Critical ** Changed in: neutron-openvswitch (Juju Charms Collection) Assignee: (unassigned) = Hua Zhang (zhhuabj) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1405588 Title: database connection failed (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1405588/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405588] [NEW] database connection failed (Protocol error)
Public bug reported: Versions: root@juju-xh-machine-5:~# dpkg -l|grep openvswitch ii openvswitch-common 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch common components ii openvswitch-switch 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch switch implementations root@juju-xh-machine-5:~# uname -a Linux juju-precise-machine-5 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@juju-xh-machine-5:~# cat /etc/issue Ubuntu 14.04.1 LTS \n \l Erros: root@juju-xh-machine-5:~# ovs-vsctl show 2014-12-25T09:26:56Z|1|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (Protocol error) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (Protocol error) root@juju-precise-machine-5:~# tail -f /var/log/neutron/openvswitch-agent.log 2014-12-25 09:37:03.990 20991 ERROR neutron.agent.linux.ovsdb_monitor [-] Error received from ovsdb monitor: ovsdb-client: unix:/var/run/openvswitch/db.sock: receive failed (End of file) Workaround: restart openvswitch-switch But ovs-vsctl will get this error every several minutes, this caused neutron-plugin-openvswitch-agent keep reporting errors since ovs-vsctl is wrong. ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1405588 Title: database connection failed (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1405588/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405588] Re: database connection failed (Protocol error)
** Description changed: + Versions: root@juju-xh-machine-5:~# dpkg -l|grep openvswitch ii openvswitch-common 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch common components ii openvswitch-switch 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch switch implementations root@juju-xh-machine-5:~# uname -a Linux juju-precise-machine-5 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@juju-xh-machine-5:~# cat /etc/issue Ubuntu 14.04.1 LTS \n \l + Erros: root@juju-xh-machine-5:~# ovs-vsctl show 2014-12-25T09:26:56Z|1|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (Protocol error) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (Protocol error) + root@juju-precise-machine-5:~# tail -f /var/log/neutron/openvswitch-agent.log + 2014-12-25 09:37:03.990 20991 ERROR neutron.agent.linux.ovsdb_monitor [-] Error received from ovsdb monitor: ovsdb-client: unix:/var/run/openvswitch/db.sock: receive failed (End of file) - workaround: + Workaround: restart openvswitch-switch - But ovs-vsctl will get this error every several minutes. + But ovs-vsctl will get this error every several minutes, this caused + neutron-plugin-openvswitch-agent keep reporting errors since ovs-vsctl + is wrong. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1405588 Title: database connection failed (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1405588/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405588] Re: database connection failed (Protocol error)
** Description changed: Versions: root@juju-xh-machine-5:~# dpkg -l|grep openvswitch ii openvswitch-common 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch common components ii openvswitch-switch 2.0.2-0ubuntu0.14.04.1 amd64 Open vSwitch switch implementations root@juju-xh-machine-5:~# uname -a Linux juju-precise-machine-5 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux root@juju-xh-machine-5:~# cat /etc/issue Ubuntu 14.04.1 LTS \n \l Erros: root@juju-xh-machine-5:~# ovs-vsctl show 2014-12-25T09:26:56Z|1|reconnect|WARN|unix:/var/run/openvswitch/db.sock: connection attempt failed (Protocol error) ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (Protocol error) root@juju-precise-machine-5:~# tail -f /var/log/neutron/openvswitch-agent.log 2014-12-25 09:37:03.990 20991 ERROR neutron.agent.linux.ovsdb_monitor [-] Error received from ovsdb monitor: ovsdb-client: unix:/var/run/openvswitch/db.sock: receive failed (End of file) + 2014-12-25 09:44:53.796 20991 ERROR neutron.agent.linux.ovsdb_monitor [-] Error received from ovsdb monitor: 2014-12-25T09:44:53Z|1|fatal_signal|WARN|terminating with signal 15 (Terminated) Workaround: restart openvswitch-switch But ovs-vsctl will get this error every several minutes, this caused neutron-plugin-openvswitch-agent keep reporting errors since ovs-vsctl is wrong. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1405588 Title: database connection failed (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1405588/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1312507] Re: rabbitmq-server fails to start on a IPv6-Only environment/epmd is not IPv6 enabled
Verified, works for me, thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in Ubuntu. https://bugs.launchpad.net/bugs/1312507 Title: rabbitmq-server fails to start on a IPv6-Only environment/epmd is not IPv6 enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/erlang/+bug/1312507/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1204456] Re: neutron ml2 plugin test failures
Hi, When I ran run_tests.sh on ubuntu, there are always fails as below: Seems it looks like the failure above. Is there any ways to fix this? because it has blocked my commit. Thanks in advance. root@ubuntu:/opt/stack/neutron# ./run_tests.sh == FAIL: process-returncode process-returncode -- _StringException: Binary content: traceback (test/plain; charset=utf8) == FAIL: process-returncode process-returncode -- _StringException: Binary content: traceback (test/plain; charset=utf8) == FAIL: neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent neutron.tests.unit.ml2.test_agent_scheduler.Ml2AgentSchedulerTestCase.test_network_add_to_dhcp_agent -- _StringException == FAIL: neutron.tests.unit.ml2.test_security_group.TestMl2SecurityGroups.test_create_security_group_rule_tcp_protocol_as_number neutron.tests.unit.ml2.test_security_group.TestMl2SecurityGroups.test_create_security_group_rule_tcp_protocol_as_number -- _StringException -- -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1204456 Title: neutron ml2 plugin test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1204456/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
