What is the status of quantum agent-list? I see on your node test3 the agents are down and you don't have openvswitch agent. I would check for the logs of the l3 agent? Have you configured the external network id on the l3 agent config file?
Filipe Manco http://about.me/fmanco 2013/6/18 Samuel Winchenbach <swinc...@gmail.com> > Hi Filipe, > > Thanks for the response. I already had the /etc/sudoers.d/quantum_sudoers > file. On a whim I added "root_helper = sudo quantum-rootwrap > /etc/quantum/rootwrap.conf" to /etc/quantum/dhcp_agent.ini and that took > care of that problem. > > I managed to remove the libvirt errors by disabling apparmor. > > All the ports on my public network are still listed as "DOWN" I have > managed to remove all of the errors and warnings from quantum but those > ports will still not come up. I really am lost. > > Thanks again for the post, I am not sure what to try next :/ > > Sam > > > On Tue, Jun 18, 2013 at 10:13 AM, Filipe Manco <filipe.ma...@gmail.com>wrote: > >> From what I can see in the logs you must create the file >> /etc/sudoers.d/quantum_sudoers with the following contents: >> >> Defaults:quantum !requiretty >> quantum ALL = (root) NOPASSWD: /usr/bin/quantum-rootwrap >> >> >> About the libvirt error edit the file /etc/libvirt/qemu.conf and add the >> following: >> >> cgroup_device_acl = [ >> "/dev/null", "/dev/full", "/dev/zero", >> "/dev/random", "/dev/urandom", >> "/dev/ptmx", "/dev/kvm", "/dev/kqemu", >> "/dev/rtc","/dev/hpet" , "/dev/net/tun" >> ] >> >> Probably this won't fix all of your issues. The logs ofI don't the l3 >> agent will be helpful. >> >> Filipe Manco >> http://about.me/fmanco >> >> >> 2013/6/18 Samuel Winchenbach <swinc...@gmail.com> >> >>> I may have found the cause of my problem, but I am unsure of the >>> solution. In my libvirt log file I found many error messages similar to >>> this: >>> >>> 2013-06-18 13:12:19.812+0000: 8353: warning : virAuditSend:135 : Failed >>> to send audit message virt=kvm resrc=net reason=open vm="instance-00000033" >>> uuid=bca8a09e-46aa-408b-81cd-2432068361c1 net=FA:16:3E:71:7F:68 >>> path="/dev/net/tun" rdev=0A:C8: Operation not permitted >>> >>> Sam >>> >>> >>> On Mon, Jun 17, 2013 at 8:52 PM, Samuel Winchenbach >>> <swinc...@gmail.com>wrote: >>> >>>> Here is a bunch more information from quantum: >>>> http://pastie.org/pastes/8053820/text >>>> >>>> If anyone has any ideas I would really appreciate it. Thanks! >>>> >>>> >>>> >>>> On Mon, Jun 17, 2013 at 5:07 PM, Samuel Winchenbach <swinc...@gmail.com >>>> > wrote: >>>> >>>>> Hi All, >>>>> >>>>> I have been stuck on a problem for a couple of days now. I am using >>>>> Grizzly on Ubuntu 12.04 LTS. I can launch vms, create networks, subnets, >>>>> routers, etc. The problem is quantum reports that all fors on the public >>>>> network are "DOWN" for example: http://pastie.org/pastes/8053283/text >>>>> >>>>> Does anyone have any hints or tips on what might be causing this, or >>>>> the errors listed below in the quantum logs? Thanks! >>>>> >>>>> quantum configuration: http://pastie.org/pastes/8053100/text >>>>> >>>>> nova configuration: http://pastie.org/pastes/8043800/text >>>>> >>>>> quantum logs: http://pastie.org/pastes/8053269/text (this is >>>>> everything logged during the creation the networks, launching of vm >>>>> instances, allocating the floating ip and assigning it to a VM) >>>>> >>>> >>>> >>> >>> _______________________________________________ >>> 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
