[Kernel-packages] [Bug 2051672] Re: Backport iproute2 6.8.0 to noble

2024-04-30 Thread Andrea Righi
Thanks @dannf for updating the bug! The SRU description looks good to me
and everything seems reasonable, same with the plan.

I'll keep monitoring this tracker and we'll proceed once oracular will
be open.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2051672

Title:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.

  Normally iproute2 is updated during the devel cycle to align with the
  kernel version, but it was missed this cycle and discovered too late
  for an FFe. We request an exception from the SRU team to do this as an
  SRU. This includes dropping the Ubuntu Fan patches, which adds
  features to iproute2 that no longer work since noble's kernels no
  longer support Ubuntu Fan.

  [Test Case]
  We'll run the 6.8 kernel self tests, which make use of a number of iproute2 
features (see comment #17). NVIDIA's networking organization (Mellanox) has 
offered to put this through their QA process (details TBD). The upstream test 
suite will also run in the autopkgtests, though that suite is fairly stale.

  [What Could Go Wrong]
  Users who may be running noble userspace with a non-noble kernel that 
supports Ubuntu Fan would lose support for configuring it. If the SRU team 
considers this to be a regression we should avoid, then we can add the Ubuntu 
Fan patches back.

  iproute2 6.8 upstream retains backwards compatibility with earlier
  releases (see comment #17). There are no commits with a Fixes:
  annotation since the v6.8.0 tag was applied upstream.

  iproute2 is obviously a key package, and any upstream version bump
  carries risk. This includes the possibility of breaking networking for
  users of an Ubuntu LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2051672] Re: Backport iproute2 6.8.0 to noble

2024-04-29 Thread dann frazier
Hi Andrea - since this is now a stable release update, I *think* the
next steps should be:

1) Edit this bug to use the SRU Template
  https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
(now done)
Since your team owns this package, please review that and let me know if you 
have any concerns with that text.

2) Wait for 24.10 ('oracular') to open for devel and forcesync iproute2
w/ Debian
(https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First).

3) Upload the SRU, and wait for feedback from the sru team. If approved,
we'll need to run the tests in the [Test Case] section and make sure
there are no regressions from 6.1.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2051672

Title:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.

  Normally iproute2 is updated during the devel cycle to align with the
  kernel version, but it was missed this cycle and discovered too late
  for an FFe. We request an exception from the SRU team to do this as an
  SRU. This includes dropping the Ubuntu Fan patches, which adds
  features to iproute2 that no longer work since noble's kernels no
  longer support Ubuntu Fan.

  [Test Case]
  We'll run the 6.8 kernel self tests, which make use of a number of iproute2 
features (see comment #17). NVIDIA's networking organization (Mellanox) has 
offered to put this through their QA process (details TBD). The upstream test 
suite will also run in the autopkgtests, though that suite is fairly stale.

  [What Could Go Wrong]
  Users who may be running noble userspace with a non-noble kernel that 
supports Ubuntu Fan would lose support for configuring it. If the SRU team 
considers this to be a regression we should avoid, then we can add the Ubuntu 
Fan patches back.

  iproute2 6.8 upstream retains backwards compatibility with earlier
  releases (see comment #17). There are no commits with a Fixes:
  annotation since the v6.8.0 tag was applied upstream.

  iproute2 is obviously a key package, and any upstream version bump
  carries risk. This includes the possibility of breaking networking for
  users of an Ubuntu LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2051672] Re: Backport iproute2 6.8.0 to noble

2024-04-29 Thread dann frazier
** Description changed:

- iproute2 upstream produces releases coinciding with upstream kernel
- releases to support the latest kernel features. Noble's iproute2 is
- still back at v6.1 even though it will use the v6.8 kernel. This means
- we provide no userspace interface for newer features - some of which are
- noted by a networking hardware partner in bug 2060969.
+ [Impact]
+ Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.
  
- Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu
- FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no
- longer needed, and we could now just do a merge. We could also port the
- FAN patches forward if we can identify a need (see the original
- description of this bug to a link to such a port), but I have not done
- any testing with that.
+ Normally iproute2 is updated during the devel cycle to align with the
+ kernel version, but it was missed this cycle and discovered too late for
+ an FFe. We request an exception from the SRU team to do this as an SRU.
+ This includes dropping the Ubuntu Fan patches, which adds features to
+ iproute2 that no longer work since noble's kernels no longer support
+ Ubuntu Fan.
  
- I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
- smoke tested it on an amd64 virtual machine:
+ [Test Case]
+ We'll run the 6.8 kernel self tests, which make use of a number of iproute2 
features (see comment #17). NVIDIA's networking organization (Mellanox) has 
offered to put this through their QA process (details TBD). The upstream test 
suite will also run in the autopkgtests, though that suite is fairly stale.
  
- ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb
- (Reading database ... 83134 files and directories currently installed.)
- Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ...
- Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ...
- dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': 
Directory not empty
- dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': 
Directory not empty
- dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not 
empty
- Setting up iproute2 (6.8.0-1~24.04.1) ...
- Removing obsolete conffile /etc/iproute2/group ...
- Removing obsolete conffile /etc/iproute2/rt_realms ...
- Removing obsolete conffile /etc/iproute2/rt_scopes ...
- Removing obsolete conffile /etc/iproute2/rt_tables ...
- Removing obsolete conffile /etc/iproute2/rt_tables.d/README ...
- Removing obsolete conffile /etc/iproute2/rt_protos.d/README ...
- Removing obsolete conffile /etc/iproute2/rt_protos ...
- Removing obsolete conffile /etc/iproute2/rt_dsfield ...
- Removing obsolete conffile /etc/iproute2/nl_protos ...
- Removing obsolete conffile /etc/iproute2/ematch_map ...
- Removing obsolete conffile /etc/iproute2/bpf_pinning ...
- Processing triggers for man-db (2.12.0-4build1) ...
+ [What Could Go Wrong]
+ Users who may be running noble userspace with a non-noble kernel that 
supports Ubuntu Fan would lose support for configuring it. If the SRU team 
considers this to be a regression we should avoid, then we can add the Ubuntu 
Fan patches back.
  
- The system rebooted fine. The ip command seems to behave normally.
+ iproute2 6.8 upstream retains backwards compatibility with earlier
+ releases (see comment #17). There are no commits with a Fixes:
+ annotation since the v6.8.0 tag was applied upstream.
  
- Since the upstream test suite only appears to run at autopkgtest time, I 
triggered a run in my PPA, and it passed:
-   
https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz
+ iproute2 is obviously a key package, and any upstream version bump
+ carries risk. This includes the possibility of breaking networking for
+ users of an Ubuntu LTS release.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2051672

Title:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Several networking features introduced in the upstream 6.2->6.8 kernels are 
not accessible to noble users because noble lacks the corresponding iproute2 
update. This includes support for new hardware features such as per-VF offload 
settings (see bug 2060969), but many others that you can see in the attached 
changelogs.

  Normally iproute2 is updated during the devel cycle to align with the
  kernel version, but it was missed this cycle and discovered too late
  for an FFe. We request an 

[Kernel-packages] [Bug 2051672] Re: Backport iproute2 6.8.0 to noble

2024-04-29 Thread dann frazier
** Summary changed:

- [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from 
testing/unstable (main)
+ Backport iproute2 6.8.0 to noble

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2051672

Title:
  Backport iproute2 6.8.0 to noble

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  iproute2 upstream produces releases coinciding with upstream kernel
  releases to support the latest kernel features. Noble's iproute2 is
  still back at v6.1 even though it will use the v6.8 kernel. This means
  we provide no userspace interface for newer features - some of which
  are noted by a networking hardware partner in bug 2060969.

  Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu
  FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no
  longer needed, and we could now just do a merge. We could also port
  the FAN patches forward if we can identify a need (see the original
  description of this bug to a link to such a port), but I have not done
  any testing with that.

  I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and
  smoke tested it on an amd64 virtual machine:

  ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb
  (Reading database ... 83134 files and directories currently installed.)
  Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ...
  Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ...
  dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': 
Directory not empty
  dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not 
empty
  Setting up iproute2 (6.8.0-1~24.04.1) ...
  Removing obsolete conffile /etc/iproute2/group ...
  Removing obsolete conffile /etc/iproute2/rt_realms ...
  Removing obsolete conffile /etc/iproute2/rt_scopes ...
  Removing obsolete conffile /etc/iproute2/rt_tables ...
  Removing obsolete conffile /etc/iproute2/rt_tables.d/README ...
  Removing obsolete conffile /etc/iproute2/rt_protos.d/README ...
  Removing obsolete conffile /etc/iproute2/rt_protos ...
  Removing obsolete conffile /etc/iproute2/rt_dsfield ...
  Removing obsolete conffile /etc/iproute2/nl_protos ...
  Removing obsolete conffile /etc/iproute2/ematch_map ...
  Removing obsolete conffile /etc/iproute2/bpf_pinning ...
  Processing triggers for man-db (2.12.0-4build1) ...

  The system rebooted fine. The ip command seems to behave normally.

  Since the upstream test suite only appears to run at autopkgtest time, I 
triggered a run in my PPA, and it passed:

https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp