[Group.of.nepali.translators] [Bug 1878835] Re: xenial/linux-aws-hwe: 4.15.0-1068.72~16.04.1 -proposed tracker

2020-05-26 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => 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 --
  kernel-stable-master-bug: 1878836
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
- phase: Packaging
- phase-changed: Tuesday, 26. May 2020 15:42 UTC
+ phase: Building in ppa
+ phase-changed: Wednesday, 27. May 2020 03:32 UTC
  reason:
-   prepare-package: Pending -- tag not published and package not
- uploaded
-   prepare-package-meta: Pending -- tag not published and package not
- uploaded
+   build-packages-ppa: Ongoing -- building in ppa main:building
  variant: debs
+ versions:
+   main: 4.15.0-1068.72~16.04.1
+   meta: 4.15.0.1068.68

-- 
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/1878835

Title:
  xenial/linux-aws-hwe: 4.15.0-1068.72~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws-hwe 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 --
  kernel-stable-master-bug: 1878836
  packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
  phase: Building in ppa
  phase-changed: Wednesday, 27. May 2020 03:32 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa main:building
  variant: debs
  versions:
main: 4.15.0-1068.72~16.04.1
meta: 4.15.0.1068.68

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1878835/+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 1878840] Re: xenial/linux-azure: 4.15.0-1084.94~16.04.1 -proposed tracker

2020-05-26 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => In Progress

** 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1878842
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Proposed
- phase-changed: Wednesday, 27. May 2020 00:02 UTC
+ phase: Testing
+ phase-changed: Wednesday, 27. May 2020 01:32 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for
- mirror sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   stakeholder-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-azure/azure-kernel: bug 1878839
  variant: debs
  versions:
main: 4.15.0-1084.94~16.04.1
meta: 4.15.0.1084.83
signed: 4.15.0-1084.94~16.04.1

-- 
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/1878840

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1878842
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Testing
  phase-changed: Wednesday, 27. May 2020 01:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-azure/azure-kernel: bug 1878839
  variant: debs
  versions:
main: 4.15.0-1084.94~16.04.1
meta: 4.15.0.1084.83
signed: 4.15.0-1084.94~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1878840/+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 1878864] Re: xenial/linux-cascade: 4.4.0-1019.21 -proposed tracker

2020-05-26 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1878873
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
- phase: Building in Signing
- phase-changed: Tuesday, 26. May 2020 22:51 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 27. May 2020 00:31 UTC
  reason:
-   build-packages-signing: Pending -- building in Signing
- signed:retry-needed
-   promote-to-proposed: Stalled -- packages copying to Signing
+   promote-signing-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1878863
  variant: debs
  versions:
main: 4.4.0-1019.21
meta: 4.4.0.1019.22
signed: 4.4.0-1019.21

-- 
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/1878864

Title:
  xenial/linux-cascade: 4.4.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1878873
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 27. May 2020 00:31 UTC
  reason:
promote-signing-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1878863
  variant: debs
  versions:
main: 4.4.0-1019.21
meta: 4.4.0.1019.22
signed: 4.4.0-1019.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1878864/+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 1878869] Re: xenial/linux-snapdragon: 4.4.0-1138.146 -proposed tracker

2020-05-26 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => In Progress

** 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1878873
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
- phase: Promote to Proposed
- phase-changed: Tuesday, 26. May 2020 22:41 UTC
+ phase: Testing
+ phase-changed: Wednesday, 27. May 2020 00:32 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for
- mirror sync
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1878868
  variant: debs
  versions:
main: 4.4.0-1138.146
meta: 4.4.0.1138.130

-- 
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/1878869

Title:
  xenial/linux-snapdragon: 4.4.0-1138.146 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-snapdragon 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1878873
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Wednesday, 27. May 2020 00:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-snapdragon/dragonboard-kernel: bug 1878868
  variant: debs
  versions:
main: 4.4.0-1138.146
meta: 4.4.0.1138.130

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1878869/+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 1874771] Re: xenial/linux-azure: 4.15.0-1083.93~16.04.1 -proposed tracker

2020-05-26 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-updates
   Status: In Progress => 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1874773
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Promote to Updates
- phase-changed: Tuesday, 26. May 2020 20:33 UTC
+ phase: Holding before Promote to Security
+ phase-changed: Tuesday, 26. May 2020 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- not ready for security (replication
  dwell)
-   promote-to-updates: Ongoing -- packages not yet published
  trackers:
xenial/linux-azure/azure-kernel: bug 1874770
  variant: debs
  versions:
main: 4.15.0-1083.93~16.04.1
meta: 4.15.0.1083.82
signed: 4.15.0-1083.93~16.04.1

-- 
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/1874771

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released

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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1874773
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Security
  phase-changed: Tuesday, 26. May 2020 21:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- not ready for security (replication
  dwell)
  trackers:
xenial/linux-azure/azure-kernel: bug 1874770
  variant: debs
  versions:
main: 4.15.0-1083.93~16.04.1
meta: 4.15.0.1083.82
signed: 4.15.0-1083.93~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1874771/+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 1874771] Re: xenial/linux-azure: 4.15.0-1083.93~16.04.1 -proposed tracker

2020-05-26 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 4.15.0-1083.93~16.04.1

---
linux-azure (4.15.0-1083.93~16.04.1) xenial; urgency=medium

  * xenial/linux-azure: 4.15.0-1083.93~16.04.1 -proposed tracker (LP:
#1874771)

  [ Ubuntu: 4.15.0-1083.93 ]

  * bionic/linux-azure-4.15: 4.15.0-1083.93 -proposed tracker (LP: #1874773)
  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] azure-4.15: Annotate CONFIG_CONTEXT_TRACKING_FORCE=n
  * Assignment of VDEV Somtimes Fails using Intel QAT (LP: #1867220)
- Revert "Revert "PCI: hv: Make sure the bus domain is really unique""
- Revert "PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain
  numbers"
- PCI: hv: Add __aligned(8) to struct retarget_msi_interrupt
- PCI: hv: Detect and fix Hyper-V PCI domain number collision
- PCI: hv: Use bytes 4 and 5 from instance ID as the PCI domain numbers
  * bionic/linux: 4.15.0-100.101 -proposed tracker (LP: #1875878)
  * built-using constraints preventing uploads (LP: #1875601)
- temporarily drop Built-Using data
  * Add debian/rules targets to compile/run kernel selftests (LP: #1874286)
- [Packaging] add support to compile/run selftests
  * getitimer returns it_value=0 erroneously (LP: #1349028)
- [Config] CONTEXT_TRACKING_FORCE policy should be unset
  * QEMU/KVM display is garbled when booting from kernel EFI stub due to missing
bochs-drm module (LP: #1872863)
- [Config] Enable CONFIG_DRM_BOCHS as module for all archs
  * Backport MPLS patches from 5.3 to 4.15 (LP: #1851446)
- net/mlx5e: Report netdevice MPLS features
- net: vlan: Inherit MPLS features from parent device
- net: bonding: Inherit MPLS features from slave devices
- net/mlx5e: Move to HW checksumming advertising
  * LIO hanging in iscsit_free_session and iscsit_stop_session (LP: #1871688)
- scsi: target: remove boilerplate code
- scsi: target: fix hang when multiple threads try to destroy the same iscsi
  session
- scsi: target: iscsi: calling iscsit_stop_session() inside
  iscsit_close_session() has no effect
  * Add hw timestamps to received skbs in peak_canfd (LP: #1874124)
- can: peak_canfd: provide hw timestamps in rx skbs
  * Bionic update: upstream stable patchset 2020-04-23 (LP: #1874502)
- ARM: dts: sun8i-a83t-tbs-a711: HM5065 doesn't like such a high voltage
- bus: sunxi-rsb: Return correct data when mixing 16-bit and 8-bit reads
- net: vxge: fix wrong __VA_ARGS__ usage
- hinic: fix a bug of waitting for IO stopped
- hinic: fix wrong para of wait_for_completion_timeout
- cxgb4/ptp: pass the sign of offset delta in FW CMD
- qlcnic: Fix bad kzalloc null test
- i2c: st: fix missing struct parameter description
- firmware: arm_sdei: fix double-lock on hibernate with shared events
- null_blk: Fix the null_add_dev() error path
- null_blk: Handle null_add_dev() failures properly
- null_blk: fix spurious IO errors after failed past-wp access
- xhci: bail out early if driver can't accress host in resume
- x86: Don't let pgprot_modify() change the page encryption bit
- block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
- irqchip/versatile-fpga: Handle chained IRQs properly
- sched: Avoid scale real weight down to zero
- selftests/x86/ptrace_syscall_32: Fix no-vDSO segfault
- PCI/switchtec: Fix init_completion race condition with poll_wait()
- libata: Remove extra scsi_host_put() in ata_scsi_add_hosts()
- gfs2: Don't demote a glock until its revokes are written
- x86/boot: Use unsigned comparison for addresses
- efi/x86: Ignore the memory attributes table on i386
- genirq/irqdomain: Check pointer in irq_domain_alloc_irqs_hierarchy()
- block: Fix use-after-free issue accessing struct io_cq
- usb: dwc3: core: add support for disabling SS instances in park mode
- irqchip/gic-v4: Provide irq_retrigger to avoid circular locking dependency
- md: check arrays is suspended in mddev_detach before call quiesce 
operations
- locking/lockdep: Avoid recursion in lockdep_count_{for,back}ward_deps()
- block, bfq: fix use-after-free in bfq_idle_slice_timer_body
- btrfs: qgroup: ensure qgroup_rescan_running is only set when the worker is
  at least queued
- btrfs: remove a BUG_ON() from merge_reloc_roots()
- btrfs: track reloc roots based on their commit root bytenr
- uapi: rename ext2_swab() to swab() and share globally in swab.h
- slub: improve bit diffusion for freelist ptr obfuscation
- ASoC: fix regwmask
- ASoC: dapm: connect virtual mux with default value
- ASoC: dpcm: allow start or stop during pause for backend
- ASoC: topology: use name_prefix for new kcontrol
- usb: gadget: f_fs: Fix use after free issue as part of queue failure
- usb: gadget: composite: Inform controller driver of self-powered
- ALSA: usb-audio: Add mixer workaround for TRX40 and co
- 

[Group.of.nepali.translators] [Bug 1877617] Re: Automatic scans cause instability for cloud use cases

2020-05-26 Thread Rafael David Tinoco
Thanks for the testing Ben.

I haven't backported it to Xenial, will flag it as won't fix. Xenial is
too "mature" to change right now, all cloud archives are bionic oriented
(or should be)... will flag it as won't fix so its more clear.

** Also affects: open-iscsi (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: open-iscsi (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: open-iscsi (Ubuntu Groovy)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (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/1877617

Title:
  Automatic scans cause instability for cloud use cases

Status in open-iscsi package in Ubuntu:
  Triaged
Status in open-iscsi source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Bionic:
  Fix Committed
Status in open-iscsi source package in Eoan:
  Fix Committed
Status in open-iscsi source package in Focal:
  Fix Committed
Status in open-iscsi source package in Groovy:
  Triaged

Bug description:
  [Impact]

  When using iSCSI storage underneath cloud applications such as
  OpenStack or Kubernetes, the automatic bus scan on login causes
  problems, because it results in SCSI disks being registered in the
  kernel that will never get cleaned up, and when those disks are
  eventually deleted off the server, I/O errors begin to accumulate,
  eventually slowing down the whole SCSI subsystem, spamming the kernel
  log, and causing timeouts at higher levels such that users are forced
  to reboot the node to get back to a usable state.

  [Test Case]

  

  # To demonstrate this problem, I create a VM running Ubuntu 20.04.0

  # Install both iSCSI initiator and target on this host
  sudo apt-get -y install open-iscsi targetcli-fb

  # Start the services
  sudo systemctl start iscsid.service targetclid.service

  # Create a randomly generated target IQN
  TARGET_IQN=$(iscsi-iname)

  # Get the initator IQN
  INITIATOR_IQN=$(sudo awk -F = '/InitiatorName=/ {print $2}' 
/etc/iscsi/initiatorname.iscsi)

  # Set up an iSCSI target and target portal, and grant access to ourselves
  sudo targetcli /iscsi create $TARGET_IQN
  sudo targetcli /iscsi/$TARGET_IQN/tpg1/acls create $INITIATOR_IQN

  # Create two 1GiB LUNs backed by files, and expose them through the target 
portal
  sudo targetcli /backstores/fileio create lun1 /lun1 1G
  sudo targetcli /iscsi/$TARGET_IQN/tpg1/luns create /backstores/fileio/lun1 1
  sudo targetcli /backstores/fileio create lun2 /lun2 1G
  sudo targetcli /iscsi/$TARGET_IQN/tpg1/luns create /backstores/fileio/lun2 2

  # Truncate the kernel log so we can see messages after this point only
  sudo dmesg -C

  # Register the local iSCSI target with out initiator, and login
  sudo iscsiadm -m node -p 127.0.0.1 -T $TARGET_IQN -o new
  sudo iscsiadm -m node -p 127.0.0.1 -T $TARGET_IQN --login

  # Get the list of disks from the iSCSI session, and stash it in an array
  eval "DISKS=\$(sudo iscsiadm -m session -P3 | awk '/Attached scsi disk/ 
{print \$4}')"

  # Print the list
  echo $DISKS

  # Note that there are two disks found already (the two LUNs we created
  # above) despite the fact that we only just logged in.

  # Now delete a LUN from the target
  sudo targetcli /iscsi/$TARGET_IQN/tpg1/luns delete lun2
  sudo targetcli /backstores/fileio delete lun2

  # Attempt to read each of the disks
  for DISK in $DISKS ; do sudo blkid /dev/$DISK || true ; done

  # Look at the kernel log
  dmesg

  # Notice I/O errors related to the disk that the kernel remembers

  

  # Now to demostrate how this problem is fixed, I create a new Ubuntu
  20.04.0 VM

  
  # Add PPA with modified version of open-iscsi
  sudo add-apt-repository -y ppa:bswartz/open-iscsi
  sudo apt-get update

  # Install both iSCSI initiator and target on this host
  sudo apt-get -y install open-iscsi targetcli-fb

  # Start the services
  sudo systemctl start iscsid.service targetclid.service

  # Set the scan option to "manual"
  sudo sed -i 's/^\(node.session.scan\).*/\1 = manual/' /etc/iscsi/iscsid.conf
  sudo systemctl restart iscsid.service

  # Create a randomly generated target IQN
  TARGET_IQN=$(iscsi-iname)

  # Get the initator IQN
  INITIATOR_IQN=$(sudo awk -F = '/InitiatorName=/ {print $2}' 
/etc/iscsi/initiatorname.iscsi)

  # Set up an iSCSI target and target portal, and grant access to ourselves
  sudo targetcli /iscsi create $TARGET_IQN
  sudo targetcli /iscsi/$TARGET_IQN/tpg1/acls create $INITIATOR_IQN

  # Create two 1GiB LUNs backed by files, and expose them through the target 
portal
  sudo targetcli /backstores/fileio create lun1 /lun1 1G
  sudo targetcli /iscsi/$TARGET_IQN/tpg1/luns create /backstores/fileio/lun1 1
  sudo targetcli /backstores/fileio create lun2 /lun2 1G
  sudo targetcli /iscsi/$TARGET_IQN/tpg1/luns create 

[Group.of.nepali.translators] [Bug 1878155] Re: Thunderbird fails to connect to server in FIPS mode

2020-05-26 Thread Launchpad Bug Tracker
This bug was fixed in the package thunderbird -
1:68.8.0+build2-0ubuntu0.18.04.2

---
thunderbird (1:68.8.0+build2-0ubuntu0.18.04.2) bionic; urgency=medium

  [ Dariusz Gadomski ]
  * Disable reading /proc/sys/crypto/fips_enabled if FIPS is not enabled on
build (LP: #1878155)

 -- Olivier Tilloy   Wed, 13 May 2020
15:05:10 +0200

** Changed in: thunderbird (Ubuntu Bionic)
   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/1878155

Title:
  Thunderbird fails to connect to server in FIPS mode

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Eoan:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Thunderbird may become useless after booting into FIPS mode - it
  refuses to connect to server displaying the following message:

  Unexpected response from the server

  This document cannot be displayed unless you install the Personal
  Security Manager (PSM). Download and install PSM and try again, or
  contact your system administrator.

  This seems to be a result of the fact that despite Thunderbird for
  Ubuntu being with FIPS support disabled there's a piece of code that
  ignores the build flag and checks for `/proc/sys/crypto/fips_enabled`
  status anyway.

  Looks like upstream fix [1] needs to be applied to Thunderbird source
  under security/nss.

  [Test Case]

   * Configure an email account in Thunderbird. I was able to reproduce it with 
a gmail account.
   * Install FIPS modules as described in [2].
   * Boot into FIPS mode.
   * Open Thunderbird.

  [Regression Potential]

   * I can't identify regression potential - this is clearly a bug fixed
  upstream by a simple fix.

  [Other Info]
   
   * Related Firefox bug: https://bugs.launchpad.net/bugs/1843044
   * I was able to backport this fix and test it - the problem was gone. Xenial 
build is available in ppa:dgadomski/thunderbird.

  
  [1] 
https://hg.mozilla.org/projects/nss/raw-rev/55ba54adfcaea2f984a999a511eec5047462eb57
  [2] https://docs.ubuntu.com/security-certs/en/fips

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1878155/+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 1878155] Re: Thunderbird fails to connect to server in FIPS mode

2020-05-26 Thread Launchpad Bug Tracker
This bug was fixed in the package thunderbird -
1:68.8.0+build2-0ubuntu0.20.04.2

---
thunderbird (1:68.8.0+build2-0ubuntu0.20.04.2) focal; urgency=medium

  [ Dariusz Gadomski ]
  * Disable reading /proc/sys/crypto/fips_enabled if FIPS is not enabled on
build (LP: #1878155)

 -- Olivier Tilloy   Wed, 13 May 2020
15:17:37 +0200

** Changed in: thunderbird (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: thunderbird (Ubuntu Eoan)
   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/1878155

Title:
  Thunderbird fails to connect to server in FIPS mode

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Eoan:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Thunderbird may become useless after booting into FIPS mode - it
  refuses to connect to server displaying the following message:

  Unexpected response from the server

  This document cannot be displayed unless you install the Personal
  Security Manager (PSM). Download and install PSM and try again, or
  contact your system administrator.

  This seems to be a result of the fact that despite Thunderbird for
  Ubuntu being with FIPS support disabled there's a piece of code that
  ignores the build flag and checks for `/proc/sys/crypto/fips_enabled`
  status anyway.

  Looks like upstream fix [1] needs to be applied to Thunderbird source
  under security/nss.

  [Test Case]

   * Configure an email account in Thunderbird. I was able to reproduce it with 
a gmail account.
   * Install FIPS modules as described in [2].
   * Boot into FIPS mode.
   * Open Thunderbird.

  [Regression Potential]

   * I can't identify regression potential - this is clearly a bug fixed
  upstream by a simple fix.

  [Other Info]
   
   * Related Firefox bug: https://bugs.launchpad.net/bugs/1843044
   * I was able to backport this fix and test it - the problem was gone. Xenial 
build is available in ppa:dgadomski/thunderbird.

  
  [1] 
https://hg.mozilla.org/projects/nss/raw-rev/55ba54adfcaea2f984a999a511eec5047462eb57
  [2] https://docs.ubuntu.com/security-certs/en/fips

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1878155/+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 1878155] Re: Thunderbird fails to connect to server in FIPS mode

2020-05-26 Thread Launchpad Bug Tracker
This bug was fixed in the package thunderbird -
1:68.8.0+build2-0ubuntu0.19.10.2

---
thunderbird (1:68.8.0+build2-0ubuntu0.19.10.2) eoan; urgency=medium

  [ Dariusz Gadomski ]
  * Disable reading /proc/sys/crypto/fips_enabled if FIPS is not enabled on
build (LP: #1878155)

 -- Olivier Tilloy   Wed, 13 May 2020
15:10:20 +0200

** Changed in: thunderbird (Ubuntu Xenial)
   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/1878155

Title:
  Thunderbird fails to connect to server in FIPS mode

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Eoan:
  Fix Released
Status in thunderbird source package in Focal:
  Fix Released
Status in thunderbird source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * Thunderbird may become useless after booting into FIPS mode - it
  refuses to connect to server displaying the following message:

  Unexpected response from the server

  This document cannot be displayed unless you install the Personal
  Security Manager (PSM). Download and install PSM and try again, or
  contact your system administrator.

  This seems to be a result of the fact that despite Thunderbird for
  Ubuntu being with FIPS support disabled there's a piece of code that
  ignores the build flag and checks for `/proc/sys/crypto/fips_enabled`
  status anyway.

  Looks like upstream fix [1] needs to be applied to Thunderbird source
  under security/nss.

  [Test Case]

   * Configure an email account in Thunderbird. I was able to reproduce it with 
a gmail account.
   * Install FIPS modules as described in [2].
   * Boot into FIPS mode.
   * Open Thunderbird.

  [Regression Potential]

   * I can't identify regression potential - this is clearly a bug fixed
  upstream by a simple fix.

  [Other Info]
   
   * Related Firefox bug: https://bugs.launchpad.net/bugs/1843044
   * I was able to backport this fix and test it - the problem was gone. Xenial 
build is available in ppa:dgadomski/thunderbird.

  
  [1] 
https://hg.mozilla.org/projects/nss/raw-rev/55ba54adfcaea2f984a999a511eec5047462eb57
  [2] https://docs.ubuntu.com/security-certs/en/fips

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1878155/+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 1878864] Re: xenial/linux-cascade: 4.4.0-1019.21 -proposed tracker

2020-05-26 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => 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 --
  kernel-stable-master-bug: 1878873
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
- phase: Packaging
- phase-changed: Monday, 25. May 2020 10:36 UTC
+ phase: Building in ppa
+ phase-changed: Tuesday, 26. May 2020 10:19 UTC
  reason:
-   prepare-package: Stalled -- package not uploaded
-   prepare-package-meta: Stalled -- package not uploaded
-   prepare-package-signed: Stalled -- package not uploaded
+   build-packages-ppa: Ongoing -- building in ppa main:building
+ meta:building
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1878863
  variant: debs
  versions:
main: 4.4.0-1019.21
meta: 4.4.0.1019.22
signed: 4.4.0-1019.21

-- 
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/1878864

Title:
  xenial/linux-cascade: 4.4.0-1019.21 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux 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 --
  kernel-stable-master-bug: 1878873
  packages:
main: linux-cascade
meta: linux-meta-cascade
signed: linux-signed-cascade
  phase: Building in ppa
  phase-changed: Tuesday, 26. May 2020 10:19 UTC
  reason:
build-packages-ppa: Ongoing -- building in ppa main:building
  meta:building
  trackers:
xenial/linux-cascade/cascade-kernel: bug 1878863
  variant: debs
  versions:
main: 4.4.0-1019.21
meta: 4.4.0.1019.22
signed: 4.4.0-1019.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1878864/+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 1878873] Re: xenial/linux: 4.4.0-180.210 -proposed tracker

2020-05-26 Thread Po-Hsu Lin
4.4.0-180.210 - lowlatency
Regression test CMPL, RTB.

56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in amd64:
  ubuntu_bpf_jit - ld_abs+vlan_push/pop failed (bug 1879752)
  ubuntu_kernel_selftests - ld_abs+vlan_push/pop failed in test_bpf from net 
(bug 1879752)
  ubuntu_kvm_unit_tests - apic (bug 1748103) debug (bug 1821906) vmx (bug 
1821394) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) 
vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) 
vmx_pending_event_test (bug 1866591)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, 
ubuntu_xfstests_ext4, ubuntu_xfstests_xfs
Issue to note in i386:
  ubuntu_bpf_jit - ld_abs+vlan_push/pop failed (bug 1879752)
  ubuntu_kernel_selftests - ld_abs+vlan_push/pop failed in test_bpf from net 
(bug 1879752)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

4.4.0-180.210 - generic
Regression test CMPL, RTB.

56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in amd64:
  ubuntu_bpf_jit - ld_abs+vlan_push/pop failed (bug 1879752)
  ubuntu_kernel_selftests - ld_abs+vlan_push/pop failed in test_bpf from net 
(bug 1879752)
  ubuntu_kvm_unit_tests - apic (bug 1748103) debug (bug 1821906) vmx (bug 
1821394) vmx_host_state_area (bug 1866585) vmx_intr_window_test (bug 1866586) 
vmx_nm_test (bug 1866587) vmx_nmi_window_test (bug 1866588) 
vmx_pending_event_test (bug 1866591)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_bpf_jit - ld_abs+vlan_push/pop failed (bug 1879752)
  ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) 
ld_abs+vlan_push/pop failed in test_bpf from net (bug 1879752)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) gicv2-mmio-3p 
(bug 1828027) gicv2-mmio-up (bug 1828026) pmu on ms10-34-mcdivittB0-kernel (bug 
1751000)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, 
ubuntu_xfstests_ext4, ubuntu_xfstests_xfs
Issue to note in i386:
  ubuntu_bpf_jit - ld_abs+vlan_push/pop failed (bug 1879752)
  ubuntu_kernel_selftests - ld_abs+vlan_push/pop failed in test_bpf from net 
(bug 1879752)
  ubuntu_ltp_syscalls - btrfs fill_fs test in fallocate06 (bug 1866323) 
fanotify06 (bug 1833028) fanotify10 (bug 1802454) kill11 (bug 1865965)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in ppc64le (P8):
  ubuntu_bpf_jit - ld_abs+vlan_push/pop failed (bug 1879752)
  ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 
320M on Xenial P8 (bug 1813863)
  ubuntu_fan_smoke_test - Failed to fetch file from http://ports.ubuntu.com 
(bug 1864140)
  ubuntu_kernel_selftests - ld_abs+vlan_push/pop failed in test_bpf from net 
(bug 1879752)
  ubuntu_ltp_syscalls - copy_file_range01, fallocate04, fanotify13, fanotify14, 
fanotify15, fdatasync03, fgetxattr01,fremovexattr01, fremovexattr02, 
fsetxattr01, fsync01, fsync04, lremovexattr01, msync04, preadv03, preadv03_64, 
preadv203, preadv203_64, pwritev03, pwritev03_64, pwritev03, pwritev03_64, 
setxattr01, sync03, syncfs01 (bug 1842270) btrfs fill_fs test in fallocate06 
(bug 1866323) fanotify06 (bug 1833028) fanotify10 (bug 1802454) move_pages12 
(bug 1831043) kill11 (bug 1865965)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

50 / 51 tests were run, missing: ubuntu_boot
Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) 
killed by signal 1 bad config 1
  ubuntu_bpf_jit - ld_abs+vlan_push/pop from ubuntu_bpf_jit will fail on X 
s390x (bug 1868243)
  ubuntu_kernel_selftests - ld_abs+vlan_push/pop in test_bpf from net will fail 
on X s390x (bug 1868243)
  ubuntu_kvm_smoke_test - 

[Group.of.nepali.translators] [Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-26 Thread Edward Hope-Morley
** Also affects: cloud-archive/mitaka
   Importance: Undecided
   Status: New

-- 
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/1662324

Title:
  linux bridge agent disables ipv6 before adding an ipv6 address

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive mitaka series:
  New
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  In Progress

Bug description:
  [Impact]
  When using linuxbridge and after creating network & interface to ext-net, 
disable_ipv6 is 1. then linuxbridge-agent doesn't add ipv6 properly to newly 
created bridge.

  [Test Case]

  1. deploy basic mitaka env
  2. create external network(ext-net)
  3. create ipv6 network and interface to ext-net
  4. check if related bridge has ipv6 ip
  - no ipv6 originally
  or
  - cat /proc/sys/net/ipv6/conf/[BRIDGE]/disable_ipv6

  after this commit, I was able to see ipv6 address properly.

  [Regression]
  You need to restart neutron-linuxbridge-agent then there could be short 
downtime needed.

  [Others]

  -- original description --

  Summary:
  
  I have a dual-stack NIC with only an IPv6 SLAAC and link local address 
plumbed. This is the designated provider network nic. When I create a network 
and then a subnet, the linux bridge agent first disables IPv6 on the bridge and 
then tries to add the IPv6 address from the NIC to the bridge. Since IPv6 was 
disabled on the bridge, this fails with 'RTNETLINK answers: Permission denied'. 
My intent was to create an IPv4 subnet over this interface with floating IPv4 
addresses for assignment to VMs via this command:
    openstack subnet create --network provider \
  --allocation-pool start=10.54.204.200,end=10.54.204.217 \
  --dns-nameserver 69.252.80.80 --dns-nameserver 69.252.81.81 \
  --gateway 10.54.204.129 --subnet-range 10.54.204.128/25 provider

  I don't know why the agent is disabling IPv6 (I wish it wouldn't),
  that's probably the problem. However, if the agent knows to disable
  IPv6 it should also know not to try to add an IPv6 address.

  Details:
  
  Version: Newton on CentOS 7.3 minimal (CentOS-7-x86_64-Minimal-1611.iso) as 
per these instructions: http://docs.openstack.org/newton/install-guide-rdo/

  Seemingly relevant section of /var/log/neutron/linuxbridge-agent.log:
  2017-02-06 15:09:20.863 1551 INFO 
neutron.plugins.ml2.drivers.linuxbridge.agent.arp_protect 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Skipping ARP spoofing 
rules for port 'tap3679987e-ce' because it has port security disabled
  2017-02-06 15:09:20.863 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command: ['ip', 
'-o', 'link', 'show', 'tap3679987e-ce'] create_process 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:89
  2017-02-06 15:09:20.870 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Exit code: 0 execute 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:146
  2017-02-06 15:09:20.871 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command: ['ip', 
'addr', 'show', 'eno1', 'scope', 'global'] create_process 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:89
  2017-02-06 15:09:20.878 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Exit code: 0 execute 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:146
  2017-02-06 15:09:20.879 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command: ['ip', 
'route', 'list', 'dev', 'eno1', 'scope', 'global'] create_process 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:89
  2017-02-06 15:09:20.885 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Exit code: 0 execute 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:146
  2017-02-06 15:09:20.886 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command (rootwrap 
daemon): ['ip', 'link', 'set', 'brqe1623c94-1f', 'up'] execute_rootwrap_daemon 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:105
  2017-02-06 15:09:20.895 1551 DEBUG 
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Starting bridge 
brqe1623c94-1f for subinterface eno1 ensure_bridge 
/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:367
  2017-02-06 15:09:20.895 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command (rootwrap 
daemon): ['brctl', 'addbr', 

[Group.of.nepali.translators] [Bug 1662324] Re: linux bridge agent disables ipv6 before adding an ipv6 address

2020-05-26 Thread Seyeong Kim
** Changed in: neutron (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: neutron (Ubuntu Xenial)
 Assignee: (unassigned) => Seyeong Kim (xtrusia)

** Changed in: cloud-archive
   Status: New => 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/1662324

Title:
  linux bridge agent disables ipv6 before adding an ipv6 address

Status in Ubuntu Cloud Archive:
  Fix Released
Status in neutron:
  Fix Released
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Xenial:
  In Progress

Bug description:
  [Impact]
  When using linuxbridge and after creating network & interface to ext-net, 
disable_ipv6 is 1. then linuxbridge-agent doesn't add ipv6 properly to newly 
created bridge.

  [Test Case]

  1. deploy basic mitaka env
  2. create external network(ext-net)
  3. create ipv6 network and interface to ext-net
  4. check if related bridge has ipv6 ip
  - no ipv6 originally
  or
  - cat /proc/sys/net/ipv6/conf/[BRIDGE]/disable_ipv6

  after this commit, I was able to see ipv6 address properly.

  [Regression]
  You need to restart neutron-linuxbridge-agent then there could be short 
downtime needed.

  [Others]

  -- original description --

  Summary:
  
  I have a dual-stack NIC with only an IPv6 SLAAC and link local address 
plumbed. This is the designated provider network nic. When I create a network 
and then a subnet, the linux bridge agent first disables IPv6 on the bridge and 
then tries to add the IPv6 address from the NIC to the bridge. Since IPv6 was 
disabled on the bridge, this fails with 'RTNETLINK answers: Permission denied'. 
My intent was to create an IPv4 subnet over this interface with floating IPv4 
addresses for assignment to VMs via this command:
    openstack subnet create --network provider \
  --allocation-pool start=10.54.204.200,end=10.54.204.217 \
  --dns-nameserver 69.252.80.80 --dns-nameserver 69.252.81.81 \
  --gateway 10.54.204.129 --subnet-range 10.54.204.128/25 provider

  I don't know why the agent is disabling IPv6 (I wish it wouldn't),
  that's probably the problem. However, if the agent knows to disable
  IPv6 it should also know not to try to add an IPv6 address.

  Details:
  
  Version: Newton on CentOS 7.3 minimal (CentOS-7-x86_64-Minimal-1611.iso) as 
per these instructions: http://docs.openstack.org/newton/install-guide-rdo/

  Seemingly relevant section of /var/log/neutron/linuxbridge-agent.log:
  2017-02-06 15:09:20.863 1551 INFO 
neutron.plugins.ml2.drivers.linuxbridge.agent.arp_protect 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Skipping ARP spoofing 
rules for port 'tap3679987e-ce' because it has port security disabled
  2017-02-06 15:09:20.863 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command: ['ip', 
'-o', 'link', 'show', 'tap3679987e-ce'] create_process 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:89
  2017-02-06 15:09:20.870 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Exit code: 0 execute 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:146
  2017-02-06 15:09:20.871 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command: ['ip', 
'addr', 'show', 'eno1', 'scope', 'global'] create_process 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:89
  2017-02-06 15:09:20.878 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Exit code: 0 execute 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:146
  2017-02-06 15:09:20.879 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command: ['ip', 
'route', 'list', 'dev', 'eno1', 'scope', 'global'] create_process 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:89
  2017-02-06 15:09:20.885 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Exit code: 0 execute 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:146
  2017-02-06 15:09:20.886 1551 DEBUG neutron.agent.linux.utils 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Running command (rootwrap 
daemon): ['ip', 'link', 'set', 'brqe1623c94-1f', 'up'] execute_rootwrap_daemon 
/usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:105
  2017-02-06 15:09:20.895 1551 DEBUG 
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent 
[req-4917c507-369e-4a36-a381-e8b287cbc988 - - - - -] Starting bridge 
brqe1623c94-1f for subinterface eno1 ensure_bridge 
/usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py:367
  2017-02-06 15:09:20.895 1551 DEBUG neutron.agent.linux.utils