** Also affects: python-quantumclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1164664
Title:
Unable to install latest python-quantumclient
** Project changed: quantum => quantum (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152820
Title:
Unable to install quantum due to hash sum mismatch on python-gflags
To manage notificati
** Changed in: quantum
Milestone: grizzly-rc1 => None
** No longer affects: quantum
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153066
Title:
L3 Agent Failed sending gratuitous ARP
To manag
ah, looks like this is already addressed, missed that comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099151
Title:
Grizzly testing packages : miss a dependency
To manage notifications abou
quantum recently started depending on alembic for db migrations, since
sqlalchemy-migrate was not sufficient.
adding markmcclain to comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1099151
Titl
m
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/quantum/+bug/1097451/+subscriptions
>
--
~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~
--
You received this bug notification becau
err: ''
>
> If I run "sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
> /sbin/iptables-save -t filter" it does indeed give me an Unauthorized
> command error.
>
> If I run "sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
> ip
ap /etc/quantum/rootwrap.conf
> /sbin/iptables-save -t filter" it does indeed give me an Unauthorized
> command error.
>
> If I run "sudo /usr/bin/quantum-rootwrap /etc/quantum/rootwrap.conf
> iptables-save -t filter" (without the /sbin/) it works OK.
> Othe
adding adam to the bug, who can comment for sure, but it looks like the
issues is just "fix committed" for quantal, not "fixed released", so I
would guess its not in the latest released version for ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Changed in: quantum
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050540
Title:
quantum-server requires plugin config at the command line
To manage notificati
** Changed in: quantum
Milestone: None => grizzly-1
** Changed in: quantum
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069966
Title:
rootwrap error with L3 a
Adding Adam, as I thought this had already been addressed in the ubuntu
packaging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070322
Title:
again creation of quantum db
To manage notifications
I have confirmed that the updated packages solve the issue by doing a
devstack install on standard precise, seeing the issue, upgrading the
ovs packages manually via deb, rebooting the system to load the new
kernel module, and then testing that the issue is no longer seen.
thanks!
** Tags removed:
** Changed in: quantum
Milestone: None => folsom-rc2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052522
Title:
L3 plugin exists / dies when external bridge isn't up
To manage notifications a
Yeah, the traceback is unrelated. The bug is valid though, as even if
the bridge is configured, if the l3-agent starts before OVS, the
l3-agent will exit permanently, which is obviously bad.
I do think there's probably a decent argument to be made that the lack
of an external bridge should probab
** Changed in: quantum
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052522
Title:
L3 plugin exists / dies when external bridge isn't up
To manage notifications a
** Changed in: quantum
Status: New => Confirmed
** Changed in: quantum
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052522
Title:
L3 plugin exists / dies
Emilien, can this be closed? Seems like you're now able to run
'quantum' commands, just maybe not the exact latest CLI?
** No longer affects: quantum
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/104
** No longer affects: quantum
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044318
Title:
[SRU] pre-1.5 OVS has trouble with floating ips when pinging from the
same box
To manage notifications a
Thanks for the quick action on this folks. Let me know when something
is available to test (not sure how 'Fix Committed' state corresponds to
availability of new packages via apt).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I'm not sure what you exactly mean by deprecated, but there was a
subnstantial update to the python-quantumclient functionality during
Folsom which may require some packaging attention.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
To clarify my previous comment, this is not an issue with the packaging,
it is a bug in OVS. I removed it from quantum RC1 as there was not code
that needed to be committed to quantum to fix the issue, simply that
distros needed to create new packages with the fix.
Again, here is the OVS change:
** No longer affects: quantum
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1045064
Title:
Impossible to run Quantum Server from testing packages
To manage notifications about this bug go to:
https
removing from milestone for quantum, as this is a purely packaging
issue.
** Changed in: quantum
Milestone: folsom-rc1 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044318
Title:
pre-1
This error is usually the result of gettext.install() was not called,
but it should be called any time something in the quantum package is
loaded, based on this grep:
./__init__.py:import gettext
./__init__.py:gettext.install('quantum', unicode=1)
My guess is that this is packaging related, since
Great, thanks Clint! Aaron (subscribed to this bug) will do
verification on this. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021530
Title:
[SRU] update to include stable fixes for OVS
hi aaron, I checked with a member of the ovs team and they confirmed
that the additional include header was not strictly necessary for the
patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021530
** Project changed: quantum => quantum (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1021921
Title:
it's not possible to quantum-plugin-openvswitch-agent
To manage notifications about thi
Thanks Adam. I had the developer confirm that the path looks good.
Adding Aaron Rosen from Nicira to the bug, as he will be the one to grab
the new PPA and confirm that it fixes the issue. Thanks again for the
quick response.
--
You received this bug notification because you are a member of Ub
Hi Adam, James,
Thanks for the quick response.
The upstream change is here: http://openvswitch.org/cgi-
bin/gitweb.cgi?p=openvswitch;a=commit;h=11f84dce005dd14a374ab2ef5f8c25bcf8285a36
In our testing, VMs frequently send out IPv6 neighbor discovery packets
(the v6 equivalent of ARP) during boot.
Public bug reported:
Hello,
I'm the lead of the OpenStack Quantum project, which uses OVS on Ubuntu
precise quite heavily.
We have a bug fix for an issue in Quantum that necessarily triggers a
bug in OVS 1.4.0 that has been fixed in the stable 1.4.2 release. We
want to push our fix, but pushing
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816754
Title:
add ovs-vsctl to sudoers file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/8
to be precise, unbuntu's apt-get seems to install ovs-vsctl in:
/usr/sbin/ovs-vsctl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816754
Title:
add ovs-vsctl to sudoers file
To manage notifications
Public bug reported:
The diablo-3 release of nova now includes the option to use Open vSwitch
in addition to the Linux Bridge for VM networking.
As a result, the nova code now calls the "ovs-vsctl" utility using sudo,
so I believe this means that ovs-vsctl should be added to the nova
sudoers file
34 matches
Mail list logo
