Here are ALL the warnings and errors I see when restarting nova and
quantum: http://pastie.org/pastes/8059837/text
Here are ALL the warnings and errors I see when creating both networks
(public and internal), the router that bridges them, assigning the public
network as the gateway, adding the int
I
did that, and I went one step further... I deleted and recreated ALL the
databases to ensure that I would be starting from scratch. I also deleted
all bridges, stopped openvswitch, deleted conf.db, started openvswitch and
recreated all the bridges.
This solved the reference to "test1-int" but
Stop quantum agents (not quantum-api) and openvswitch service. Delete
/etc/openvswitch/conf.db and delte all agents using quantum agent-delete
. Start openvswitch service and then quantum agents. If ports still
down check quantum logs mainly quantum l3-agent. If you don't find anything
interesting
Hmmm I used both of those commands, but no matter what I do I can not
remove references to "test1-int" in /etc/openvswitch/conf.db
Should I just manually replace those with the IP? Delete the file?
On Tue, Jun 18, 2013 at 1:14 PM, Filipe Manco wrote:
> Honestly I'm not sure because I've always
Honestly I'm not sure because I've always used IPs. But according to the
logs it looks so. After changing configurations you should probably run
quantum-netns-cleanup and quantum-ovs-cleanup before starting the services.
Filipe Manco
http://about.me/fmanco
2013/6/18 Samuel Winchenbach
> I thin
I think I may be onto something: http://pastie.org/pastes/8056137/text
from syslog
Jun 18 12:57:26 test1 ovs-vsctl: 1|vsctl|INFO|Called as
/usr/bin/ovs-vsctl -- --may-exist add-port br-int qvo3eb6d144-07 -- set
Interface qvo3eb6d144-07
external-ids:iface-id=3eb6d144-077e-42cf-ad2e-57c50aa0039
I have three agents running (Open vSwitch agent, DHCP agent, and L3 agent):
http://pastie.org/pastes/8055658/text
The agents listed on test3 are there because ubuntu starts them
automatically. L3 agent will never run on test3 because it doesn't even
have an external interface. Right now I am jus
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 W
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 a
>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_
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+: 8353: warning : virAuditSend:135 : Failed to
send audit message virt=kvm resrc=net reason=open vm="instance-0033"
uuid=b
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 wrote:
> Hi All,
>
> I have been stuck on a problem for a couple of days now. I am using
> Gr
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
D
13 matches
Mail list logo
