On 11/09/2012 12:11 AM, Dennis Jacobfeuerborn wrote:
On 11/09/2012 12:55 AM, Pádraig Brady wrote:
[SNIP]
That was the bug fixed (supposedly) by the openstack-utils
update I referenced above. What has probably happened
is that you were just ahead of your fedora mirror
(which was one of the reasons we were using a side repo for the test days).
Anyway you can update openstack-demo-install manually like:
rpm -Uvh
http://kojipkgs.fedoraproject.org//packages/openstack-utils/2012.2/6.fc18/noarch/openstack-utils-2012.2-6.fc18.noarch.rpm
I'm going to try this right away, thanks.
Note the new openstack-utils now does no keystone<->quantum setup at all,
so that horizon is happy by default. So I've just now updated:
https://fedoraproject.org/wiki/QA:Testcase_Quantum_V2
to add the required quantum keystone config steps.
I tried to set up quantum according to the docs on the test page and while
I don't get any errors it doesn't seem to work as I cannot get any packets
to the VM.
This might be related to:
https://bugzilla.redhat.com/show_bug.cgi?id=872689
It does look like the same issue.
Please update with a little info if you can,
at least to ping the assignees.
In the l3-agent.log I see this:
...
RuntimeError:
Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip',
'netns', 'exec', 'qrouter-39e52a8a-9ffe-4ba5-a625-bb7513035cbf', 'sysctl',
'-w', 'net.ipv4.ip_forward=1']
Exit code: 1
Stdout: ''
Stderr: 'mount of /sys failed: Device or resource busy\n'
As the bug mentions all "ip netns exec" calls seem to fail so this is
likely to interfere with quantum and also makes debugging difficult.
thanks,
Pádraig.
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
