https://bugzilla.redhat.com/show_bug.cgi?id=1997250
Bug ID: 1997250
Summary: can't run iscsid in a docker container RHEL8,
originally issue on RHEL7 and closed wontfix (Veritas)
Product: Red Hat Enterprise Linux 8
Version: 8.5
Hardware: x86_64
OS: Linux
Status: NEW
Component: kernel
Sub Component: Kernel-Core Namespace
Keywords: Reopened
Severity: medium
Priority: medium
Assignee: agladkov(a)redhat.com
Reporter: loberman(a)redhat.com
QA Contact: kernel-general-qe(a)redhat.com
CC: abeausol(a)redhat.com, admiller(a)redhat.com,
agladkov(a)redhat.com, amurdaca(a)redhat.com,
atragler(a)redhat.com, berthiaume_wayne(a)emc.com,
borgan(a)redhat.com, bubrown(a)redhat.com,
cleech(a)redhat.com, david.barnhill(a)emc.com,
dornelas(a)redhat.com, dwalsh(a)redhat.com,
ebiederm(a)redhat.com, fsimonce(a)redhat.com,
fsuba(a)redhat.com,
golang-updates(a)lists.fedoraproject.org,
jhunsaker(a)redhat.com, jkeck(a)redhat.com,
jmagrini(a)redhat.com, jsafrane(a)redhat.com,
jslagle(a)redhat.com, kzhang(a)redhat.com,
loberman(a)redhat.com, lsm5(a)redhat.com,
mattdm(a)redhat.com, mleitner(a)redhat.com,
pedro(a)aguatechnologies.com, revers(a)redhat.com,
rvykydal(a)redhat.com, s(a)shk.io,
vaibhav.khanduja(a)emc.com
Depends On: 1100000, 1416129
Blocks: 1186913, 1420851, 1102911, 1422628
Target Milestone: rc
Group: private
Classification: Red Hat
Pool ID: sst_kernel_ft_rhel_8
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1100000
[Bug 1100000] can't run iscsid in a docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1102911
[Bug 1102911] can't run iscsid in a docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1416129
[Bug 1416129] can't run iscsid in a docker container
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096816
petrkuzel(a)eurofins.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |petrkuzel(a)eurofins.com
--- Comment #10 from petrkuzel(a)eurofins.com ---
This bug is used as exemplary for The limits of compatibility and
supportability with containers
<https://www.redhat.com/en/blog/limits-compatibility-and-supportability-cont…>.
I understand that for the same image and the same hosting kernel, the docker
service upgrade impacted behaviour of the container.
Despite the docker service upgrade impacted containers it was not seen as a
regression in the docker service but it was evaluated
as that the upgrade detected a latent bug in the container and preserving a
bug-to-bug backward compatibility was not beneficial was it, please?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096816