** Tags removed: verification-needed-bionic verification-needed-groovy
** Tags added: verification-done-bionic verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898601
Title:
Also on Groovy, trying to install the -server package fails:
$ ubuntu-drivers --gpgpu list
This is gpgpu mode
ERROR:root:could not open aplay -l
Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect
aplay = subprocess.Popen(
File
Groovy:
$ ubuntu-drivers --gpgpu list
This is gpgpu mode
ERROR:root:could not open aplay -l
Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect
aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line 854, in
Tested Bionic, and the spirit of this bug is resolved, I think?
However, it couldn't be completely verified since ubuntu-drivers doesn't
install the -server package when --gpgpu is being called:
This is gpgpu mode
Reading package lists...
Building dependency tree...
Reading state information...
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898601
Title:
'ubuntu-drivers --gpgpu install' installs a lot of
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934428
Title:
Request to pull-in new PERC11 PCI-id from upstream
To manage notifications
I'm pretty sure you meant "Public" not "Public Security" so I've changed
it.
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933790
Title:
@chihchun, any update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon: device descriptor is not closed
To manage notifications about this bug go to:
Hirsute likely won't get an update as it's an interim release. Do you
know if 4.2 will be released and built in Debian before the Feature
Freeze for Impish on August 19, 2021
** Changed in: mdadm (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
ubuntu@doubletusk:~$ sudo ubuntu-drivers list
ERROR:root:could not open aplay -l
Traceback (most recent call last):
File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect
aplay = subprocess.Popen(
File "/usr/lib/python3.8/subprocess.py", line
Marking Invalid for now.
After email discussion, I believe that the 20.04 ISO is older and
unsupported now, while the 20.04.2 ISO does work and thus the issue is
resolved there.
Users should always be using the latest ISO image from ubuntu.com, and
then can choose either the GA (5.4) or HWE
Hi. I don't think this is a grub-installer issue so I've moved it over
to Subiqutiy, as it looks like that is what you're trying to do here.
So to confirm for BOTH 20.04 and 20.04.2, you are using the new
Subiquity installer (The Ubuntu Server Live ISO available from
ubuntu.com)?
Does the
Can this be recreated without sosreport?
e.g. can the call traces be created simply by running something like
sudo ethtool /dev/DEVICE
Also, which 100Gb NIC is this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: lxc (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933359
Title:
[Ubuntu 21.10][Broadcom] mpi3mr driver submission request
To manage notifications
dpuble post
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898601
Title:
'ubuntu-drivers --gpgpu install' installs a lot of unnecessary
packages, including a full desktop environment on Ubuntu
When can this be finally pulled back at least as far as Focal? We are
not going to be doing nVidia testing on Bionic, so that task can be
dropped I think, unless it's worthwhile, but for Focal - Hirsute, this
would be very helpful to cut down on the amount of stuff being
installed, as well as
Public bug reported:
Forgot to use sudo and discovered an ugly traceback.
ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu install
This is gpgpu mode
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 480, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py",
** Description changed:
[Impact]
Improves support in SmartPQI for most recent controllers
[Fixes]
All are in mainline currently and cleanly cherry pick into Hirsute.
c64aab41c5e1 scsi: smartpqi: Remove unused functions
5cad5a507241 scsi: smartpqi: Fix device pointer variable
tarball of patches that cover these commits provided by microchip
** Attachment added: "ubuntu_21.04.tar"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+attachment/5506766/+files/ubuntu_21.04.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs,
MODULE_SUPPORTED_DEVICE
[Testing]
TBD
[Regression Risk]
Low. Patch set only adds tested bug fixes and support for additional
controllers that are shipping with current refreshes for various OEMs
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
Mariusz,
> The following patches should fix the issue (not verified yet):
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
> https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81
Were those patches verified to fix
** Changed in: debian-installer (Ubuntu Cosmic)
Status: New => Won't Fix
** Changed in: debian-installer (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: debian-installer (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a
Should be resolved with work in progress for Subiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage
Set back to Incomplete. I presume Pawel should comment on this so we
can sort out what the actuall issue is.
** Changed in: subiquity
Status: Expired => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
PR made for 5.11
** Summary changed:
- Ubuntu 21.04, kernel feature request, TLS device offload for Bond
+ [FEATURE] Hirsute: support TLS device offload for Bond
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
The request here is to pull needed patches to support tls rx/tx offload
for bond interfaces.
patch set:
4e5a73329051 net/tls: Except bond interface from some TLS checks
153cbd137f0a net/tls: Device offload to use lowest netdevice in chain
dc5809f9e2b6
** Description changed:
It would be very helpful for automation to have a metapackage that
always installs the latest linux-modules-nvidia-$VER-server and nvidia-
kernel-common-$VER-server packages.
For example, something like linux-modules-nvidia-server-generic could
point to the
** Description changed:
+ +++Update+++
+ I am in a position where I need to run regression testing using the nVidia
drivers on systems configured for GPU compute. This bug prevents me from using
ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers.
+
+ To resolve this,
*** This bug is a duplicate of bug 1898601 ***
https://bugs.launchpad.net/bugs/1898601
** This bug has been marked a duplicate of bug 1898601
'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages,
including a full desktop environment on Ubuntu Server
--
You received
Public bug reported:
It would be very helpful for automation to have a metapackage that
always installs the latest linux-modules-nvidia-$VER-server and nvidia-
kernel-common-$VER-server packages.
For example, something like linux-modules-nvidia-server-generic could
point to the 460 versions of
Public bug reported:
one cannot install drivers unless one is root (or has root priv
escalation via sudo).
For that reason, ubuntu-drivers should not run without a priv check.
ubuntu@doubletusk:~$ ubuntu-drivers --gpgpu autoinstall
This is gpgpu mode
E: Could not open lock file
Public bug reported:
when I use --gpgpu mode to install gpgpu drivers using ubuntu-drivers, I
want ONLY apropriate drivers for GPU compute functions. I do NOT need,
nor want, desktop packages that I have no need for to be installed.
Start-Date: 2021-03-19 15:43:24
Commandline: apt-get install
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915717
Title:
Ubuntu 21.04, kernel feature request, TLS device offload for Bond
To manage notifications about this bug
Test kernels available here:
https://kernel.ubuntu.com/~kmously/kernel-kmously-d2f84a2-M5Ea/
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Assignee: Jeff Lane (bladernr)
Sta
These two do not cleanly pick to either Hirsute (currently at 5.10) or
unstable (currently 5.11). The conflicts are small, but not clean in
any case
dc5809f9e2b6 net/bonding: Declare TLS RX device offload support
89df6a810470 net/bonding: Implement TLS TX device offload
--
You received this
On second thought, nevermind, I was able to do it. There does not
appear to be any identifying information in this summary so I've been
able to mark this public and moved it to the appropriate project.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi.
I think you've filed this bug in the wrong place. Please file a public
kernel bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+filebug
Thank you,
Jeff
** Information type changed from Proprietary to Public
** Project changed: dell-poweredge => linux (Ubuntu)
--
You received
log files unnecessary, this is a patch pull request.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915717
Title:
Ubuntu 21.04,
Not necessarily. Build 3709, which is in Focal, is too old to have
Barlow Pass support¸the earliest build is 3764, as I understand it, so
only builds later than that will have the needed support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Sorry, that was an overzealous CopyPasta. I meant just for 20.10 for
some of these (which are obviously not Subiquity parts).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon:
Tagged Ubuntu SRU team, hoping to push this through soonish, targeting
02.00.00.3774+ds-1
@Adam, as you said 3764 or later is good, I am presuming 2.00.00.3774
should be fine for Barlow Pass then, can you confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
[IMPACT]
The ipmctl package in Focal needs to be updated to a newer version to support
Barlow Pass DCPMM
(new hardware enablement).
In Focal, the package supports only Apache Pass (ie, the first
generation of the hardware) -- but by now, Barlow Pass has been
** Description changed:
Hi,
[Impact]
Currently in focal, devices reporter recovery is enabled even if state is
healthy.
+
+ [fix]
+ 402818205c9e devlink: don't do reporter recovery if the state is healthy
+ this upstream commit from kernel v5.5-rc1 which is cleanly applied on focal
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915403
Title:
devlink: don't do reporter recovery if the state is healthy
Can we please target this for 21.10? This is being requested by several
hardware partners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid
Can this please be targeted for 21.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
To manage notifications about this bug go to:
Can we please target this for 21.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/112
Title:
mdmonitor doesn't start recovery immediately
To manage notifications about this bug go to:
I think the ultimate issue is that users cannot install to VROC volumes
using Subiquity, and not finding a deb for mdadm may be a bit of a red
herring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can this please be targeted for 21.10 in subiquity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868708
Title:
mdmon: device descriptor is not closed
To manage notifications about this bug go
** Tags added: blocks-hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915413
Title:
Milan Delta A100 GPU fails to detect on Ubuntu 18.04 and 20.04
To manage notifications about this
Test kernels are available here: https://kernel.ubuntu.com/~kmously
/kernel-kmously-92dc8ac-EqeO/
Please test and let us know if these meet your needs.
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of
some test kernels soon.
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Focal)
Im
Patch pull request, Bot stuff not needed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915403
Title:
devlink: don't do
** Also affects: lvm2 (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
To
** Also affects: mdadm
Importance: Undecided
Status: New
** Also affects: subiquity
Importance: Undecided
Status: New
** Changed in: subiquity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Still a problem in 20.04. Now its been 5 LTS releases and time is still
broken.
** Changed in: time (Ubuntu)
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660655
fix:
commit 195fb97766da1b41b4d49bccc37e13603bcb49cc
Author: Bruce Allan
Date: Thu Feb 13 13:31:27 2020 -0800
ice: add additional E810 device id
Add support for device id 0x159b.
Signed-off-by: Bruce Allan
Signed-off-by: Tony Nguyen
Tested-by: Andrew Bowers
Note, as this patch is already present from 5.7 onward, the only work
necessary is a pull into 5.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912511
Title:
[SRU] Add support for E810 NIC to
, further
patches are necessary to fully enable support in the Ice driver.
[Other Info]
This was reported by a hardware partner and blocks certification for systems
that use E810 based NICs as their primary network devices.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Jeff
** Changed in: plainbox-provider-checkbox
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896119
Title:
Catting the SecureBoot efivar in /sys hangs
To
For context, the update from the customer was that
cat /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-
00e098032b8c
actually works fine UNTIL he runs the cert suite, after which point it
hangs.
So I wonder if not properly closing the file leaves this in a bad state
somehow once
box
Status: Incomplete => Fix Committed
** Changed in: plainbox-provider-checkbox
Status: Fix Committed => In Progress
** Changed in: plainbox-provider-checkbox
Importance: Undecided => Medium
** Changed in: plainbox-provider-checkbox
Assignee: (unassigned) => Jeff
** Summary changed:
- secure boot test locks machine up
+ Catting the SecureBoot efivar in /sys hangs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896119
Title:
Catting the SecureBoot efivar in
At this point, this is not a problem I can fix. It's very much tied to
their hardware, and to the kernel on that hardware. This is the only
instance of this I have ever seen, anywhere, over literally thousands of
test runs, and it is very easily reproduced manually by simply catting
the efi
Please test this with 20.04 (tboot version 1.9.7-0ubuntu2) to see if the
issue persists in 1.9.7).
I would presume that the 21.04 daily image (tboot version
1.9.12+hg20200718-1) will work correctly as it uses the same version you
tried from sourceforge, but it would be nice if you could also test
Additionally¸ it could help if you could reformat the summarty to match
the SRU template as noted here:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Has there been any movement on this? We get asked about Secure Boot in
MAAS periodically by various hardware partners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from
Quanxian, Pavel, Can these servers with VROC enabled/configured be
installed using MAAS (https://maas.io)?
For server, while we do have an ISO installer in Subiquity, any time we
do a deployment for customers the preferred method of managing and
deploying DC hardware is MAAS. MAAS deployments
After discussion with the kernel team, we will not back port these to
5.4 at this time. There are varying degrees of backporting necessary to
get each patch from 5.8 into 5.4 and unfortunately there's no way to
schedule the work currently.
We can revisit this should there be customer demand, but
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox
None of these cleanly pick into Focal. Deferring to Kernel team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox Connect-IB
Double Checked and ALL these are in 5.8 already.
These are via this bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902130:
410bd754cd73
1d5558b1f0de
50b2412b7e78
432161ea26d6
and the other one appears directly in the kernel, so I guess that means
it was part of a sync from 5.8/5.9?
Marking Linux task invalid as this is not necessary for Hirsute or
Groovy.
Will work the Focal task now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four needed fixes
Public bug reported:
I noticed this in syslog while investigating an unrelated issue today.
I have Focal installed on a Fujitsu RX2530 M5 server with two Xeon Gold
6240 18c/36t CPUs installed. Every reboot results in the following MSR
stack trace:
Dec 3 17:34:31 nabbit kernel: [0.002463]
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) =
Tag/Log Check - looks like the first patch is already in 5.8
d43b7007dbd1 -- Ubuntu-5.8.0-10.11 -- Wed Mar 18 21:44:32 2020 +0200
410bd754cd73 -- v5.10-rc1 -- Mon Aug 31 15:04:35 2020 +0300
1d5558b1f0de -- v5.10-rc1 -- Tue Jul 21 10:25:52 2020 +0300
50b2412b7e78 -- v5.10-rc1 -- Tue Aug 4 10:40:21
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ub
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905574
Title:
Ubuntu 20.10 four needed fixes to 'Add driver for Mellanox
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900668
Title:
MAAS PXE Boot stalls with grub 2.02
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904848
Title:
Ubuntu 18.04- call trace in kernel buffer when unloading ib_ipoib
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Opinion
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Importance: Undecided
Status: New
--
You received this bug notification
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893661
Title:
Support for Intel VROC (Virtual RAID On CPU)
To manage notifications about this bug go to:
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this
Checking affected versions, this only applies to Focal:
ipmctl | 02.00.00.3709+ds-1 | focal/universe | source, amd64
ipmctl | 02.00.00.3774+ds-1 | groovy/universe | source, amd64
ipmctl | 02.00.00.3825+ds-1 | hirsute/universe | source, amd64
Groovy and Hirsute both have later versions that
** Description changed:
[IMPACT]
The ipmctl package in Focal needs to be updated to a newer version to support
Barlow Pass DCPMM
(new hardware enablement).
In Focal, the package supports only Apache Pass (ie, the first
generation of the hardware) -- but by now, Barlow Pass has been
** Tags added: blocks-hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903204
Title:
[SRU] ipmctl in Focal does not work with Barlow Pass DCPMM hardware
To manage notifications about
** Description changed:
+ [IMPACT]
The ipmctl package in Focal needs to be updated to a newer version to support
Barlow Pass DCPMM
(new hardware enablement).
In Focal, the package supports only Apache Pass (ie, the first
generation of the hardware) -- but by now, Barlow Pass has been
** Summary changed:
- [SRU] update ipmctl in Focal
+ [SRU] ipmctl in Focal does not work with Barlow Pass DCPMM hardware
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903204
Title:
[SRU] ipmctl
** Changed in: lvm2 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887372
Title:
Cannot create lvm upon IMSM raid array
To manage notifications about
Patch exists upstream in 5.9. So Hirsute should be good, will need backport for
Groovy and Focal.
** Project changed: kernel-sru-workflow => linux (Ubuntu)
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Groovy)
Sreekanth, what's the target upstream kernel version for this feature?
Just want to get a feel for the timing. As you've already submitted
these upstream, getting them into 21.04 should be no problem at all.
Also, do you expect (or desire) us to pull these back into 5.4 at some
point, or are you
Thanks Lee... I think there are two different issues that need to be
resolved.
First, is that we recently introduced patches to the 5.4 kernel for
Intel x710 NICs because 5.4 only saw some of the NIC ports. So to solve
that problem, we would need new maas images spun that include the latest
5.4
Jonas, Billy, Alec: Can you provide me the output of the following:
$ ls -l /var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily
$ sha256sum
/var/lib/maas/boot-resources/current/ubuntu/amd64/ga-20.04/focal/daily/*
I suspect I know what the answers will be, but I want to verify
Thanks, yes, MAAS will sync using a nightly cron job, I just wasn't
quite sure how often that happens so I had to ask.
** Summary changed:
- [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
+ [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after
images
Note for investigation: Is it possible that the kenrel and initrd boot
media are not updated and thus you're seeing the Carlsville NIC problem
with old initrd? This could mean we need to rebuild initrd and push that
to the stream?
--
You received this bug notification because you are a member of
Marked all tasks invalid. It's been over 2 years and no further update
from the tester who reported this initially. One can only presume it's
been resolved by some update to the kernel, or was not kernel related
and resolved itself by other means. If this appears again, we'll open a
fresh bug.
** Tags removed: blocks-hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
To manage notifications
Alec, Billy: are these the same MAAS environments you've previously used
to deploy 20.04 for other work, or have you rebuilt the MAAS
environments recently?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: blocks-hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898808
Title:
[maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut
To manage notifications about
201 - 300 of 3415 matches
Mail list logo
