Hi,
I'm coming by cleaning old open bugs to ensure nothing gets forgotten for too
long and or clutters the view to the remaining issues.
This case here - as Paride outlined almost two years ago - is already
covered and discussed in bug 1833586 . We won't/can't SRU it and there
was no further inpu
Xenial has reached end of standard support.
** Changed in: open-iscsi (Ubuntu Xenial)
Status: Triaged => Won't Fix
** Changed in: linux (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
I think this is basically a duplicate of LP: #1833586. SRUing the fix
was discussed there but vorlon was not positive about it, see comment #6
there.
I'm marking the open-iscsi task as Triaged, but if stick with Steve's
opinion then this is to be considered a Won't Fix.
** Also affects: open-iscs
Based on the update above, #17, I am adding the open-iscsi package task.
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
This is a bug in the open-iscsi package in xenial and bionic. That
package installs this file: /lib/modules-load.d/open-iscsi.conf
Which contains the following:
iscsi_tcp
ib_iser
This causes systemd to always try and load the iscsi_tcp and ib_iser
modules on boot. In eoan, the open-iscsi package
Thanks for the review, it turns out that this failure has always been
present.
Going back to the Bionic 20180705 and Xenial 20180705, which were the
first releases of minimal, also showed that the system "Failed to find
module 'ib_iser'".
Is this something that could be fixed in order to prevent
We have determined nothing has changed in those kernels from last cycle
or this cycle. We think something changed in the CPC environment that
might have triggered what we think might be an old bug. But we need to
CPC help to identify the "last good kernel" and the "first bad kernel".
Once we can
This may not be a new problem. Running the test case against a bionic
image from June shows similar behavior:
$ multipass launch
'https://cloud-images.ubuntu.com/minimal/releases/bionic/release-20200610/ubuntu-18.04-minimal-cloudimg-amd64.img'
Launched: main-gnu
(Ignore comment #12, that was for the master kernel not -kvm)
To clarify: linux-modules-4.15.0-1069-kvm_4.15.0-1069.70_amd64.deb does
*not* contain the ib_iser.ko module.
I don't think it was actually removed from that kernel recently though.
Nothing has changed in that area as far as I know
--
>From linux-modules-4.15.0-112-generic_4.15.0-112.113_amd64.deb :
drwxr-xr-x root/root 0 2020-07-09 19:13
./lib/modules/4.15.0-112-generic/kernel/drivers/infiniband/ulp/
drwxr-xr-x root/root 0 2020-07-09 19:13
./lib/modules/4.15.0-112-generic/kernel/drivers/infiniband/ulp/iser/
-
This might be the same problem as reported and fix in this earlier but:
https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1566468
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888
Could someone check the disposition of ib_iser.ko in either linux-
modules or linux-modules-extra.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888000
Title:
Bionic/Xenial minimal clo
Apport info was collected and attached... moving to confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888000
13 matches
Mail list logo
