[Group.of.nepali.translators] [Bug 2055913] Re: xenial/linux-azure: 4.15.0-1175.190~16.04.1 -proposed tracker

2024-03-13 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  built:
from: feb7ac6444827739
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
bugs-spammed: true
proposed-announcement-sent: true
proposed-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11482
  kernel-stable-master-bug: 2055915
  packages:
generate: linux-generate-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Wednesday, 13. March 2024 10:02 UTC
+ phase: Signoff
+ phase-changed: Thursday, 14. March 2024 00:06 UTC
  reason:
-   regression-testing: Stalled -s testing FAILED
+   promote-to-updates: 'Holding -- waiting for signoffs:
+ stakeholder-signoff'
stakeholder-signoff: Stalled -s waiting for signoff
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1175.190~16.04.1
meta: 4.15.0.1175.159
signed: 4.15.0-1175.190~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-03-11 15:17:50.647410
clamps:
  new-review: feb7ac6444827739
  promote-to-proposed: feb7ac6444827739
  self: 4.15.0-1175.190~16.04.1
  sru-review: feb7ac6444827739
tracker:
  last-message: '2024-03-11 19:45:06.341516+00:00'

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055913

Title:
  xenial/linux-azure: 4.15.0-1175.190~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Fix Released
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  built:
from: feb7ac6444827739
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
bugs-spammed: true
proposed-announcement-sent: true
proposed-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11482
  kernel-stable-master-bug: 2055915
  packages:
generate: linux-generate-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Signoff
  phase-changed: Thursday, 14. March 2024 00:06 UTC
  reason:
promote-to-updates: 'Holding -- waiting for signoffs:
  stakeholder-signoff'
stakeholder-signoff: Stalled -s waiting for signoff
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1175.190~16.04.1
meta: 4.15.0.1175.159
signed: 4.15.0-1175.190~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-03-11 15:17:50.647410
clamps:
  new-review: feb7ac6444827739
  promote-to-proposed: feb7ac6444827739
  self: 4.15.0-1175.190~16.04.1
  sru-review: feb7ac6444827739
tracker:
  last-message: '2024-03-11 19:45:06.341516+00:00'

To manage notifications about this bug go to:

[Group.of.nepali.translators] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2024-03-13 Thread Athos Ribeiro
As discussed in
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074 and
pointed out in
https://bugs.launchpad.net/ubuntu/bionic/+source/keepalived/+bug/1815101/comments/65,
as KeepConfiguration= is part of systemd nowadays, and since the
keepalived fix is available since 2.x, This should be fixed nowadays,
and I am marking the keepalived task as such.

** Tags removed: server-todo

** Changed in: keepalived (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: keepalived (Ubuntu)
 Assignee: Athos Ribeiro (athos-ribeiro) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Triaged
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in keepalived source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # 

[Group.of.nepali.translators] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2024-03-13 Thread Athos Ribeiro
Closing bionic as per
https://bugs.launchpad.net/netplan/+bug/1815101/comments/59 (it is also
on EOSS).

** Changed in: keepalived (Ubuntu Bionic)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Triaged
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in keepalived source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable 

[Group.of.nepali.translators] [Bug 2055904] Re: xenial/linux-kvm: 4.4.0-1130.140 -proposed tracker

2024-03-13 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  auto-prepare:
cycle: s2024.01.08
previous-cycle: s2024.01.08
  built:
from: 1868ebbaa63711ce
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta]
  flag:
boot-testing-requested: true
bugs-spammed: true
proposed-announcement-sent: true
proposed-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11472
  kernel-stable-master-bug: 2055907
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Testing
- phase-changed: Tuesday, 12. March 2024 08:11 UTC
+ phase: Holding before Promote to Updates
+ phase-changed: Wednesday, 13. March 2024 12:11 UTC
  reason:
-   regression-testing: Stalled -s testing FAILED
+   promote-to-updates: Holding -- cycle not ready to release
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.4.0-1130.140
meta: 4.4.0.1130.127
  ~~:
announce:
  swm-transition-crankable: 2024-03-08 09:15:44.556432
clamps:
  new-review: 1868ebbaa63711ce
  promote-to-proposed: 1868ebbaa63711ce
  self: 4.4.0-1130.140
  sru-review: 1868ebbaa63711ce
tracker:
  last-message: '2024-03-08 13:15:07.103766+00:00'

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055904

Title:
  xenial/linux-kvm: 4.4.0-1130.140 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Fix Released
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  auto-prepare:
cycle: s2024.01.08
previous-cycle: s2024.01.08
  built:
from: 1868ebbaa63711ce
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta]
  flag:
boot-testing-requested: true
bugs-spammed: true
proposed-announcement-sent: true
proposed-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11472
  kernel-stable-master-bug: 2055907
  packages:
main: linux-kvm
meta: linux-meta-kvm
  phase: Holding before Promote to Updates
  phase-changed: Wednesday, 13. March 2024 12:11 UTC
  reason:
promote-to-updates: Holding -- cycle not ready to release
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.4.0-1130.140
meta: 4.4.0.1130.127
  ~~:
announce:
  swm-transition-crankable: 2024-03-08 09:15:44.556432
clamps:
  new-review: 1868ebbaa63711ce
  promote-to-proposed: 1868ebbaa63711ce
  self: 4.4.0-1130.140
  sru-review: 1868ebbaa63711ce
tracker:
  last-message: '2024-03-08 13:15:07.103766+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2055904/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 2055913] Re: xenial/linux-azure: 4.15.0-1175.190~16.04.1 -proposed tracker

2024-03-13 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/regression-testing
   Status: Fix Released => Incomplete

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  built:
from: feb7ac6444827739
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
bugs-spammed: true
proposed-announcement-sent: true
proposed-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11482
  kernel-stable-master-bug: 2055915
  packages:
generate: linux-generate-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Signoff
- phase-changed: Wednesday, 13. March 2024 00:31 UTC
+ phase: Testing
+ phase-changed: Wednesday, 13. March 2024 10:02 UTC
  reason:
-   promote-to-updates: 'Holding -- waiting for signoffs:
- stakeholder-signoff'
+   regression-testing: Stalled -s testing FAILED
stakeholder-signoff: Stalled -s waiting for signoff
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1175.190~16.04.1
meta: 4.15.0.1175.159
signed: 4.15.0-1175.190~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-03-11 15:17:50.647410
clamps:
  new-review: feb7ac6444827739
  promote-to-proposed: feb7ac6444827739
  self: 4.15.0-1175.190~16.04.1
  sru-review: feb7ac6444827739
tracker:
  last-message: '2024-03-11 19:45:06.341516+00:00'

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2055913

Title:
  xenial/linux-azure: 4.15.0-1175.190~16.04.1 -proposed tracker

Status in canonical-signing-jobs task00 series:
  Fix Released
Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow abi-testing series:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow boot-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow new-review series:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-generate series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Invalid
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow sru-review series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  built:
from: feb7ac6444827739
route-entry: 2
  comments:
abi-testing: 1
  delta:
promote-to-proposed: [main, meta, signed, generate]
  flag:
boot-testing-requested: true
bugs-spammed: true
proposed-announcement-sent: true
proposed-testing-requested: true
stream-from-cycle: true
  issue: KSRU-11482
  kernel-stable-master-bug: 2055915
  packages:
generate: linux-generate-azure
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Wednesday, 13. March 2024 10:02 UTC
  reason:
regression-testing: Stalled -s testing FAILED
stakeholder-signoff: Stalled -s waiting for signoff
  synthetic:
:promote-to-as-proposed: Invalid
  variant: debs
  versions:
main: 4.15.0-1175.190~16.04.1
meta: 4.15.0.1175.159
signed: 4.15.0-1175.190~16.04.1
  ~~:
announce:
  swm-transition-crankable: 2024-03-11 15:17:50.647410
clamps:
  new-review: feb7ac6444827739
  promote-to-proposed: feb7ac6444827739
  self: 4.15.0-1175.190~16.04.1
  sru-review: feb7ac6444827739
tracker:
  last-message: '2024-03-11 19:45:06.341516+00:00'

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2055913/+subscriptions



[Group.of.nepali.translators] [Bug 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

2024-03-13 Thread David Fernandez Gonzalez
Fixed released for Xenial ESM: 1.0.2g-1ubuntu4.20+esm12

https://ubuntu.com/security/notices/USN-6663-2

** Changed in: openssl (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: openssl (Ubuntu Trusty)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2054090

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  Won't Fix
Status in openssl source package in Xenial:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Focal:
  Fix Released
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Mantic:
  Fix Released
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

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


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp


[Group.of.nepali.translators] [Bug 2044657] Re: Multiple data corruption issues in zfs

2024-03-13 Thread Launchpad Bug Tracker
This bug was fixed in the package zfs-linux - 2.1.5-1ubuntu6~22.04.3

---
zfs-linux (2.1.5-1ubuntu6~22.04.3) jammy; urgency=medium

  * d/p/77b0c6f0403b2b7d145bf6c244b6acbc757ccdc9.patch Cherry-pick
"dnode_is_dirty: check dnode and its data for dirtiness" fix from
zfs-2.1.14. LP: #2044657

 -- Dimitri John Ledkov   Wed, 31 Jan 2024
14:32:34 +

** Changed in: zfs-linux (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

** Changed in: zfs-linux (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2044657

Title:
  Multiple data corruption issues in zfs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Confirmed
Status in zfs-linux source package in Bionic:
  Confirmed
Status in zfs-linux source package in Focal:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Released
Status in zfs-linux source package in Lunar:
  Won't Fix
Status in zfs-linux source package in Mantic:
  Fix Released
Status in zfs-linux source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

   * Multiple data corruption issues have been identified and fixed in
  ZFS. Some of them, at varying real-life reproducibility frequency have
  been deterimed to affect very old zfs releases. Recommendation is to
  upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
  ensure users get other potentially related fixes and runtime tunables
  to possibly mitigate other bugs that are related and are being fixed
  upstream for future releases.

   * For jammy the 2.1.14 upgrade will bring HWE kernel support and also
  compatiblity/support for hardened kernel builds that mitigate SLS
  (straight-line-speculation).

   * In the absence of the upgrade a cherry-pick will address this
  particular popular issue alone - without addressing other issues
  w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
  improvements that were discovered and fixed around the same time as
  this popular issue.

  [ Test Plan ]

   * !!! Danger !!! use reproducer from
  https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
  and confirm if that issue is resolved or not. Do not run on production
  ZFS pools / systems.

   * autopkgtest pass (from https://ubuntu-archive-
  team.ubuntu.com/proposed-migration/ )

   * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )

   * kernel regression zfs testsuite pass (from Kernel team RT test
  results summary, private)

   * zsys integration test pass (upgrade of zsys installed systems for
  all releases)

   * zsys install test pass (for daily images of LTS releases only that
  have such installer support, as per iso tracker test case)

   * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
  2.1.14, and test LXD on these updated kernels)

  [ Where problems could occur ]

   * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
  introduce slight slow down on amd64 (for hw accelerated assembly code-
  paths only in the encryption primitives)

   * Uncertain of the perfomance impact of the extra checks in dnat
  patch fix itself. Possibly affecting speed of operation, at the
  benefit of correctness.

   * The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
 only makes it stronger and not weaker, thus if it were incorrect, likely
 only performance would be impacted (and it is unlikely to be incorrect
 given upstream reviews and attention to data corruption issues; also,
 there are no additional changes to that function upstream)

  [ Other Info ]

   * https://github.com/openzfs/zfs/pull/15571 is most current
  consideration of affairs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions


___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp