Alex: Hardy at the stage you were using it was in development, and there
were tonns of warnings posted all over the place saying Don't use this
on production machines. You were using hardy during its testing stage,
and the fix was released before Hardy :)
--
[hardy] ip broken
** Changed in: iproute (Debian)
Status: Unknown = Fix Released
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hardy is a great work its ok for beginners but if you want something just not
in the mainstream such as xen perhaps,
then ANYTHING like this ubuntu will fail.
It has been my misfortune since brezzy badger that I usae ubuntu its ok
for the run of the mill stuff but thats IT
For a ROCK solid
This bug was fixed in the package iproute - 20071016-2ubuntu1
---
iproute (20071016-2ubuntu1) hardy; urgency=low
* Cherry-picked merge from Debian unstable, remaining changes:
- debian/patches/tc_qdisc_segv.patch: Fix an off-by-one error that
causes segfaults in tc on
The info for iproute lists ubuntu-core-dev as the maintainers. Please
reassign if I'm making a mistake.
** Changed in: iproute (Ubuntu)
Assignee: (unassigned) = Ubuntu Core Development Team (ubuntu-core-dev)
** Also affects: vzctl (Ubuntu)
Importance: Undecided
Status: New
--
I'm sorry to say but this is actually 1/2 user error and 1/2 xen
logistics. Xen while creating the briding for DomU's, renames eth0 to
peth0. You can verify this by running chmod -x /etc/init.d/xend ;
reboot and verifying that iproute works as you expect it to.
Please see
Paul, ubuntu-core-dev is the set of people responsible for the 'main'
section of the Ubuntu archive, so it's not particularly meaningful to
assign a bug to that group. :) It does get eyeballs on it, though;
let's see what we come up with.
James, I'm pretty sure that this is /not/ user error wrt
... gah, wrong button.
However, this bug is *not* reproducible for me with the standard hardy
kernel on amd64. So far, it looks like everyone who's reporting this
bug is running a non-Ubuntu kernel - can anyone reproduce this problem
with an Ubuntu kernel?
This may come down to configuration
Mmm,
It is true I am running a non-Ununtu kernel ...
Perhaps because the Ubuntu Xen kernel, certainly upto Gutsy, was simply
too unstable to be of any use. I'm running ~ 20 Xen instances across 4
servers and spent a LONG TIME trying to make raw Ubuntu work. My
eventual solution was to switch to
Ok, I've gone back to a dapper kernel and have been able to confirm that
the iproute in hardy is not compatible with a dapper kernel, whereas it
is compatible with a gutsy (and, obviously, with a hardy) kernel.
So this bug is of interest for an LTS - anyone who upgrades from Ubuntu
6.06 to 8.04
Someone are working on hardy-openvz kernel:
http://git.openvz.org/?p=ubuntu-hardy-openvz;a=summary
Ok, I'll wait for release.
Bye.
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, I have pinned the iproute package in /etc/apt/preferences
Package: iproute
Pin: release a=gutsy
Pin-Priority: 900
Then I have removed iproute and reinstalled all packages removed (also
the old libldap-2.4-2 and iproute 20070313-1ubuntu2)
Now it work...but is a dirty solution!
Thank you!
I don't know if this should be forward to OpenVZ Ubuntu team.
I make a mistake, it don't work:
with old iproute i don't get RTNETLINK error but ARP requests to OpenVZ VE
aren't resolved so VM aren't reachable via network.
Moreover during startup of VE I get:
Starting VE ...
VE is mounted
Does ubuntu have an OpenVZ package or a OpenVZ team?
You should add the package that it affects if so.
Are you able to see a fix for it. Most likely it is fixed upstream
right?
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a
Also I can confirm this bug on hardy with OpenVZ kernel.
[EMAIL PROTECTED]:~# uname -a
Linux hnode02 2.6.18-fza-028stab053.5-amd64 #1 SMP Sat Mar 1 19:50:43 UTC 2008
x86_64 GNU/Linux
Bye.
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because
fdb: did you install the older versions of iproute and libdb to work
around the problem?
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this bug on hardy.
simple steps to reproduce
ip link set eth0 down
RTNETLINK answers: Invalid argument
This is called by the Xen network-bridge script also.
fixed by installing hardy iproute package with --force-depends (since
libdb package is missing from the repos)
This is a
I can't reproduce this in Hardy - however I'm not using xen.
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
libdb is in fact in gutsy main so the force-depends shouldn't be
necessary.
I am doing a fresh install and upgrade to latest gutsy.
I will make sure I can reproduce it in that situation
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you
latest hardy i meant...
iproute at alpha6 does seem to work.
I am still downloading updates and them will need to install the ubuntu-
xen-server package.
I don't see how the xen packages could break the ip command, but I guess
it could be possible
--
[hardy] ip broken
it seems that i can't reproduce this problem on the hardy then kernel.
it is possible it only happens on the Xen kernel from
http://xen.org/download/
It might be a few days before i can test further as we need to do some
benchmarks on Xen and KVM in a working state.
I can't test more later.
I meant to say I *can* test more later.
sorry for the confusion.
any other testers appreciated :)
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi,
Do you get that error message for all usage of ip, or just that particular one?
Also, can you please post the result of uname -a?
Thanks
** Changed in: iproute (Ubuntu)
Status: New = Incomplete
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug
Linux nodea 2.6.21-prep #11 SMP Tue Feb 12 19:15:35 UTC 2008 x86_64
GNU/Linux
This is the stock RH kernel with Xen extensions built from source .. you
know why I'm not using the Ubuntu Kernel (!)
--
[hardy] ip broken
https://bugs.launchpad.net/bugs/192294
You received this bug notification
24 matches
Mail list logo
