date:20170505

[Group.of.nepali.translators] [Bug 1686978] Re: linux-hwe: 4.8.0-52.55~16.04.1 -proposed tracker

2017-05-05 Thread Brad Figg

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => 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/1686978

Title:
  linux-hwe: 4.8.0-52.55~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:
  In Progress
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  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: 1686976
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686978/+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 1448164] Re: runit cannot be installed (Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused)

2017-05-05 Thread Dimitri John Ledkov

** Changed in: runit (Ubuntu Xenial)
   Status: Won't Fix => Triaged

** Changed in: runit (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: runit (Ubuntu Xenial)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: runit (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.3

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

Title:
  runit cannot be installed (Unable to connect to Upstart: Failed to
  connect to socket /com/ubuntu/upstart: Connection refused)

Status in runit package in Ubuntu:
  Fix Released
Status in runit source package in Xenial:
  Triaged

Bug description:
  In Ubuntu 15.04 "runit" cannot be installed. postinst fails with the
  following message:

  start: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused

  Due to this error, packages depending on runit, like git-daemon-run,
  cannot be installed as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164/+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 1688632] [NEW] nplan 0.21 update

2017-05-05 Thread Mathieu Trudel-Lapierre

Public bug reported:

[Impact]
Nplan has been in active development and includes important bug fixes and 
critical features for users.

[Test case]
- Run nplan integration tests on the release
- Validate that netplan generate && netplan apply alone, without config, behave 
as expected (no result)
- Validate that netplan generate && netplan apply with minimal config writes 
/run/NetworkManager/conf.d/10-globally-managed-devices.conf
- Validate that netplan generate && netplan apply works with any existing 
configuation.

[Regression potential]
Any failure to work with existing configuration should be considered a 
regression. Any new failure of the test suite would be a regression.

** Affects: nplan (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: nplan (Ubuntu Xenial)
 Importance: High
 Assignee: Mathieu Trudel-Lapierre (cyphermox)
 Status: In Progress

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

** Also affects: nplan (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: nplan (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: nplan (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: nplan (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: nplan (Ubuntu Xenial)
Milestone: None => xenial-updates

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

Title:
  nplan 0.21 update

Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  In Progress

Bug description:
  [Impact]
  Nplan has been in active development and includes important bug fixes and 
critical features for users.

  [Test case]
  - Run nplan integration tests on the release
  - Validate that netplan generate && netplan apply alone, without config, 
behave as expected (no result)
  - Validate that netplan generate && netplan apply with minimal config writes 
/run/NetworkManager/conf.d/10-globally-managed-devices.conf
  - Validate that netplan generate && netplan apply works with any existing 
configuation.

  [Regression potential]
  Any failure to work with existing configuration should be considered a 
regression. Any new failure of the test suite would be a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1688632/+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 1688606] Re: SRU cloud-initramfs-rooturl to archive

2017-05-05 Thread Scott Moser

** No longer affects: cloud-initramfs-tools (Ubuntu Precise)

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

Title:
  SRU cloud-initramfs-rooturl to archive

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in cloud-initramfs-tools source package in Trusty:
  Confirmed
Status in cloud-initramfs-tools source package in Xenial:
  Confirmed
Status in cloud-initramfs-tools source package in Yakkety:
  Confirmed

Bug description:
  === Begin SRU Template ===
  [Impact]
  MAAS has an interest in booting entirely ephemerally without iscsi root.
  The package cloud-initramfs-rooturl supports booting with root coming
  from a url.
    root=http:///squashfs

  This function will be used to pxe boot into a RAM only system with no
  dependency on the network.

  [Test Case]
  1. make sure squashfs module is in the initramfs
     squashfs module is not automatically added to initramfs in precise.
     Just ensure that it is there.

     $ echo "manual_add_modules squashfs" |
    sudo tee /etc/initramfs-tools/hooks/squashfs

  2. install cloud-initramfs-rooturl
     sudo apt-get update
     sudo apt-get install cloud-initramfs-rooturl

  3. collect the kernel and newly generated initramfs

     sudo cat /boot/vmlinu?-$(uname -r) > kernel
     cp /boot/initrd.img-$(uname -r) initrd

  4. Download a squashfs image or a .tar.xz image

     rel="xenial"
     burl="http://cloud-images.ubuntu.com/daily/server;
     file="$rel-server-cloudimg-amd64-root.tar.xz"
     file="$rel-server-cloudimg-amd64.squashfs"
     wget "$burl/$rel/current/$file" -O "$file"

  5. run a web server
     python -m SimpleHTTPServer  &

  6. create a seed disk for cloud-init.

     $ cat > my-user-data < my-meta-data
     $ cloud-localds seed.img my-user-data my-meta-data

  7. Boot a vm using the kernel, initrd and url.

     cmdline="root=http://10.0.2.2:/$file console=ttyS0 -v "
     cmdline="${cmdline} overlayroot=tmpfs"

     qemu-system-x86_64 -enable-kvm \
    -device virtio-net-pci,netdev=net00 \
    -netdev type=user,id=net00 \
    -drive if=virtio,file=seed.img \
    -m 1G -nographic \
    -kernel kernel -initrd initrd \
    -append "root=$cmdline"

  [Regression Potential]
  Low.  This is adding a package previously not present.

  [Other Info]

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1688606/+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 1636531] Re: unittests blkid command fails on slave s390x

2017-05-05 Thread Scott Moser

** Changed in: cloud-init
   Status: Invalid => Fix Committed

** Changed in: cloud-init
   Importance: Undecided => Medium

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

Title:
  unittests blkid command fails on slave s390x

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
   Unit test updates to avoid leaking blkid calls from 
tests/unittests/test_datasource/test_altcloud.py.

  [Test Case]

  wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-
  info/plain/bin/lxc-proposed-snapshot

  chmod 755 lxc-proposed-snapshot

  
  # Create fake-blkid.sh
  cat fake-blkid.sh
  #!/bin/bash
  echo "LEAKED BLKID CALL"

  name=proposed-test
  for release in xenial yakkety zesty; do \
   ref=$release-proposed;
   ./lxc-proposed-snapshot --proposed --publish $release $ref;
   lxc init $ref $name;
   lxc start $name;
   sleep 10;
   lxc exec $name mv /sbin/blkid /sbin/blkid.orig;
   lxc file push fake-flkid.sh $name/sbin/blkid
   lxc exec $name git clone -b ubuntu/xenial 
https://git.launchpad.net/cloud-init 
   tox -e py27 tests/unittests/test_datasource/test_altcloud.py | grep 'LEAKED 
BLKID';
  done
   
  [Regression Potential] 
  None. Unit test changes only

  [Other Info]

  === End SRU Template ===

  
  Running the unittests on our slave s390x system, the blkid command fails. 
Running it manually returns the following:

  jenkins@s1lp04:~$ blkid -tLABEL=CDROM -odevice
  jenkins@s1lp04:~$ echo $?
  2
  jenkins@s1lp04:~$ lsblk
  NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  dasda 94:00  20.6G  0 disk
  |-dasda1  94:10  19.7G  0 part /
  `-dasda2  94:20 953.5M  0 part [SWAP]

  Full run output:
  https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1636531/+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 1673637] Re: cloud-init - Hosts in softlayer receiving warning

2017-05-05 Thread Scott Moser

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Zesty)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Artful)
   Importance: Undecided => Medium

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

Title:
  cloud-init - Hosts in softlayer receiving warning

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  
  === Begin cloud-init SRU Template ===
  [Impact]
  Softlayer user datasource is undetected when only openstack/latest 
config-drive directory is provided (due to softlayer user-data being provided).

  [Test Case]

  For cloud-init, the easiest way to demonstrate this is to
  create a lxc container and populate it with a '/config-drive' that only 
contains a openstack/latest path.

  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot
  chmod 755 lxc-proposed-snapshot
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/tools/make-configdrive-dir
  chmod 755 make-configdrive-dir
  name=test-proposed

  for release in xenial yaketty zesty; do
   ref=$release-proposed;
   ./lxc-proposed-snapshot --proposed --publish $release $ref;
   ./lxc init $ref $name;

  ## populate a /config-drive with attached 'make-configdrive-dir'
  ## and push it to the container

   d=$(mktemp -d)
   ./make-configdrive-dir "$d" "$name"
   rm -Rf "$d"
   lxc file pull $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg - |
  sed 's/NoCloud, //' |
  lxc file push - $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg;
   

   lxc start $name;
   sleep 10;
   lxc exec $name cp -r /config-drive /var/lib/cloud/seed/config_drive;
   lxc exec $name rm -rf /var/lib/cloud/seed/config_drive/openstack/2015-10-15;
   lxc exec $name sudo DEBUG_LEVEL=2 DI_LOG=stderr 
/usr/lib/cloud-init/ds-identify --force 2>&1 | grep latest ;

   # should produce config drive seeded directory had only 'latest'
  done

  
  [Regression Potential] 
  Minimal as this code is exercised for soft

  [Other Info]

  === End cloud-init SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1673637/+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 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22

2017-05-05 Thread Launchpad Bug Tracker

This bug was fixed in the package linux-firmware - 1.165

---
linux-firmware (1.165) artful; urgency=medium

  * Rebase against 
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
ade8332383e228cbdcfc605b5e5ef3aa51211401
- linux-firmware: liquidio: update firmware to v1.4.2
- iwlwifi: update -17 firmware for 3260, 7260 and 7265
- iwlwifi: update -22 firmware for 7265D and up
- iwlwifi: add -27 firmware for 3168, 7265D, 8000C and 8265
- linux-firmware/i915: Add HuC 1.07.1398 for SKL
- linux-firmware/i915: Add HuC 1.07.1398 for broxton
- linux-firmware/i915: HuC on 2.0.1810 for Kabylake
- linux-firmware/i915: GuC firmware for Broxton v8.7
- linux-firmware/i915: GuC firmware for Kabylake v9.14
- radeon/amdgpu: update license copyright dates
- radeon: add new firmware for SI chips
- rtlwifi: rtl8723bs: Add firmware for new driver
- qla2xxx: Update firmware version to 8.06.00
- amdgpu: add firmware for polaris12 asics
- amdgpu: update VI gfx/sdma firmware
- amdgpu: update VI smc/mc firmware
- update WHENCE for new amdgpu/polaris12_*.bin firmware
- linux-firmware: add firmware for mt76x2
- linux-firmware: update Marvell SD8897-B0 firmware image
- linux-firmware: update Marvell PCIe-USB8997 firmware image
- amdgpu: add smc firmware for new polaris variants
- Revert "amdgpu: update VI smc/mc firmware"
- Revert "amdgpu: update VI gfx/sdma firmware"
- linux-firmware/i915: Fix Corrupted GuC files.
- cxgb4: update firmware to revision 1.16.33.0
- nvidia: add GM20B PMU firmware
- nvidia: add GP102/GP104/GP106/GP107 signed firmware
- linux-firmware: intel: Add Geminilake audio firmware
- linux-firmware: Update firmware patch for Intel Bluetooth, 7265
- linux-firmware: Update firmware patch for Intel Bluetooth,8260
- linux-firmware: Update firmware file for Intel Bluetooth,8265
- brcm: update firmware for BCM43340/1 SDIO devices
- ath10k: QCA6174 hw3.0: update board-2.bin
- qed: Add firmware 8.15.3.0
- linux-firmware: update Marvell PCIe-USB8997 wifi-only firmware image
- linux-firmware: intel: Update Broxton audio firmware
- nfp: Add firmware 0.6.1
- mediatek: update MT8173 VPU firmware for unsupported VP9 profiles
- nvidia: add GP10B signed firmware
- nvidia: fix GP107 signed firmware
- linux-firmware: liquidio: update firmware to v1.5.1
- linux-firmware: update Marvell SD8887 firmware image
- linux-firmware: update Marvell SD8897-B0 firmware image
- rtl_bt: Update firmware for BT part of rtl8822be

  * intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22
(LP: #1647826)
- UBUNTU: SAUCE: Remove iwlwifi-8000C-22.ucode

 -- Seth Forshee   Fri, 05 May 2017 08:43:13
-0500

** Changed in: linux-firmware (Ubuntu Artful)
   Status: Confirmed => 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/1647826

Title:
  intel 8260 doesn't work with linux kernel 4.8+ when using ucode
  version 22

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Xenial:
  Fix Committed
Status in linux-firmware source package in Yakkety:
  Fix Released
Status in linux-firmware source package in Zesty:
  Fix Committed
Status in linux-firmware source package in Artful:
  Fix Released

Bug description:
  SRU Justification

  Impact: The -22 firmware for iwlwifi introduces regressions with some
  hardware versus earlier firmware versions. As no newer firmware is
  available, the only fix is to revert back to the older firmware which
  does work.

  Test Case: Using the -22 firmware with affected hardware produces the
  behavior described below. The -21 firmware does not.

  Regression Potential: Switching back to -21 could cause some
  regressions with other hardware supported by this firmware. However as
  -22 causes some hardware to completely fail to work any regressions
  are almost certain to be less severe than the current problems.

  ---

  The -22 microcode for the intel 8260 wifi adapter has compatibility
  issues with Linux Kernel 4.8 under certain hardware configurations.

  The iwlwifi module crashes resulting in wifi failing with "device not
  ready" and kernel errors reported in dmesg.

  [   10.691115] iwlwifi :6e:00.0: Microcode SW error detected.
  Restarting 0x200.

  Renaming the ucode file at /lib/firmware/iwlwifi-8000C-22.ucode to
  fallback to the -21 ucode resolves the issue and wifi begins working
  normally again.

  This is an issue with Linux kernel 4.8 on both yakkety and xenial, so
  the bug doesn't currently affect users on xenial, but will begin to
  after the 16.04.2 HWE release.  Kernel 4.4 is unaffected because it
  doesn't

[Group.of.nepali.translators] [Bug 1437353] Re: UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+

2017-05-05 Thread Mathieu Trudel-Lapierre

** Also affects: grub2-signed (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: grub2-signed (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: grub2-signed (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: grub2-signed (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit
  SFI/SFP+

Status in MAAS:
  Invalid
Status in maas-images:
  Triaged
Status in python-tx-tftp:
  Invalid
Status in grub2 package in Ubuntu:
  Fix Released
Status in grub2-signed package in Ubuntu:
  New
Status in grub2 source package in Trusty:
  New
Status in grub2-signed source package in Trusty:
  New
Status in grub2 source package in Xenial:
  In Progress
Status in grub2-signed source package in Xenial:
  In Progress
Status in grub2 source package in Yakkety:
  New
Status in grub2-signed source package in Yakkety:
  New

Bug description:
   I am using MAAS to commission and install machines. When I attempt to 
commission a machine with a "82599ES 10-Gigabit SFI/SFP+" network adapter the 
following happens:
  1) TFTP Request — bootx64.efi
  2) TFTP Request — /grubx64.efi
  3) Console hangs at grub prompt

  If I go into bios and force the adapter above into legacy mode then the 
machine is able to network boot and run through the commission process.
  1) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-initrd
  2) TFTP Request — ubuntu/amd64/generic/trusty/release/boot-kernel
  3) TFTP Request — ifcpu64.c32
  4) PXE Request — power off
  5) TFTP Request — pxelinux.cfg/01-90-e2-ba-52-23-78
  6) TFTP Request — pxelinux.cfg/71e3f102-bd8b-11e4-b634-3c18a001c80a
  7) TFTP Request — pxelinux.0

  Also, if I disconnect the cable to the adapter above and connect a
  cable to the integrated "I210 Gigabit" adapter which is configured for
  UEFI mode. The machine is able to network boot grubx64.efi and run
  through the commission process.

  ~$ dpkg -l '*maas*'|cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version
Architecture Description
  
+++-=-==--===
  ii  maas  1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS server all-in-one metapackage
  ii  maas-cli  1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS command line API tool
  ii  maas-cluster-controller   1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS server cluster controller
  ii  maas-common   1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS server common files
  ii  maas-dhcp 1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS DHCP server
  ii  maas-dns  1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS DNS server
  ii  maas-proxy1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS Caching Proxy
  ii  maas-region-controller1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS server complete region controller
  ii  maas-region-controller-min1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS Server minimum region controller
  ii  python-django-maas1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS server Django web framework
  ii  python-maas-client1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS python API client
  ii  python-maas-provisioningserver1.7.2+bzr3355-0ubuntu1~trusty1 
all  MAAS server provisioning libraries
  ~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1437353/+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 1682160] Re: update-grub-legacy-ec2 fails if no /etc/fstab causing install or upgrade fail

2017-05-05 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Medium
   Status: 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/1682160

Title:
  update-grub-legacy-ec2 fails if no /etc/fstab causing install or
  upgrade fail

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Fix Committed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  update-grub-legacy-ec2 fails on system with missing /etc/fstab with error 
message:
  Cannot determine root device.  Assuming /dev/hda1
  This error is probably caused by an invalid /etc/fstab
  awk: fatal: cannot open file `/etc/fstab' for reading (No such file or 
directory)

  [Test Case]

  Mimic missing /etc/fstab config using lxc-proposed-snapshot from 

https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot

  It publishes an image to lxd with proposed enabled and cloud-init
  upgraded.

  $ name=proposed-test
  $ for release in xenial yakkety zesty; do
  $ ref=$release-proposed
  $ lxc-proposed-snapshot --proposed --publish $release $ref
  $ lxc init $ref $name
  $ lxc start $name
  $ sleep 10
  $ lxc exec $name apt install grub-legacy-ec2
  $ lxc exec $name mv /etc/fstab /etc/fstab.orig
  $ lxc exec $name dpkg-reconfigure grub-legacy-ec2

  # Ensure error message does not exist "This error is probably caused
  by an invalid /etc/fstab"

  [Regression Potential] 
  Low. oneliner in a script

  [Other Info]
  Upstream commit:
   https://git.launchpad.net/cloud-init/commit/?id=fd9f36267541

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1682160/+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 1685810] Re: nova-lxd needs to read 'product_name' in environment, not 'platform'

2017-05-05 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Medium
   Status: 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/1685810

Title:
  nova-lxd needs to read 'product_name' in environment, not 'platform'

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Warning message for nova-lxd images in openstack clouds due to no valid 
datasource found.

  [Test Case]
  # It downloads a cloud image of a given release, and then creates a -proposed
  image with cloud-init upgraded.
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot
  chmod 755 get-proposed-image

  source novarc

  for release in xenial yakkety zesty do;
   ref=$release-proposed;
   lxc-proposed-snapshot --proposed --publish $release $ref;
   lxc image export $ref .;
   imagefile=`ls -tr *gz | tail -n 1`
   mkdir $ref;
   cd $ref;
   tar -zxvf ../$imagefile;
   cd rootfs;
   tar zcvf $ref.tar.gz *;
   #upload raw image to your cloud
openstack image create --disk-format raw --container-format bare --file 
$ref.tar.gz testing/$ref.tar.gz;
openstack server create --image testing/$ref.tar.gz --flavor=m1.tiny 
lxd-$release --key-name ;
nova floating-ip-create;
nova foating-ip-associate  ;
ssh ubuntu@ 'sudo DEBUG_LEVEL=2 DI_LOG=stderr 
/usr/lib/cloud-init/ds-identify --force 2>&1 | grep Found';   # single 
datasource: OpenStack
  done

  [Regression Potential]
  Low as this only addresses the warning by correctly identifying the OpenStack 
cloud datasource.

  
  [Other Info]

  === End SRU Template ===

  
  It seems that signals were crossed in bug 1661797.
  cloud-init implementation reads the environment variable 'platform' from 
pid1, and nova-lxd implementation exported 'product_name'.

  Thus, ssh to nova-lxd provided container, user sees a warning.
  Also
  $ sudo DEBUG_LEVEL=2 DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force 
2>&1 | grep PLAT
  PID_1_PLATFORM=unavailable

  While:
  $ sudo cat /proc/1/environ | tr '\0' '\n'
  product_name=OpenStack Nova
  container=lxc

  Related bugs:
   * bug 1661797: identify lxd-nova platform to enable Openstack datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1685810/+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 1688579] [NEW] linux-aws/linux-gke incorrectly producing and using linux--tools-common/linux--cloud-tools-common

2017-05-05 Thread Andy Whitcroft

Public bug reported:

Both linux-aws and linux-gke are producing linux-*-tools-common and
linux-*-cloud-tools-common.  By shipping common files in this way we
create conflicting packages:

$ sudo apt-get install linux-tools-generic
[...]
$ sudo apt-get install linux-tools-gke  
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-45 linux-headers-4.4.0-45-generic linux-headers-4.4.0-75 
linux-headers-4.4.0-75-generic linux-headers-4.8.0-27
  linux-headers-4.8.0-27-generic linux-image-4.4.0-45-generic 
linux-image-4.4.0-75-generic linux-image-4.8.0-27-generic
  linux-image-extra-4.4.0-45-generic linux-image-extra-4.4.0-75-generic 
linux-image-extra-4.8.0-27-generic linux-signed-image-4.4.0-45-generic
  linux-signed-image-4.4.0-75-generic snap-confine ubuntu-core-launcher
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  linux-gke-tools-4.4.0-1012 linux-gke-tools-common linux-tools-4.4.0-1012-gke
The following NEW packages will be installed
  linux-gke-tools-4.4.0-1012 linux-gke-tools-common linux-tools-4.4.0-1012-gke 
linux-tools-gke
0 to upgrade, 4 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/804 kB of archives.
After this operation, 2,344 kB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 427294 files and directories currently installed.)
Preparing to unpack .../linux-gke-tools-common_4.4.0-1012.12_all.deb ...
Unpacking linux-gke-tools-common (4.4.0-1012.12) ...
dpkg: error processing archive 
/var/cache/apt/archives/linux-gke-tools-common_4.4.0-1012.12_all.deb (--unpack):
 trying to overwrite '/usr/share/man/man8/x86_energy_perf_policy.8.gz', which 
is also in package linux-tools-common 4.4.0-77.98
Selecting previously unselected package linux-gke-tools-4.4.0-1012.
Preparing to unpack .../linux-gke-tools-4.4.0-1012_4.4.0-1012.12_amd64.deb ...
Unpacking linux-gke-tools-4.4.0-1012 (4.4.0-1012.12) ...
Selecting previously unselected package linux-tools-4.4.0-1012-gke.
Preparing to unpack .../linux-tools-4.4.0-1012-gke_4.4.0-1012.12_amd64.deb ...
Unpacking linux-tools-4.4.0-1012-gke (4.4.0-1012.12) ...
Selecting previously unselected package linux-tools-gke.
Preparing to unpack .../linux-tools-gke_4.4.0.1012.14_amd64.deb ...
Unpacking linux-tools-gke (4.4.0.1012.14) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-gke-tools-common_4.4.0-1012.12_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
$

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Confirmed

** Affects: linux-aws (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Confirmed

** Affects: linux-gke (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Confirmed

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Confirmed

** Affects: linux-aws (Ubuntu Xenial)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Confirmed

** Affects: linux-gke (Ubuntu Xenial)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Confirmed

** Changed in: linux-aws (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-aws (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-aws (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Also affects: linux-gke (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-gke (Ubuntu)
   Importance: Undecided => High

** Changed in: linux-gke (Ubuntu)
   Status: New => Confirmed

** Changed in: linux-gke (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-aws (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-gke (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: linux-aws (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: linux-aws (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: linux-aws (Ubuntu Xenial)
 Assignee: (unassigned) => Andy Whitcroft (apw)

** Changed in: linux-gke (Ubuntu

[Group.of.nepali.translators] [Bug 1367899] Re: cloud-init rsyslog config uses deprecated syntax

2017-05-05 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Low
   Status: 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/1367899

Title:
  cloud-init rsyslog config uses deprecated syntax

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init package in Debian:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Warning messages in /var/log/syslog on startup:
  warning: ~ action is deprecated, consider using the 'stop' statement instead

  [Test Case]
  Startup proposed lxcs and confirm warning message no longer present

  $ name=proposed-test
  $ for release in xenial yakkety zesty; do
  $ ref=$release-proposed
  $ lxc-proposed-snapshot --proposed --publish $release $ref
  $ lxc init $ref $name
  $ lxc start $name
  $ sleep 10
  $ lxc exec $name grep "warning: ~ action is deprecated, consider using the 
  'stop' statemen" /var/log/syslog
  # validate cloud-init messages are making it into syslog still
  $  lxc exec $name grep cloud-init /var/log/syslog
  $ lxc stop $name
  $ lxc delete $name

  
  [Regression Potential]
  Low. oneliner rsyslog change

  [Other Info]
  Upstream commit:

https://git.launchpad.net/~powersj/cloud-init/commit/?id=87dcf5769df4e5ce370be753b7d39f5a65cee2f2

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1367899/+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 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

2017-05-05 Thread Scott Moser

** Also affects: linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Zesty)
   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/1682871

Title:
  attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
  4.4

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Triaged
Status in cloud-init source package in Yakkety:
  New
Status in linux source package in Yakkety:
  New
Status in cloud-init source package in Zesty:
  New
Status in linux source package in Zesty:
  New

Bug description:
  [Impact]

   * When vlan interfaces are created, their mac address is copied from
  the underlying interface, but it is not marked by kernel as stolen.

   * When underlying interface MAC address is changed, it does not
  propagate to the vlan interfaces.

  [Test Case]

   * Create vlan interface, check the addr_assign_type sysfs attribute,
  it should be 2, not 0.

   * Update the base interface mac address, the mac address of the vlan
  interface should change too.

   * cloud-init test case

  
  
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/get-proposed-cloudimg;
  chmod 755 get-proposed-cloudimg;

  for release in xenial yakkety zesty; do
./get-proposed-cloudimg $release;
MODE=vlan ./btest-launch.sh $release-server-cloudimg-amd64-proposed.img 
;
# ubuntu/passw0rd
python3 -c 'from cloudinit.net import get_interfaces_by_mac; 
print(get_interfaces_by_mac())'; # results in no runtime error and doesn't 
report vlan interface name
  done
   


  
  [Regression Potential]

   * Userspace may rely on non-propagating MAC addresses, and the fact
  that vlan mac address type is wrongly stated as non-stolen; however
  this behaviour will be consistent with 4.7+ kernels.

  [Other Info]

   * Please cherrypick 308453aa9156a3b8ee382c0949befb507a32b0c1 into
  v4.4 kernels

  commit 308453aa9156a3b8ee382c0949befb507a32b0c1
  Author: Mike Manning 
  Date:   Fri May 27 17:45:07 2016 +0100

  vlan: Propagate MAC address to VLANs

  The MAC address of the physical interface is only copied to the VLAN
  when it is first created, resulting in an inconsistency after MAC
  address changes of only newly created VLANs having an up-to-date MAC.

  The VLANs should continue inheriting the MAC address of the physical
  interface until the VLAN MAC address is explicitly set to any value.
  This allows IPv6 EUI64 addresses for the VLAN to reflect any changes
  to the MAC of the physical interface and thus for DAD to behave as
  expected.

  Signed-off-by: Mike Manning 
  Signed-off-by: David S. Miller 

   * Original bug report

  When attempting to verify sru for bug 1669860, I found that vlans
  are not properly filtered out by 'get_interfaces_by_mac'.  That means
  that the bug is still present with vlans.

  The reason for this is that /sys/class/net//addr_assign_type
  shows '0' for a vlan on 4.4, but (correctly) shows '2' on 4.8.
  See https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net
  for doc on addr_assign_type.

  Related bugs:
   * bug 1669860: cloud-init attempts to rename bonds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1682871/+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 1684869] Re: growing root partition does not always work with root=PARTUUID=

2017-05-05 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Medium
   Status: Fix Released

** Also affects: cloud-init (Ubuntu Yakkety)
   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/1684869

Title:
  growing root partition does not always work with root=PARTUUID=

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Yakkety:
  New
Status in cloud-init source package in Zesty:
  New
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Growing the root partition would fail in either of two cases:
   a.) if the device /dev/root existed
   b.) the kernel command line had upper case letters in PARTUUID=

  [Test Case]
  get-proposed-image is
    
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/get-proposed-image
  It downloads a cloud image of a given release, and then creates a -proposed
  image with cloud-init upgraded.

  1.) get a (proposed) disk image image.
    and convert it to raw so you can read the partuuid with sfdisk
    (get-proposed-image does this, if not,
    'qemu-img convert -O raw orig.img orig.raw')
    ./get-proposed-image

  2.) get the partition uuid of the first partition
     $ raw=yakkety-server-cloudimg-amd64-proposed.raw
     $ ptuuid=$(sfdisk --part-uuid $raw 1)

  3.) create a nocloud seed
     $ printf "%s\n%s\n%s\n%s\n" "#cloud-config" "password: passw0rd" \
  "chpasswd: {expire: False}" "ssh_pwauth: True" > my-user-data
     $ echo "instance-id: $(uuidgen || echo i-abcdefg)" > my-meta-data
     $ cloud-localds my-seed.img my-user-data my-meta-data

  4.) extract kernel from inside the image
     $ sudo mount-image-callback $raw -- mchroot sh -xc 'cat /boot/vmlinu?-*' > 
kernel

  5.) boot instance with disk backed by the raw disk above.

     $ qemu-img create -f qcow2 -b $raw disk.img 10G
     $ qemu-system-x86_64 -enable-kvm \
     -drive file=disk.img,if=ide,index=0 -drive file=my-seed.img,if=ide \
     -net nic -net user,hostfwd=tcp::-:22 \
     -snapshot -m 768 -nographic -echr 0x05 \
     -kernel kernel \
     -append "root=PARTUUID=${ptuuid} ro console=tty1 console=ttyS0"

  6.) log in, verify / has been resized.
     log in with 'ubuntu' and password 'passw0rd'
  $ df -h /
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/root   9.6G 1009M  8.6G  11% /

  [Regression Potential]
  The regression path is really the case where devent2dev finds /dev/root
  and /dev/root exists.  In that case, we now possibly return a /dev/
  path when previously it would have returned /dev/root.

  [Other Info]
  The qemu-system-x86 command above uses ide devices.  This is because
  the ide device emulated by qemu is built into the -generic kernel,
  whilei the more common virtio-block or virtio-scsi are not.  If you
  attach those device types, it will fail with 'cant find root'.

  === End SRU Template ===

  When trying to verify I found a couple cases where this still does not
  work.

  Related bugs:
   * bug 1677376: growing partitions does not work when booted without initramfs
   * bug 1685291: RFC: virtio and virtio-scsi should be built in

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1684869/+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 1636531] Re: unittests blkid command fails on slave s390x

2017-05-05 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Artful)
   Status: New => Fix Released

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Zesty)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Artful)
   Importance: Undecided => Medium

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

Title:
  unittests blkid command fails on slave s390x

Status in cloud-init:
  Invalid
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
   Unit test updates to avoid leaking blkid calls from 
tests/unittests/test_datasource/test_altcloud.py.

  [Test Case]

  wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-
  info/plain/bin/lxc-proposed-snapshot

  chmod 755 lxc-proposed-snapshot

  
  # Create fake-blkid.sh
  cat fake-blkid.sh
  #!/bin/bash
  echo "LEAKED BLKID CALL"

  name=proposed-test
  for release in xenial yakkety zesty; do \
   ref=$release-proposed;
   ./lxc-proposed-snapshot --proposed --publish $release $ref;
   lxc init $ref $name;
   lxc start $name;
   sleep 10;
   lxc exec $name mv /sbin/blkid /sbin/blkid.orig;
   lxc file push fake-flkid.sh $name/sbin/blkid
   lxc exec $name git clone -b ubuntu/xenial 
https://git.launchpad.net/cloud-init 
   tox -e py27 tests/unittests/test_datasource/test_altcloud.py | grep 'LEAKED 
BLKID';
  done
   
  [Regression Potential] 
  None. Unit test changes only

  [Other Info]

  === End SRU Template ===

  
  Running the unittests on our slave s390x system, the blkid command fails. 
Running it manually returns the following:

  jenkins@s1lp04:~$ blkid -tLABEL=CDROM -odevice
  jenkins@s1lp04:~$ echo $?
  2
  jenkins@s1lp04:~$ lsblk
  NAME MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  dasda 94:00  20.6G  0 disk
  |-dasda1  94:10  19.7G  0 part /
  `-dasda2  94:20 953.5M  0 part [SWAP]

  Full run output:
  https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1636531/+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 1673637] Re: cloud-init - Hosts in softlayer receiving warning

2017-05-05 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Undecided
   Status: Fix Committed

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   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/1673637

Title:
  cloud-init - Hosts in softlayer receiving warning

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Yakkety:
  New
Status in cloud-init source package in Zesty:
  New
Status in cloud-init source package in Artful:
  Fix Committed

Bug description:
  
  === Begin cloud-init SRU Template ===
  [Impact]
  Softlayer user datasource is undetected when only openstack/latest 
config-drive directory is provided (due to softlayer user-data being provided).

  [Test Case]

  For cloud-init, the easiest way to demonstrate this is to
  create a lxc container and populate it with a '/config-drive' that only 
contains a openstack/latest path.

  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot
  chmod 755 lxc-proposed-snapshot
  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/tools/make-configdrive-dir
  chmod 755 make-configdrive-dir
  name=test-proposed

  for release in xenial yaketty zesty; do
   ref=$release-proposed;
   ./lxc-proposed-snapshot --proposed --publish $release $ref;
   ./lxc init $ref $name;

  ## populate a /config-drive with attached 'make-configdrive-dir'
  ## and push it to the container

   d=$(mktemp -d)
   ./make-configdrive-dir "$d" "$name"
   rm -Rf "$d"
   lxc file pull $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg - |
  sed 's/NoCloud, //' |
  lxc file push - $name/etc/cloud/cloud.cfg.d/90_dpkg.cfg;
   

   lxc start $name;
   sleep 10;
   lxc exec $name cp -r /config-drive /var/lib/cloud/seed/config_drive;
   lxc exec $name rm -rf /var/lib/cloud/seed/config_drive/openstack/2015-10-15;
   lxc exec $name sudo DEBUG_LEVEL=2 DI_LOG=stderr 
/usr/lib/cloud-init/ds-identify --force 2>&1 | grep latest ;

   # should produce config drive seeded directory had only 'latest'
  done

  
  [Regression Potential] 
  Minimal as this code is exercised for soft

  [Other Info]

  === End cloud-init SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1673637/+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 1644064] Re: sshd_config file permission changed to 644 if ssh_pwauth value is true or false

2017-05-05 Thread Scott Moser

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Xenial)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Yakkety)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Zesty)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: cloud-init (Ubuntu Artful)
   Importance: Undecided => Medium

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

Title:
  sshd_config file permission changed to 644 if ssh_pwauth value is true
  or false

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Existing security permissions on /etc/ssh/sshd_config file are not honored.

  [Test Case]

  wget 
https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot
  chmod 755 lxc-proposed-snapshot

  
  # create config.yaml
  cat config.yaml
  #cloud-config
  ssh_pwauth: true

  name=proposed-test
  for release in xenial yakkety zesty; do \
   ref=$release-proposed;
   lxc-proposed-snapshot --proposed --publish $release $ref;
   lxc init $ref $name;
   lxc start $name;
   sleep 10;
   lxc file pull $name/etc/ssh/sshd_config .;
   chmod 600 sshd_config;
   lxc file push sshd_config $name/etc/ssh/sshd_config;
   lxc config set $name user.user-data - < config.yml;
   lxc start;
   sleep 10;
   lxc exec $name ls -ltr /etc/ssh/sshd_config;  # should remain 600
   lxc stop $name;
   lxc delete $name;
  done

  [Regression Potential]
  Minimal as we are now honoring file permissions if an sshd_config file exists.

  [Other Info]

  === End SRU Template ===

  
  In my deploy image, the default permission of sshd_config file is 600. It 
always be changed to 644 after cloud-init run. After debug, it is caused by 
cloud-config item:

  ssh_pwauth: true

  The related code is:

  lines = [str(l) for l in new_lines]
  util.write_file(ssh_util.DEF_SSHD_CFG, "\n".join(lines))
  of file cc_set_passwords.py.

  write_file function use default mask 644 to write sshd_config. So my
  file permission changed.

  It shall be enhanced to read old sshd_config permission and write new
  sshd_config with old permission to avoid security issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1644064/+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 1687877] Re: bonding - mlx5 - speed changed to 0 after changing ring size

2017-05-05 Thread Stefan Bader

The proposed fix is part of upstream v4.5, so included in Yakkety/16,10
onwards.

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (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/1687877

Title:
  bonding - mlx5 - speed changed to 0 after changing ring size

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  The problem happens when changing the ring size of a mlx5_core interface that 
is part of a LACP bond.

  [268312.721076] mlx5_core :42:00.1 enp66s0f1: mlx5e_update_carrier:143: 
Link up
  [268312.721940] mlx5_core :42:00.1 enp66s0f1: speed changed to 0 for port 
enp66s0f1
  [268312.732089] bond0: link status up again after 0 ms for interface enp66s0f1

  
  the upstream commit "bonding: allow notifications for 
bond_set_slave_link_state " fix the issue, will cherry-pick and send to xenial 
git tree.

  
  Thanks,
  Talat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687877/+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 1688551] [NEW] Update chrome-gnome-shell to version 9 in all supported releases

2017-05-05 Thread Ken VanDine

Public bug reported:

Impact
==
gnome-shell provides a browser plugin so that users can manage GNOME Shell 
extensions by visiting https:/extensions.gnome.org/ in Firefox and compatible 
browsers.

This extension will stop working in Firefox once users upgrade to
Firefox 54. Firefox 54 is scheduled for upstream release June 13, 2017
and 54 Beta has been available since April 19th.

chrome-gnome-shell version 9 adds Firefox support that will keep working
in Firefox 54 and beyond.

There are actually two parts to chrome-gnome-shell: a system helper and a 
browser addon. The chrome-gnome-shell package provides the system helper. The 
browser addon can be installed directly without admin privileges from
https://addons.mozilla.org/en/firefox/addon/gnome-shell-integration/

or for Chrome at
https://chrome.google.com/webstore/detail/gnome-shell-integration/gphhapmejobijbbhgpjhcjognlahblep

For more details, see
https://blogs.gnome.org/ne0sight/2016/12/25/how-to-install-gnome-shell-extensions-with-firefox-52/

Test Case
=
- In Ubuntu GNOME, install the updated chrome-gnome-shell
- Open Firefox and browse to https://extensions.gnome.org/local/
- In the list of extensions, turn on the "Applications Menu". The Activities 
button in the top left of the screen should now read Applications and show a 
menu of installed apps when clicked.
- Turn off the "Applications Menu". The Applications button should revert to 
being a simple Activities button.

* Repeat the above test with chromium-browser

* If you are using Firefox 53, that test was just testing the old functionality 
(It's important that it still works though!). To test the new version:
- Install 
https://addons.mozilla.org/en-US/firefox/addon/gnome-shell-integration/
- To make sure that you aren't testing the old functionality, run
sudo rm /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
- Restart Firefox and do the above "Applications Menu" test.

- When you are finished testing, run this command to restore the manually 
deleted file:
sudo apt install --reinstall gnome-shell

Regression Potential
===
It's important that installing the Firefox helper does not break the existing 
Firefox support for https://extensions.gnome.org/

Other Info
==
chrome-gnome-shell 9 is available in artful. We want to make version 9 
available in -updates for 16.10, 16.04 and 17.04 to ensure no regressions when 
updating to firefox 54.

https://wiki.mozilla.org/RapidRelease/Calendar

** Affects: chrome-gnome-shell (Ubuntu)
 Importance: Undecided
 Assignee: Ken VanDine (ken-vandine)
 Status: Fix Released

** Affects: chrome-gnome-shell (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Ken VanDine (ken-vandine)
 Status: New

** Affects: chrome-gnome-shell (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Ken VanDine (ken-vandine)
 Status: New

** Affects: chrome-gnome-shell (Ubuntu Zesty)
 Importance: Undecided
 Assignee: Ken VanDine (ken-vandine)
 Status: New

** Affects: chrome-gnome-shell (Ubuntu Artful)
 Importance: Undecided
 Assignee: Ken VanDine (ken-vandine)
 Status: Fix Released

** Also affects: chrome-gnome-shell (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: chrome-gnome-shell (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Also affects: chrome-gnome-shell (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: chrome-gnome-shell (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: chrome-gnome-shell (Ubuntu Artful)
   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/1688551

Title:
  Update chrome-gnome-shell to version 9 in all supported releases

Status in chrome-gnome-shell package in Ubuntu:
  Fix Released
Status in chrome-gnome-shell source package in Xenial:
  New
Status in chrome-gnome-shell source package in Yakkety:
  New
Status in chrome-gnome-shell source package in Zesty:
  New
Status in chrome-gnome-shell source package in Artful:
  Fix Released

Bug description:
  Impact
  ==
  gnome-shell provides a browser plugin so that users can manage GNOME Shell 
extensions by visiting https:/extensions.gnome.org/ in Firefox and compatible 
browsers.

  This extension will stop working in Firefox once users upgrade to
  Firefox 54. Firefox 54 is scheduled for upstream release June 13, 2017
  and 54 Beta has been available since April 19th.

  chrome-gnome-shell version 9 adds Firefox support that will keep
  working in Firefox 54 and beyond.

  There are actually two parts to chrome-gnome-shell: a system helper and a 
browser addon. The chrome-gnome-shell package provides the system helper. The 
browser addon can be installed directly without admin privileges from

[Group.of.nepali.translators] [Bug 1688505] [NEW] Xenial update to 4.4.66 stable release

2017-05-05 Thread Stefan Bader

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.66 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.66 stable release shall be
applied:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-7308

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

Title:
  Xenial update to 4.4.66 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.66 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.66 stable release shall be
  applied:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688505/+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 1688483] [NEW] Xenial update to 4.4.65 stable release

2017-05-05 Thread Stefan Bader

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.65 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

The following patches from the 4.4.65 stable release shall be applied:
* tipc: make sure IPv6 header fits in skb headroom
* tipc: make dist queue pernet
* tipc: re-enable compensation for socket receive buffer double counting
* tipc: correct error in node fsm
* tty: nozomi: avoid a harmless gcc warning
* hostap: avoid uninitialized variable use in hfa384x_get_rid
* gfs2: avoid uninitialized variable warning
* tipc: fix random link resets while adding a second bearer
* tipc: fix socket timer deadlock
* xc2028: avoid use after free
* netfilter: nfnetlink: correctly validate length of batch messages
* tipc: check minimum bearer MTU
* vfio/pci: Fix integer overflows, bitmask check
* staging/android/ion : fix a race condition in the ion driver
* ping: implement proper locking
* perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race
* Linux 4.4.65

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Xenial)
 Importance: Medium
 Assignee: Stefan Bader (smb)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  Xenial update to 4.4.65 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.65 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.65 stable release shall be applied:
  * tipc: make sure IPv6 header fits in skb headroom
  * tipc: make dist queue pernet
  * tipc: re-enable compensation for socket receive buffer double counting
  * tipc: correct error in node fsm
  * tty: nozomi: avoid a harmless gcc warning
  * hostap: avoid uninitialized variable use in hfa384x_get_rid
  * gfs2: avoid uninitialized variable warning
  * tipc: fix random link resets while adding a second bearer
  * tipc: fix socket timer deadlock
  * xc2028: avoid use after free
  * netfilter: nfnetlink: correctly validate length of batch messages
  * tipc: check minimum bearer MTU
  * vfio/pci: Fix integer overflows, bitmask check
  * staging/android/ion : fix a race condition in the ion driver
  * ping: implement proper locking
  * perf/core: Fix concurrent sys_perf_event_open() vs. 'move_group' race
  * Linux 4.4.65

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688483/+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 1686978] Re: linux-hwe: 4.8.0-52.55~16.04.1 -proposed tracker

[Group.of.nepali.translators] [Bug 1448164] Re: runit cannot be installed (Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused)

[Group.of.nepali.translators] [Bug 1688632] [NEW] nplan 0.21 update

[Group.of.nepali.translators] [Bug 1688606] Re: SRU cloud-initramfs-rooturl to archive

[Group.of.nepali.translators] [Bug 1636531] Re: unittests blkid command fails on slave s390x

[Group.of.nepali.translators] [Bug 1673637] Re: cloud-init - Hosts in softlayer receiving warning

[Group.of.nepali.translators] [Bug 1647826] Re: intel 8260 doesn't work with linux kernel 4.8+ when using ucode version 22

[Group.of.nepali.translators] [Bug 1437353] Re: UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+

[Group.of.nepali.translators] [Bug 1682160] Re: update-grub-legacy-ec2 fails if no /etc/fstab causing install or upgrade fail

[Group.of.nepali.translators] [Bug 1685810] Re: nova-lxd needs to read 'product_name' in environment, not 'platform'

[Group.of.nepali.translators] [Bug 1688579] [NEW] linux-aws/linux-gke incorrectly producing and using linux--tools-common/linux--cloud-tools-common

[Group.of.nepali.translators] [Bug 1367899] Re: cloud-init rsyslog config uses deprecated syntax

[Group.of.nepali.translators] [Bug 1682871] Re: attempts to rename vlans / vlans have addr_assign_type of 0 on kernel 4.4

[Group.of.nepali.translators] [Bug 1684869] Re: growing root partition does not always work with root=PARTUUID=

[Group.of.nepali.translators] [Bug 1636531] Re: unittests blkid command fails on slave s390x

[Group.of.nepali.translators] [Bug 1673637] Re: cloud-init - Hosts in softlayer receiving warning

[Group.of.nepali.translators] [Bug 1644064] Re: sshd_config file permission changed to 644 if ssh_pwauth value is true or false

[Group.of.nepali.translators] [Bug 1687877] Re: bonding - mlx5 - speed changed to 0 after changing ring size

[Group.of.nepali.translators] [Bug 1688551] [NEW] Update chrome-gnome-shell to version 9 in all supported releases

[Group.of.nepali.translators] [Bug 1688505] [NEW] Xenial update to 4.4.66 stable release

[Group.of.nepali.translators] [Bug 1688483] [NEW] Xenial update to 4.4.65 stable release

21 matches

Site Navigation

Mail list logo

Footer information