Yeah - I did a blanket disable for powerpc for the time being; I'll
make it a bit more specific for my next upload.
Yeah, sorry about the trouble, I'll put it on my to-do list to find and
fix the race in the test.
--
You received this bug notification because you are a member of Ubuntu
Server
This test has a race condition. If it's causing trouble in Ubuntu
builds, then the best thing to do is to disable the test.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1189408
I pushed a fix to Open vSwitch upstream master: http://openvswitch.org
/cgi-
bin/gitweb.cgi?p=openvswitch;a=commit;h=39bbf1bd166ab5dc9a98066ee6a4e2effabca922
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
The dkms package was disabled as its not compatible with the 3.5
kernel; this decision was taken under the assumption that the upstream
kernel module was feature comparable with the dkms provided kernel
module.
That's right, the Open vSwitch FAQ says:
Q: What features are not available in the
Any chance you could take a look at the proposed cherry pick patches
in the branch to see if they look sane?
I'd be glad to do so, but I'm not having any luck finding the proposed
cherry pick patches. (I always have a terrible time finding my way
around launchpad.)
--
You received this bug
I managed to find the patches.
All of those patches seem reasonable to me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1068365
Title:
openvswitch gre tunnels not working in
I am only asking that the server team look at your work here.
Oh, thanks for clarifying, I hadn't made that connection. That makes
sense, thank you.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
While not a condition of this MIR, IMHO it would be good to coordinate
with Ben to see if what is happening for wheezy is good for 12.10.
I'm not sure what I'm being asked here, can you be more explicit?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This could presumably be fixed by applying upstream commit 3d192f8e5655
datapath: Use ETH_ALEN instead of VLAN_ETH_ALEN. I don't think that
OVS branch-1.4 is supposed to support kernel 3.5 however.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I hope that you guys at Ubuntu are aware that I'm proposing an
alternative to get into Debian wheezy, as opposed to what's in Debian
sid at the moment. The full details are at: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=683771
(I proposed this weeks ago but it seems that the Debian
I believe there is a PPC build failure that is blocking it. Do the
failures in the build log look like anything obvious to you?
It's obviously the bug fixed here:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=f79982ba930364f2d3935196dc13b422ba711ef2
I guess we get to
It seems I found a fix for this.
Thanks, I sent out a patch to ovs-dev:
http://openvswitch.org/pipermail/dev/2012-June/018075.html
With luck, it will be committed to the OVS repository today and then go
into Debian in a day or two.
Thank you very much!
--
You received this bug notification
This message is very odd, because it implies that configure was not run
correctly, to use /var instead of /usr/local/var:
/usr/local/bin/ovs-pki: /usr/local/var/lib/openvswitch/pki already exists
and --force not specified
That is in fact probably the reason for the problem, because the
I had OVS built from source and was trying to install using apt-get on
top of it. It failed
Oh, I see. You installed OVS programs earlier in your $PATH than the
packaged versions and were surprised that this didn't work well. I
think the answer is don't do that then.
--
You received this bug
Error! Your kernel headers for kernel 3.2.0-2-virtual cannot be found.
Please install the linux-headers-3.2.0-2-virtual package,
or use the --kernelsourcedir option to tell DKMS where it's located
I'm pretty sure that it's not anything from Open vSwitch printing this
message, so I'm not sure
- sfl_agent_*error uses a fixed length buffer. is it ensured that it
won't overflow?
I only see calls to that function with short, fixed strings. The buffer
is 1000 bytes. I don't see how it could overflow.
However, it can't hurt to switch to snprintf(), so I posted a patch to
ovs-dev:
However, it can't hurt to switch to snprintf(), so I posted a patch to
ovs-dev: http://openvswitch.org/pipermail/dev/2012-January/014601.html
Patch was reviewed. I've pushed it to master and all active 1.x
branches.
--
You received this bug notification because you are a member of Ubuntu
I don't want brcompat to control the bridge module. I want brcompat to
make it possible to REPLACE the bridge kernel module with an OvS switch.
OK. That's the purpose of brcompat. Thank you for the report.
I'll see what I can do about fixing this upstream.
--
You received this bug
I posted a fix to ovs-dev for review:
http://openvswitch.org/pipermail/dev/2012-January/014352.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/917309
Title:
brcompatd works
I pushed the fix to master and the branches for 1.2, 1.3, 1.4, and 1.5.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/917309
Title:
brcompatd works with brctl delif but
When I start the openvswitch initscript it doesn't remove the bridge module,
but loads the brcompat module.
brcompatd should not be enabled by default. Does this mean that you
specifically enabled ovs-brcompatd, by installing the openvswitch-brcompat
package and editing
Examining the openvswitch opening script I find that it only tries to remove
the module if there are no bridges up.
...to prevent the script from destroying all of your bridges, if you have some
configured.
But what good is brcompatd if there are no bridges up?
I think you misunderstand the
I don't understand what problem this bug reports. Can you please
rephrase it?
Thanks,
Ben (upstream maintainer).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/914160
Title:
The DKMS support that I just committed to the upstream Git master for
Open vSwitch has this bug fixed (s/linux-2.6/linux/ as suggested in
comment #3).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
I sent the following bugfix patch to ovs-dev for review:
http://openvswitch.org/pipermail/dev/2011-August/010334.html
Anyone who is running into the problem can for now just mkdir
/var/run/openvswitch.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
I pushed the fix to the Open vSwitch Git master, so the next Debian
upload should fix this bug, once it propagates to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/808224
I posted a patch here:
http://openvswitch.org/pipermail/dev/2011-July/009879.html
I've only partially tested it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/808224
Title:
@Ben: Can you comment on why it's use is discouraged?
A few reasons:
* Its original goal was to support XAPI on Citrix XenServer, in versions of
XenServer before OVS was integrated. We implemented exactly the feature set
required for that. There could easily be important omissions.
* Unlike
Speaking as the Debian and upstream maintainer for Open vSwitch, ovs-
brcompatd isn't in the upstream Debian version of the package because we
don't want to encourage people to use it.
It might make sense to add another binary package for ovs-brcompatd, if
you really need it.
The DKMS package is
I don't see value in having two kernel module packages.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/808224
Title:
ovs-brcompatd not built
To manage notifications about this
30 matches
Mail list logo
