[Openstack] How to get around bug 1135948
Hi All, I am trying to find out how to get around this bug : https://bugs.launchpad.net/quantum/+bug/1135948 in FOLSOM release. I saw in the bug's history that it was fixed and released on 2013-03-13, which means that it's has been included in grizzly-rc1 but unfortunately grizzly-rc1 packages are not available yet for DEBIAN. Do you know to get around this bug in FOLSOM or 2013.1~g3-1 packages? It's the last obstacle, I hope, which prevents me from pinging a VM. Thanks for your time and help. Amine. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] How to get around bug 1135948
I don't think that bug is preventing you from pinging your instances. That bug just cleans up left over dnsmaq processes after a network has been deleted while the quantum dhcp agent was down. If you stop the quantum dhcp agent; sudo pkill dnsmaq ; start quantum-dhcp agent that should do the clean up I believe. But I don't think this is stopping you from pinging. Aaron On Thu, Mar 28, 2013 at 7:46 AM, Mohammed Amine SAYA < asaya.openst...@gmail.com> wrote: > Hi All, > > I am trying to find out how to get around this bug : > https://bugs.launchpad.net/quantum/+bug/1135948 in FOLSOM release. > > I saw in the bug's history that it was fixed and released on 2013-03-13, > which means that it's has been included in grizzly-rc1 but unfortunately > grizzly-rc1 packages are not available yet for DEBIAN. > > Do you know to get around this bug in FOLSOM or 2013.1~g3-1 packages? > > It's the last obstacle, I hope, which prevents me from pinging a VM. > > Thanks for your time and help. > Amine. > > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] How to get around bug 1135948
Hi Aaron, Thanks a lot for your answer. I couldn't follow up the discussion because I was on vacation. Before I dive in any debug, I am going to switch to grizzly release and then try to launch a VM. I'll get back to you if I face the same issue. Best regards, Amine. On Fri, Mar 29, 2013 at 8:29 AM, Aaron Rosen wrote: > I don't think that bug is preventing you from pinging your instances. That > bug just cleans up left over dnsmaq processes after a network has been > deleted while the quantum dhcp agent was down. > > If you stop the quantum dhcp agent; sudo pkill dnsmaq ; start quantum-dhcp > agent that should do the clean up I believe. But I don't think this is > stopping you from pinging. > > Aaron > > On Thu, Mar 28, 2013 at 7:46 AM, Mohammed Amine SAYA < > asaya.openst...@gmail.com> wrote: > >> Hi All, >> >> I am trying to find out how to get around this bug : >> https://bugs.launchpad.net/quantum/+bug/1135948 in FOLSOM release. >> >> I saw in the bug's history that it was fixed and released on 2013-03-13, >> which means that it's has been included in grizzly-rc1 but unfortunately >> grizzly-rc1 packages are not available yet for DEBIAN. >> >> Do you know to get around this bug in FOLSOM or 2013.1~g3-1 packages? >> >> It's the last obstacle, I hope, which prevents me from pinging a VM. >> >> Thanks for your time and help. >> Amine. >> >> ___ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
