[Group.of.nepali.translators] [Bug 1738206] Re: linux-azure-edge: 4.14.0-1002.2 -proposed tracker

[Brad Figg]

** 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/regression-testing
   Status: New => Confirmed

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

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

** Description changed:

  This bug is for tracking the 4.14.0-1002.2 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
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Saturday, 16. December 2017 00:01 UTC

** Description changed:

  This bug is for tracking the 4.14.0-1002.2 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
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Saturday, 16. December 2017 00:01 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-azure-edge: 4.14.0-1002.2 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.14.0-1002.2 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
  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/1738206/+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 1551636] Re: MaaS on older releases need support for newer curtin images

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1551636

Title:
  MaaS on older releases need support for newer curtin images

Status in curtin:
  Fix Released
Status in MAAS:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Confirmed
Status in curtin source package in Wily:
  Confirmed
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  This came up when we chatted about problems using Xenial images on
  Maas this morning. And it will likely become a big problem when Xenial
  is released. Server environments do not change that quickly, so we
  should expect hosts running Trusty (cloud-archive or maas from the
  PPA) trying to provision Xenial.

  This currently is broken because the smarts of the curtin installer
  seems to have changed and the rootfs-tgz (the base filesystem used) no
  longer comes with the kernel (and modules) pre-installed. But the init
  phase of older curtin versions does not include steps to download a
  kernel from the archive. So we end up with a client that starts the
  final reboot without any kernel installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1551636/+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 1592149] Re: simple networking mode (net-meta) does not account for device names

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1592149

Title:
  simple networking mode (net-meta) does not account for device names

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users which do not use a customized network configuration rely
 on curtin's fallback/automatic configuration.  On Xenial and newer
 systems the network configuration that is generated doesn't always
 work due to the persistent nic names which do not match between
 initial install environment and booting the system after
 installation.

 This affects all curtin releases which use auto configure
 networking and an Ubuntu release which uses persistent network
 device nameing.
 
   * This SRU resolves the bug by ensuring auto configured networking
 includes nic naming rules to ensure the network device names match
 what is generated in the config.

  
  [Test Case]

   * On a Xenial 16.04 system
  - % apt-get install curtin
  - % OUTPUT_NETWORK_CONFIG=rendered-eni curtin net-meta -t /tmp auto

  
FAIL: Systems with the error will print an interfaces file to stdout

PASS: Systems with the fix with emit host networking config to the file
  "rendered-eni" and produces no output to stdout.

  
  [Regression Potential]

   * Users that use auto configuration may find that the persistent nic
 names in the target system are no longer ethN, but named based on
 location.

  
  [Original Description]
  I ran
   nosetests3 -v tests/vmtests/test_basic.py:XenialTestBasic
  and was seeing failures.

  That does an install without network config, so it relies on 'net-
  meta' of 'auto'.

  The install worked, but boot failed as networking was not configured.

  The issue is that the net-meta was writing /etc/network/interfaces
  file, but no udev rules or other mechanism to ensure that the device
  got the same name in the new environment.  That, coupled with a change
  in the commands between 'launch' and 'xkvm' meant that the install
  environment named the device 'ens3' and the installed environment
  'ens4'.

  I'll attach logs just for completeness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1592149/+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 1597522] Re: curtin passes wrong args to mkfs when making filesystem on advanced format disks

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1597522

Title:
  curtin passes wrong args to mkfs when making filesystem on advanced
  format disks

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * curtin passes wrong args to mkfs when making filesystem on advanced
 format disks (4k sector size)

 Curtin has been modified to only pass the '-s 1' sector-size flag 
 to the vfat formatting tools.  Curtin has been updated to specify
 the correct sector-size flags and values to other formatting
 utilities that support such settings.
 

  [Test Case]

   * Install proposed curtin package and attempt to format a disk with
 xfs filesystem using 4K logical blocksize for the disk.

PASS: Ubuntu successfully installs with xfs filesystem on top of a
  4k Disk

FAIL: Ubuntu fails to install with xfs filesystem on 4k disk.
  
  [Regression Potential]

   * Low; current users expecting xfs on 4k disks were blocked without
 this fix.

  
  [Original Description]
  During format handling, curtin detects the underlying block size of the disk 
and sets the filesystem block size accordingly.

  In order to properly handle a bug in mkfs.vfat, curtin adds the flag
  '-s 1'. However, curtin adds this flag to all disk format commands,
  not just to commands using 'mkfs.vfat'. This can lead to unexpected
  behavior with some formatting tools, and can cause installation to
  halt with others.

  For example, the mkfs.btrfs utility understands '-s' to mean
  sectorsize, so when curtin installs to an advanced format disk and
  storage config includes a btrfs formatted filesystem, curtin will
  create a filesystem that uses 1 byte sectors. This will greatly harm
  filesystem performance.

  For xfs volumes, this means that installation will fail completely, as
  the sectorsize attribute for xfs volumes must be specified in the
  format '-s size=512', so '-s 1' will cause mkfs.xfs to fail.

  Fortunately, this does not affect mkfs.ext* because these tools seem
  to silently ignore the '-s' flag, so most users likely have not been
  affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1597522/+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 1618429] Re: Curtin doesn't clean up previous MD configuration

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1618429

Title:
  Curtin doesn't clean up previous MD configuration

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * On some machines which have existing MDADM RAID metadata on one or
 more of disks, curtin fails to remove this existing metadata when
 instructed to do so and fails to install on such machines.

 Curtin has been updated to ignore mdadm asseble errors specifically
 in the case where curtin has been instructed to wipe a designated
 device. In the above case, curtin encountered an unexpected return
 code from mdadm assemble command which is not relevant since curtin
 is going to wipe the underlying device for re-installation.
 
  [Test Case]

   * Install proposed curtin package and deploy to a machine with a
 partial mdadm raid array which cannot be properly assembled.

PASS: Successfully deploy image with RAID configuration included.

FAIL: Deployment fails with the following error:

  Command: ['mdadm', '--assemble', '--scan']
  Exit code: 3
  Reason: -
  Stdout: ''
  Stderr: u'mdadm: /dev/md/4 assembled from 3 drives
  not enough to start the array.

  [Regression Potential]

   * Users requesting curtin 'preserve' existing raid configurations may
 be impacted.

  
  [Original Description]

  When deploying a machine in MAAS with a MD setup, deployment fails.
  Inspection shows that curtin doesn't clean up existin MD devices. On a
  failed machine I can see in dmesg:

  [   22.352672] md/raid1:md2: active with 2 out of 2 mirrors
  [   22.730212] md/raid1:md1: active with 2 out of 2 mirrors

  these are MD devices from previous deployment. Instead of deleting
  those, curtin tries to create a new one. So /proc/mdstat shows:

  Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] 
[raid10]
  md3 : inactive md1[1](S) md2[2](S)
    3125299568 blocks super 1.2

  md1 : active raid1 sdd[1] sdc[0]
    1562649792 blocks super 1.2 [2/2] [UU]

  md2 : active raid1 sdf[1] sde[0]
    1562649792 blocks super 1.2 [2/2] [UU]

  unused devices: 

  MAAS's storage config appears to be correct.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1618429/+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 1617375] Re: AttributeError: module 'curtin.util' has no attribute 'RunInChroot'

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1617375

Title:
  AttributeError: module 'curtin.util' has no attribute 'RunInChroot'

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Curtin removed a previously used python module method,
 'RunInChroot' which was used by non-ubuntu curthooks for 
 deploying OSes like CentOS.  Removing the method prevents
 deploying CentOS where it worked prior to updating.

 Curtin has been updated to include an alias to the previous method that
 provides backward compat to callers of 'RunInChroot'
 
  [Test Case]

   * Install proposed curtin package and deploy CentOS to target system

PASS: CentOS deploys successfully.

FAIL: CentOS deployment fails with message:

AttributeError: module 'curtin.util' has no attribute 'RunInChroot'

  [Regression Potential]

   * Other OSes besides CentOS may have used other flags against
 the original 'RunInChroot' method which is not being tested and
 may fail with the backward compat mode supporting 'RunInChroot'.


  [Original Description]
  I tested curtin bzr418 and bzr415, and I get the following error. This is a 
regression provided that it is not backward compatible and will cause all 
CentOS deployments via MAAS to fail.

  MAAS injects curtin_hooks code to CentOS images that call such
  function. If users upgrade to the latest curtin, they wont be able to
  deploy CentOS.

  AttributeError: module 'curtin.util' has no attribute 'RunInChroot'

  curtin bzr418:

  In [1]: import curtin.util

  In [2]: curtin.util.RunInChroot
  ---
  AttributeErrorTraceback (most recent call last)
   in ()
  > 1 curtin.util.RunInChroot

  AttributeError: module 'curtin.util' has no attribute 'RunInChroot'

  curtin bzr399:

  In [1]: import curtin.util

  In [2]: curtin.util.RunInChroot
  Out[2]: curtin.util.RunInChroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1617375/+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 1598310] Re: Curtin block.get_blockdev_sector_size incorrectly assumes block._lsblock will return a dictionary with only a single entry

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1598310

Title:
  Curtin block.get_blockdev_sector_size incorrectly assumes
  block._lsblock will return a dictionary with only a single entry

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Curtin block module method `get_blockdev_sector_size` fails when
 pointed at a device with multiple partitions instead of only 
 a partition.
 
 Curtin has been updated to filter the results to find the expected
 device path and return results for that device.
 
  [Test Case]

   * Install proposed curtin package on a system with a block device with
 multiple partitions.
 - python3 -c 'from curtin import block;
   block.get_blockdev_sector_size("/dev/sda")'

PASS: method call returns tuple with values
 - (512, 512)

FAIL: method call fails with stacktrace like
 - Traceback (most recent call last):
 File "", line 1, in 
 File "curtin/curtin/block/__init__.py", line 426,
  in get_blockdev_sector_size
   [parent] = info
 ValueError: too many values to unpack (expected 1)

  [Regression Potential]

   * Third-party consumers of curtin modules may have relied on this failure
 to detect devices which contained partitions.


  [Original Description]
  The function curtin.get_blockdev_sector_size will not work when called with a 
devpath which lsblk will return multiple lines of results for.

  This means that in some cases formatting a device other than a
  partition may fail, because block.mkfs checks for logical block size
  using this function.

  For example:
  Python 3.5.1+ (default, Mar 30 2016, 22:46:26)
  [GCC 5.3.1 20160330] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> from curtin import block
  >>> block.get_blockdev_sector_size('/dev/sda1')
  (512, 512)
  >>> block.get_blockdev_sector_size('/dev/sda5')
  Traceback (most recent call last):
    File "", line 1, in 
    File "/home/magicanus/code/curtin-clean/curtin/curtin/block/__init__.py", 
line 426, in get_blockdev_sector_size
  [parent] = info
  ValueError: too many values to unpack (expected 1)
  >>> block.get_blockdev_sector_size('/dev/sda')
  Traceback (most recent call last):
    File "", line 1, in 
    File "/home/magicanus/code/curtin-clean/curtin/curtin/block/__init__.py", 
line 426, in get_blockdev_sector_size
  [parent] = info
  ValueError: too many values to unpack (expected 1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1598310/+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 1615780] Re: Confusing 'success' message when apply_net fails.

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1615780

Title:
  Confusing 'success' message when apply_net fails.

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Curtin produced a configusing 'success' message when failying to apply
 a provided network configuration.

 Curtin has been updated to ensure that if 'apply_net' commands fail
 the return code is propagated up to the invocation and no longer 
 prints both a success and failure message when a failure occurs.
 
  [Test Case]

   * Install proposed curtin package and run the command
 - # curtin apply_net -t target -c bad.yaml

PASS: Curtin does not emit successful message:
  'Applied network configuration successfully'

FAIL: Curtin emits both
  'Applied network configuration successfully' and
  'failed to apply network config'

  [Regression Potential]

   * Users of apply_net cli command may have examined the output of the
 command which is now modified, as well as the return code.

  
  [Original Description]

  When apply_net fails, the user both a fail message and a success
  message.. a bit confusing.

  root@x1:~# curtin apply_net -t target -c bad.yaml
  Applying network configuration
  failed to apply network config
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/curtin/commands/apply_net.py", line 
78, in apply_net_main
  network_config=state['network_config'])
    File "/usr/lib/python3/dist-packages/curtin/commands/apply_net.py", line 
44, in apply_net
  ns = net.parse_net_config(network_config)
    File "/usr/lib/python3/dist-packages/curtin/net/__init__.py", line 283, in 
parse_net_config
  net_config = config.load_config(path)
    File "/usr/lib/python3/dist-packages/curtin/config.py", line 117, in 
load_config
  return yaml.safe_load(content)
    File "/usr/lib/python3/dist-packages/yaml/__init__.py", line 94, in 
safe_load
  return load(stream, SafeLoader)
    File "/usr/lib/python3/dist-packages/yaml/__init__.py", line 72, in load
  return loader.get_single_data()
    File "/usr/lib/python3/dist-packages/yaml/constructor.py", line 35, in 
get_single_data
  node = self.get_single_node()
    File "/usr/lib/python3/dist-packages/yaml/composer.py", line 36, in 
get_single_node
  document = self.compose_document()
    File "/usr/lib/python3/dist-packages/yaml/composer.py", line 55, in 
compose_document
  node = self.compose_node(None, None)
    File "/usr/lib/python3/dist-packages/yaml/composer.py", line 84, in 
compose_node
  node = self.compose_mapping_node(anchor)
    File "/usr/lib/python3/dist-packages/yaml/composer.py", line 133, in 
compose_mapping_node
  item_value = self.compose_node(node, item_key)
    File "/usr/lib/python3/dist-packages/yaml/composer.py", line 84, in 
compose_node
  node = self.compose_mapping_node(anchor)
    File "/usr/lib/python3/dist-packages/yaml/composer.py", line 127, in 
compose_mapping_node
  while not self.check_event(MappingEndEvent):
    File "/usr/lib/python3/dist-packages/yaml/parser.py", line 98, in 
check_event
  self.current_event = self.state()
    File "/usr/lib/python3/dist-packages/yaml/parser.py", line 428, in 
parse_block_mapping_key
  if self.check_token(KeyToken):
    File "/usr/lib/python3/dist-packages/yaml/scanner.py", line 116, in 
check_token
  self.fetch_more_tokens()
    File "/usr/lib/python3/dist-packages/yaml/scanner.py", line 257, in 
fetch_more_tokens
  self.get_mark())
  yaml.scanner.ScannerError: while scanning for the next token
  found character '\t' that cannot start any token
    in "", line 4, column 5:
    config:
  ^
  Applied network configuration successfully

  Note the emitting of messages

  "failed to apply network config"
  AND
  "Applied network configuration successfully"

  Really a minor issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1615780/+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 1597923] Re: curtin is unable to create whole disk fat/vfat formats

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1597923

Title:
  curtin is unable to create whole disk fat/vfat formats

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Curtin is unable to create FAT/VFAT filesystems on whole disks. The FAT
 filesystem creation utilities do not, by default, support creating a
 FAT filesystem against an unpartitioned device.

 Curtin has been updated to support passing a force flag to the
 utilities to allow custom storage configurations to use FAT/VFAT
 filesystems against such a device.
 
  [Test Case]

   * Install proposed curtin package and deploy Ubuntu to target system
 specifying a VFAT filesystem on top of a whole block device.

PASS: Ubuntu installation succeeds

FAIL: Ubuntu installation fails when attempting to format the block
  device on which the VFAT filesystem would reside.


  [Regression Potential]

   * Other OSes which may attempt to mount and read a VFAT filesystem
 created in so-called 'superfloppy' format might not recognize the
 filesystem.

  
  [Original Description]
  The mkfs.fat and mkfs.vfat tools do not by default permit the creation of a 
filesystem on a disk that has not been partitioned. This is not really a 
limitation of the filesystems themselves; it is just a safety feature to keep 
people from accidentally overwriting data.

  Since some curtin users may have a need for whole disk fat/vfat
  filesystems, it makes sense to use the '-I' flag for mkfs.vfat
  commands, which forces the tools to work on whole disks. It appears
  that this flag does not interfere with any of the other options in
  mkfs, and so is essentially a force flag, and can just be added to
  family_flag_mappings in block.mkfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1597923/+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 1641661] Re: curtin fails to partition software raid md0

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1641661

Title:
  curtin fails to partition software raid md0

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released
Status in curtin source package in Zesty:
  Fix Released

Bug description:
  - Begin SRU Template -
  [Impact]
  Curtin is unable to partition md (raid) devices.
  A system configured to put partitions on a raided device will fail to
  install.

  [Test Case]
  We added 2 test paths for this code to curtin
  a.) unit tests - these will run in the build process, so successful build
  verifies that this has passed.
  b.) vmtests named: *MirrorbootPartitions

  vmtests are currently only run on trunk, but we can modify source
  to run with the packaged version.  So, then to test the md path
  with a vm install, we will:
  i) run a xenial system
  ii) enable proposed
  iii) install curtin
  iv) run vmtests of the Mirrorboot tests using curtin from the sru.

  [Regression Potential]
  Quite low, the path for failure would be if there were some cases
  when the device name for a mdadm partition was /dev/mdNM rather than
  /dev/mdNpM.

  [Other Info]
  The upstream merge proposal is at
   https://code.launchpad.net/~raharper/curtin/trunk.lp1641661/+merge/311275
  and shows the code that went in to fix this.

  - End SRU Template -

  It seem curtin has problem with software RAID partitioning: md*
  Trying to deploy node in MAAS Version 2.0.0+bzr5189-0ubuntu1 (16.04.1).
  During partitioning stage curtin returns following error:

  An error occured handling 'md0-part1': OSError - could not get path to dev 
from kname: md01
  finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: failed: 
configuring partition: md0-part1
  finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: failed: 
curtin command block-meta
  Traceback (most recent call last):
    File "/curtin/curtin/commands/main.py", line 211, in main
  ret = args.func(args)
    File "/curtin/curtin/commands/block_meta.py", line 62, in block_meta
  meta_custom(args)
    File "/curtin/curtin/commands/block_meta.py", line 1041, in meta_custom
  handler(command, storage_config_dict)
    File "/curtin/curtin/commands/block_meta.py", line 550, in partition_handler
  get_path_to_storage_volume(info.get('id'), storage_config),
    File "/curtin/curtin/commands/block_meta.py", line 267, in 
get_path_to_storage_volume
  volume_path = block.kname_to_path(partition_kname)
    File "/curtin/curtin/block/__init__.py", line 114, in kname_to_path
  raise OSError('could not get path to dev from kname: {}'.format(kname))
  OSError: could not get path to dev from kname: md01
  could not get path to dev from kname: md01
  builtin command failed
  finish: cmd-install/stage-partitioning/builtin: FAIL: failed: running 'curtin 
block-meta custom'
  builtin took 8.861 seconds

  I've added commit which fixes mentioned error:
  http://bazaar.launchpad.net/~ruslan-
  lutcenko/curtin/curtin/revision/431

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1641661/+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 1645680] Re: apt feature broken on >=Yakkety due to new gpg agent

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1645680

Title:
  apt feature broken on >=Yakkety due to new gpg agent

Status in curtin:
  Fix Released
Status in GnuPG:
  Incomplete
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released
Status in curtin source package in Zesty:
  Fix Released

Bug description:
  - Begin SRU Template -
  [Impact]
  The mechanism for adding PPAs during was prone to failure when installing
  16.10 (yakkety) or newer systems.

  A curtin install of yakkety with the following configuration would
  fail:
apt:
sources:
  ignored1:
source: "ppa:paelzer/yourppa"

  [Test Case]
  Install a yakkety or zesty system with the above configuration.
  This can be accomplished by running the vmtest YakketyTestAptConfigCMDCMD
  with the installed version of curtin.

  It has configuration of
  apt:
sources:
  ignored:
 source: "ppa:curtin-dev/test-archive"
  curtin-test1.list:
 source: "deb $MIRROR $RELEASE-proposed main"

  
  [Regression Potential]

  [Other Info]
  This failure came as a result of change in behavior of gpg.  Curtin
  (indirectly through add-apt-repository) uses GPG to add PPAs into a
  chroot.  GPG2 began daemonizing itself, which meant that unmounts of the
  filesystem would fail due to open filehandles of the daemonized gpg
  process.

  There is further discussion both on the bug and in the upstream
  merge proposal [1] on other ways to do this.  The solution taken was
  a killall of processes named 'dirmgr' or 'gpg-agent' that were spawned
  after the chroot.

  [1] 
https://code.launchpad.net/~paelzer/curtin/curtin-bug-1645680-gpgagent/+merge/312143
  - End   SRU Template -

  Hi,
  while testing I found that when running apt feature related to 
add-apt-repository like:

  apt:
    sources:
  ignored1:
    source: "ppa:paelzer/yourppa"

  Or in fact any sort of add-apt-repository (also unrelated to the apt feature 
itself) like:
  late_commands:
   01_install_ppa: ['curtin', 'in-target --', 'add-apt-repository --yes 
ppa:paelzer/bug-1645274-multipath-merge']

  Then the installation fails.

  Both use the chroot to execute in target, but recent add-apt-
  repository seems so cause daemons to spawn which then let the umount
  fail.

  Failure is usually around something like:
  "umount: /tmp/tmptmucmfm0/target/dev: target is busy"

  Here an excerpt from a lsof +fg afterwards.
  dirmngr   6771 root1r   CHRLG,0x81,9  
0t0   11 /tmp/tmptmucmfm0/target/dev/urandom
  dirmngr   6771 root2w   CHR  W,LG1,3  
0t06 /tmp/tmptmucmfm0/target/dev/null
  gpg-agent 6776 root0r   CHRLG1,3  
0t06 /tmp/tmptmucmfm0/target/dev/null
  gpg-agent 6776 root1w   CHR  W,LG1,3  
0t06 /tmp/tmptmucmfm0/target/dev/null
  gpg-agent 6776 root2w   CHR  W,LG1,3  
0t06 /tmp/tmptmucmfm0/target/dev/null

  One of them could be shut down by:
  gpg-connect-agent --verbose KILLAGENT
  But not dirmngr, that has to be killed.
  Actually killing them seems ok (does not seem to create and later fallout).

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1645680/+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 1659509] Re: curtin fails to create MD devices

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1659509

Title:
  curtin fails to create MD devices

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  On some machines with existing MDADM RAID metadata on one or
  more disks, curtin can fails to remove this existing metadata when
  instructed to do so and fails to install on such machines.

  Improvement in curtin's ability to release holders on a disk
  and clear it mean that installation succeeds.

  [Test Case]
  Run curtin vmtest on tests/unittests/test_commands_block_meta.py
./tools/jenkins-runner tests/unittests/test_commands_block_meta.py

  [Regression Potential]
  Installation failures would be the most likely regression, and
  then most likely with multipath, raid or both.

  [Other Info]
   End   SRU Template 

   * On some machines which have existing MDADM RAID metadata on one or
     more disks, curtin fails to remove this existing metadata when
     instructed to do so and fails to install on such machines.

  On xenial we used curtin: 0.1.0~bzr425-0ubuntu1~16.04.1
  and for trusty deployment curtin_0.1.0~bzr399-0ubuntu1~14.04.1

  please see the attached full installation log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1659509/+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 1661337] Re: curtin does not retry when gpg fails to recv key

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1661337

Title:
  curtin does not retry when gpg fails to recv key

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  Curtin installation can be configured to install additional apt
  repositories and import gpg keys from a remote keyserver by fingerprint.
  'gpg --recv' can transiently fail, causing installation failure.

  The fix is to just retry
    gpg --keyserver keyserver.ubuntu.com --recv 

  [Test Case]
  Run curtin vmtest on XenialTestAptSrcDisablePockets
   ./tools/jenkins-runner tests/vmtests/test_apt_source.py

  The named test pushes curtin through use of gpg --keyserver.
  It does not guarantee failure and re-try, but does test the
  happy path.  Even if the gpg server was available on the first
  time, we at very least then verify that there is no regression.

  [Regression Potential]
  Low risk of regression.  The code change is just to sleep and retry
  a command if it failed.

  [Other Info]
  When looking further into some failures in add-apt-repository that were
  not fixed by re-trying, we found bug 1532855 .  It is not explicitly
  related to this bug, but is a similar failure path.

   End   SRU Template 

  In some cases we have transient network failure while attempting to
  recv gpg keys when configuring apt.

  https://jenkins.ubuntu.com/server/job/curtin-
  vmtest/737/artifact/output/XenialTestAptSrcDisablePockets/logs
  /install-serial.log

  [   40.161264] cloud-init[1528]: Command: ['gpg', '--keyserver', 
'keyserver.ubuntu.com', '--recv', '0E72 9061 0D2F 6DC4 D65E  A921 9A31 4EC5 
F470 A0AC']
  [   40.162213] cloud-init[1528]: Exit code: 2
  [   40.163711] cloud-init[1528]: Reason: -
  [   40.164256] cloud-init[1528]: Stdout: "gpgkeys: key 
0E7290610D2F6DC4D65EA9219A314EC5F470A0AC can't be retrieved\n"
  [   40.174200] cloud-init[1528]: Stderr: 'gpg: requesting key F470A0AC from 
hkp server keyserver.ubuntu.com\ngpg: no valid OpenPGP data found.\ngpg: Total 
number processed: 0\ngpg: keyserver communications error: keyserver helper 
general error\ngpg: keyserver communications error: unknown pubkey 
algorithm\ngpg: keyserver receive failed: unknown pubkey algorithm\n'
  [   40.180654] cloud-init[1528]: During handling of the above exception, 
another exception occurred:
  [   40.182056] cloud-init[1528]: Traceback (most recent call last):
  [   40.183644] cloud-init[1528]:   File "/curtin/curtin/gpg.py", line 65, in 
getkeybyid
  [   40.185067] cloud-init[1528]: recv_key(keyid, keyserver=keyserver)
  [   40.186653] cloud-init[1528]:   File "/curtin/curtin/gpg.py", line 48, in 
recv_key
  [   40.187895] cloud-init[1528]: (key, keyserver, error))

  Curtin should retry this command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1661337/+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 1649652] Re: [MAAS 2.1.2] Issue with adding routes to hosts via maas

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1649652

Title:
  [MAAS 2.1.2] Issue with adding routes to hosts  via maas

Status in curtin:
  Fix Released
Status in MAAS:
  Invalid
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released

Bug description:
   Begin SRU Template 
  [Impact]
  System configuration of networking with static routes did not
  work properly.  Systems where static routes were necessary would
  install but not come up with the desired networking.

  [Test Case]
  Run curtin vmtest on tests/vmtests/test_network_static_routes.py
  These tests show the failure without a patched curtin,
  and passing verifies the fix.

  [Regression Potential]
  Likeliest path to regression would be in failure of other network
  configurations.

  [Other Info]
   End   SRU Template 

  I'm trying to set routes for a subnet and have them be passed to a
  host during provision.

  This fails due to formatting issues in the /etc/network/interfaces
  file.

  I've attached both /etc/network/interfaces and the output of get-
  curtin-config. I'm running version 2.1.2+bzr-0ubuntu1~16.04.1.

  roaksoax suggested this was a curtin issue, but would still be tracked
  here.

  Please let me know if you need anymore information.

  Thanks,
  Brandon

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1649652/+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 1645515] Re: [FFe] Support for ISCSI block devices

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1645515

Title:
  [FFe] Support for ISCSI block devices

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released

Bug description:
   Begin Curtin SRU Template 
  [Impact]
  Curtin currently does not support specifying iSCSI targets in the storage
  configuration.  That means that MAAS or other users of curtin are not able
  to install to use iscsi disks during installation.

  The changes in this bug add the ability to specify non-root iSCSI targets
  to curtin, and include integration tests (vmtest) and unit tests to excercise
  the functionality.

  [Test Case]
  Run curtin vmtest on tests/vmtests/test_iscsi.py.
   ./tools/jenkins-runner tests/vmtests/test_iscsi.py

  The named test sets up an iscsi server with tgt and does an installation
  utilizing the disks provided by that iscsi server.

  [Regression Potential]
  Regression would most likely be a result of the new iscsi functionality
  mis-identifying configuration for a local disk as a iscsi disk, and then
  failing to do things as a result.

   End Curtin SRU Template 

  [FFe Justification]

   - Curtin currently does not support specifying iSCSI targets in the
  storage configuration.

   - Users have iSCSI targets they would like to install to via curtin.

   - The changes in this bug add the ability to specify non-root iSCSI
  targets in the YAML and include vmtests and unittests for that
  functionality.

   - Existing users are unaffected by this change, as if they specified
  a iSCSI compatible value in their YAML currently it would fail to
  parse. The added code is only used when iSCSI is used.

  ---

  Curtin needs to support the ability to attach an ISCSI block device
  during the installation and perform disk operations just like a
  locally attached block device. The disk also needs to be auto mounted
  when Ubuntu is rebooted after installation.

  Possible format:

  - id: sdb
    type: disk
    iscsi:
  target: iqn.2016-11.io.maas:storage.lun1
  portal: 192.168.122.2:3260

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1645515/+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 1662346] Re: vmtest: s390x requires zipl command

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1662346

Title:
  vmtest: s390x requires zipl command

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Installations of s390x systems will fail.  s390x requires zipl to boot
  and curtin assumed it was in the target image.  The change is simply
  to install it from the archive if it is not present.

  [Test Case]
  Run curtin vmtest on s390 as:
/tools/jenkins-runner tests/vmtests/test_simple.py:XenialTestSimple

  [Regression Potential]
  No regression potential on s390x as it simply did not work.
  Errant code could accidently attempt installation of zipl on other
  arch, but successful installation of other arch show that is not the
  case.

  [Other Info]

  Before any s390x vmtests can be run on any regular basis the zipl
  command needs to be added as a dependency during install. Currently a
  basic test fails [1] with the output:

  [  114.303504] cloud-init[1482]: Running command ['chroot', 
'/tmp/tmpua0mwwjb/target', 'zipl'] with allowed return codes [0] (shell=False, 
capture=False)
  [  114.304453] cloud-init[1482]: chroot: failed to run command 'zipl': No 
such file or directory

  [1] https://jenkins.ubuntu.com/server/job/curtin-vmtest-s390x/8/

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1662346/+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 1713537] Re: iscsi-targets don't quit session on shutdown

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1713537

Title:
  iscsi-targets don't quit session on shutdown

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Confirmed
Status in curtin source package in Zesty:
  Confirmed
Status in curtin source package in Artful:
  Fix Released

Bug description:
  1. Artful (MAAS Image)[a]
  2. open-iscsi 2.0.874-4ubuntu1
  3. On shutdown, all iscsi sessions to be stopped and unmounted
  4. Iscsi stops but does not stop sessions and shutdown is blocked/hung

  [^[[0;32m  OK  ^[[0m] Reached target Shutdown.
  [  125.666350]  connection4:0: ping timeout of 5 secs expired, recv timeout 
5, last rx 4294921130, last ping 4294922432, now 4294923712
  [  125.922334]  connection3:0: ping timeout of 5 secs expired, recv timeout 
5, last rx 4294921211, last ping 4294922496, now 4294923776
  [  126.178553]  connection2:0: ping timeout of 5 secs expired, recv timeout 
5, last rx 4294921292, last ping 4294922560, now 4294923840
  [  126.434334]  connection1:0: ping timeout of 5 secs expired, recv timeout 
5, last rx 4294921371, last ping 4294922624, now 4294923904

  Note, previously released Artful MAAS images work fine:
  http://images.maas.io/ephemeral-v2/daily/artful/amd64/20170721/
  which contain 

  open-iscsi  2.0.873+git0.3b4b4500-14ubuntu17

  a. http://images.maas.io/ephemeral-v2/daily/artful/amd64/20170826/

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1713537/+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 1351085] Re: documentation is out of date and sparse

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1351085

Title:
  documentation is out of date and sparse

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Curtin documentation is out-of-date and sparse.

 Curtin has been updated to include detailed documentation about
 its configuration, features, function and implementation.  The
 latest configuration is now available at:

 http://curtin.readthedocs.io/en/latest/
 
  [Test Case]

   n/a

  [Regression Potential]

   n/a

  
  [Original Description]

  The only documentation I could find curtin is doc/topics/overview.rst
  in the source.  It has several problems:

   - It talks about a final_commands hook which doesn't exist AFAICS

   - It doesn't talk about the late_commands hook which definitely does
     exist

   - It refers to both TARGET_MOUNT_POINT and TARGET_MP; I suspect only
     one exists

   - It has confusing examples which I don't think work/make sense, e.g:

  | config_hook: {{TARGET_MP}}/opt/curtin/config-hook

  The documentation is also pretty sparse in many ways, it doesn't for
  example:

   - Explain that the config is YAML

   - Explain other basic things about the config, e.g. what are the keys
     for hooks?  Do the names matter?  Does ordering matter?

   - Explain why you might want to use a list versus scalar for values

   - Explain how one might use YAML features such as 'repeated notes' to
     include data in the config that's intended for files

   - Explain that you probably want to use -- with curtin in-target to
     stop options of what you're trying to run being swallowed up by
     curtin

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1351085/+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 1562249] Re: Failed to deploy machine with HP Smart Array Raid 6i

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1562249

Title:
  Failed to deploy machine with HP Smart Array Raid 6i

Status in curtin:
  Fix Released
Status in Landscape Server:
  Invalid
Status in MAAS:
  Invalid
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Confirmed
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Attempting to deploy a machine with a HP Smart Array Raid 6i fails to
 install due to Curtin miscalculating the device path to CCISS
 partitions

 Curtin has been updated to properly calculate and handle the
 different forms of the HP CCISS array devices and partition path names
 in /dev and in /sys
 
  [Test Case]

   * Install proposed curtin package and deploy Ubuntu images to a system
 with an HP Smart Array device.

 PASS: Ubuntu OS successfully installed

 FAIL: Ubuntu fails to install with error message like:

  An error occured handling 'cciss!c0d0':
  OSError - [Errno 2] No such file or directory:  '/sys/block/c0d0/holders'

  [Regression Potential]

   * The fix included changes to how curtin determines the sysfs path to
 block devices and partitions.  It's possible that these changes could
 cause working systems which currently deploy to fail to deploy.
 However, this is mitigated by the fact that only HP Smart Array devices
 have special naming scheme for partitions so it's unlikely that non-HP
 storage devices are using the kernel path /dev/cciss as a prefix.

  
  [Original Description]
  Attempting to deploy a machine with a HP Smart Array Raid 6i fails. 
Installation output contains:

  Error: Partition(s) 5 on /dev/cciss/c0d0 have been written, but we have been 
unable to inform the kernel of the change, probably because it/they are in use. 
As a result, the old partition(s) will remain in use. You should reboot now 
before making further changes.
  An error occured handling 'cciss!c0d0': OSError - [Errno 2] No such file or 
directory: '/sys/block/c0d0/holders'
  [Errno 2] No such file or directory: '/sys/block/c0d0/holders'
  Installation failed with exception: Unexpected error while running command.
  Command: ['curtin', 'block-meta', 'custom']
  Exit code: 3
  Reason: -
  Stdout: "Error: Partition(s) 5 on /dev/cciss/c0d0 have been written, but we 
have been unable to inform the kernel of the change, probably because it/they 
are in use. As a result, the old partition(s) will remain in use. You should 
reboot now before making further changes.\nAn error occured handling 
'cciss!c0d0': OSError - [Errno 2] No such file or directory: 
'/sys/block/c0d0/holders'\n[Errno 2] No such file or directory: 
'/sys/block/c0d0/holders'\n"

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1562249/+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 1524031] Re: attempting to preserve disk curtin expects PTTYPE in blkid output

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1524031

Title:
  attempting to preserve disk curtin expects PTTYPE in blkid output

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * On a Trusty host, if users enable storage disk preserve feature,
 the use of blkid expects PTTYPE value in the output, however, this is
 not present in Trusty blkid output.  This prevents Trusty hosts from
 preserving existing partitions.

 Curtin has been updated to fallback to using parted to determine how to
 preserve existing partitions on disks when directed.
 
  [Test Case]

   * Install proposed curtin package and deploy in a Trusty ephemeral
 environment with the following storage configuration:

 storage:
  version: 1
  config:
- id: vdg
  model: Unknown Model
  preserve: true
  ptable: gpt
  serial: 64bddb21-61f3-4869-8
  type: disk
  wipe: superblock

PASS: Successfully deploy image while preserving the original partition
  table.

FAIL: Deployment fails with the following error:

line 530, in disk_handler
out.splitlines()))[0].split("=")[-1]
IndexError: list index out of range
list index out of range

  
  [Regression Potential]

   * No known other failures when using parted as replacement for blkid
 partition data.


  [Original Description]
  On a trusty host, this storage configuration breaks:

  storage:
    version: 1
    config:
  - id: vdg
    model: Unknown Model
    preserve: true
    ptable: gpt
    serial: 64bddb21-61f3-4869-8
    type: disk
    wipe: superblock

  like this:

  Running command ['partprobe', '/dev/vdg'] with allowed return codes [0, 1] 
(shell=False, capture=False)
  Running command ['udevadm', 'settle'] with allowed return codes [0] 
(shell=False, capture=False)
  Running command ['blkid', '-o', 'export', '/dev/vdg'] with allowed return 
codes [0] (shell=False, capture=True)
  An error occured handling 'vdg': IndexError - list index out of range
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/curtin/commands/main.py", line 208, in 
main
  ret = args.func(args)
    File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
63, in block_meta
  meta_custom(args)
    File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
1208, in meta_custom
  handler(command, storage_config_dict)
    File "/usr/lib/python3/dist-packages/curtin/commands/block_meta.py", line 
530, in disk_handler
  out.splitlines()))[0].split("=")[-1]
  IndexError: list index out of range
  list index out of range

  From this code here:

  # Check state of current ptable
  try:
  (out, _err) = util.subp(["blkid", "-o", "export", disk],
  capture=True)
  except util.ProcessExecutionError:
  raise ValueError("disk '%s' has no readable partition table or \
  cannot be accessed, but preserve is set to true, so cannot \
  continue")
  current_ptable = list(filter(lambda x: "PTTYPE" in x,
   out.splitlines()))[0].split("=")[-1]

  And the output of blkid -o export /dev/vdg on trusty instance is:

  # blkid -o export /dev/vdg
  UUID=ef30955b-8aa0-453f-a37d-d631a09a6f7c
  UUID_SUB=9a21ae23-6f14-405d-9e9a-8955855132d5
  TYPE=btrfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1524031/+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 1551937] Re: lvm and multipath and xenial not happy together

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1551937

Title:
  lvm and multipath and xenial not happy together

Status in curtin:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * MaaS deployments to systems with multipath configures cannot
 install Xenial releases due to a change in how multipath configures
 its friendly names.  On older releases (multipath-tools < 0.5.0)
 multipath-tools expects that the names of the devices will include
 names and parses the file with that expectation. However, on newer
 releases (multipath-tools >= 0.5.0) multipath-tools uses spaces to
 separate fields in the bindings file and fails if the device name
 includes spaces. 

 Curtin will detect the level of multipath-tools to be used in the
 target OS and adjusts how it generates device names for the binding
 file accordingly.
 
  [Test Case]

   * Install proposed curtin package and deploy custom storage
 configuration against a Power8 or similiar configured multipath
 system and select Xenial as the target OS.

PASS: The multipath configured machine will successfully install
both Xenial and Trusty.

FAIL: The multipath configured machine will fail to install Xenial
but will successfully install Trusty.

  [Regression Potential]

   * May impact users of systems with multipath storage configurations.

  
  [Original Description]

  tried deploy of xenial with curtin on a powerNV system.  the result was 
failure to mount the root, ending like this:
  Begin: Running /scripts/local-block ...   lvmetad is not active yet, using 
direc
  t activation during sysinit
    Volume group "mpath0" not found
    Cannot process volume group mpath0
  done.
  Begin: Running /scripts/local-block ...   lvmetad is not active yet, using 
direct activation during sysinit
    Volume group "mpath0" not found
    Cannot process volume group mpath0
  done.
  done.
  Gave up waiting for root device.  Common problems:
   - Boot args (cat /proc/cmdline)
     - Check rootdelay= (did the system wait long enough?)
     - Check root= (did the system wait for the right device?)
   - Missing modules (cat /proc/modules; ls /dev)
  ALERT!  /dev/mapper/mpath0-part2 does not exist.  Dropping to a shell!

  Related bugs:
   * bug 1429327: Boot from a unique, stable, multipath-dependent symlink
   * bug 1432062: multipath-tools-boot: support booting without 
user_friendly_names on devices with spaces in identifiers
   * bug 1552319: xenial kernel boot slow/timeout on power8 powerNV

  $ dpkg-query --show | egrep '(maas|curtin)'
  curtin-common   0.1.0~bzr359-0ubuntu1
  maas1.9.1+bzr4541-0ubuntu1~trusty1
  maas-cli1.9.1+bzr4541-0ubuntu1~trusty1
  maas-cluster-controller 1.9.1+bzr4541-0ubuntu1~trusty1
  maas-common 1.9.1+bzr4541-0ubuntu1~trusty1
  maas-dhcp   1.9.1+bzr4541-0ubuntu1~trusty1
  maas-dns1.9.1+bzr4541-0ubuntu1~trusty1
  maas-provision  2.2.2-0ubuntu4
  maas-provision-common   2.2.2-0ubuntu4
  maas-proxy  1.9.1+bzr4541-0ubuntu1~trusty1
  maas-region-controller  1.9.1+bzr4541-0ubuntu1~trusty1
  maas-region-controller-min  1.9.1+bzr4541-0ubuntu1~trusty1
  python-curtin   0.1.0~bzr359-0ubuntu1
  python-django-maas  1.9.1+bzr4541-0ubuntu1~trusty1
  python-maas-client  1.9.1+bzr4541-0ubuntu1~trusty1
  python-maas-provision   2.2.2-0ubuntu4
  python-maas-provisioningserver  1.9.1+bzr4541-0ubuntu1~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1551937/+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 1588547] Re: Generated bonding configuration is incorrect.

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   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/1588547

Title:
  Generated bonding configuration is incorrect.

Status in curtin:
  Fix Released
Status in MAAS:
  Opinion
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users attempting to configure nic bonding and using both ipv4 and ipv6
 encounter a misconfigured network due to a bug in curtin's handling of
 bond configuration and ipv6.  The error results in superflous 
 attributes and then broken ipv4 entries if preceeded by an ipv6
 address.

 This affects all curtin releases which support networking
 configuration.
 
   * This SRU fixes bonding and ipv6 configurations by no longer emitting
 attributes for aliased interfaces and calculating the correct
 inet type for a given interface.

  
  [Test Case]

   * On a Xenial 16.04 system
  - apt-get install curtin
  - cat >test.yaml 

[Group.of.nepali.translators] [Bug 1728048] Re: squashfs url matching is to strict

[Scott Moser]

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

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

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

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

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

** Changed in: cloud-initramfs-tools (Ubuntu Artful)
   Status: New => Confirmed

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

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

** Changed in: cloud-initramfs-tools (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/1728048

Title:
  squashfs url matching is to strict

Status in cloud-initramfs-tools:
  Fix Released
Status in cloud-initramfs-tools package in Ubuntu:
  Fix Released
Status in cloud-initramfs-tools source package in Xenial:
  Confirmed
Status in cloud-initramfs-tools source package in Zesty:
  Confirmed
Status in cloud-initramfs-tools source package in Artful:
  Confirmed

Bug description:
  The code that automatically determines a squashfs url is just to strict.
  You can explicitly declare it as squash with:
 root=squashfs:http://<>/...
  but currently the automatic matching requires it to end in .squashfs or 
.squash.

  This doesn't match urls like
/squashfs
/my-squash

  which are as obviously squashfs urls as others.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-initramfs-tools/+bug/1728048/+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 1708665] Re: prerotate.sh fails due to no shell for www-data user

[David Britton]

** Also affects: awstats (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

** Also affects: awstats (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/1708665

Title:
  prerotate.sh fails due to no shell for www-data user

Status in awstats package in Ubuntu:
  Triaged
Status in awstats source package in Xenial:
  Triaged
Status in awstats source package in Zesty:
  Triaged
Status in awstats source package in Artful:
  Triaged

Bug description:
  This was found in Ubuntu 16.04. I have not tested other versions.

  The /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh script does
  not run by default, because the 'www-data' user does not have a valid
  shell by default.

  root@www:~# bash -x /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh
  + UPDATE_SCRIPT=/usr/share/awstats/tools/update.sh
  + '[' -x /usr/share/awstats/tools/update.sh ']'
  + su -l -c /usr/share/awstats/tools/update.sh www-data
  This account is currently not available.

  We could give www-data a valid shell but my preferred fix is to edit
  /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh and explicitly
  specify the shell with '-s /bin/bash':

  
  diff -u ~/prerotate.sh /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh
  --- /root/prerotate.sh  2017-07-31 17:07:43.749559681 -0500
  +++ /etc/logrotate.d/httpd-prerotate/awstats/prerotate.sh   2017-07-31 
17:07:54.122034426 -0500
  @@ -2,5 +2,5 @@
   UPDATE_SCRIPT=/usr/share/awstats/tools/update.sh
   if [ -x $UPDATE_SCRIPT ]
   then
  -  su -l -c $UPDATE_SCRIPT www-data
  +  su -l -c $UPDATE_SCRIPT -s /bin/bash www-data
   fi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1708665/+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 1737923] Re: linux-kvm: 4.4.0-1014.19 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  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 --
  kernel-stable-master-bug: 1737916
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 15. December 2017 18:30 UTC

** Description changed:

  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: 1737916
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 15. December 2017 18:30 UTC
+ phase: Uploaded

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

Title:
  linux-kvm: 4.4.0-1014.19 -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:
  New
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:
  Confirmed
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm 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: 1737916
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737923/+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 1737944] Re: linux-gcp: 4.13.0-1003.6 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => 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/1737944

Title:
  linux-gcp: 4.13.0-1003.6 -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:
  New
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1737942
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737944/+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 1737944] Re: linux-gcp: 4.13.0-1003.6 -proposed tracker

[Brad Figg]

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

** Description changed:

  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 --
  kernel-stable-master-bug: 1737942
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 15. December 2017 17:30 UTC

** Description changed:

  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 --
  kernel-stable-master-bug: 1737942
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 15. December 2017 17:30 UTC
+ phase: Uploaded

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

Title:
  linux-gcp: 4.13.0-1003.6 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1737942
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737944/+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 1738206] Re: linux-azure-edge: 4.14.0-1002.2 -proposed tracker

[Łukasz Zemczak]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-azure-edge: 4.14.0-1002.2 -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:
  New
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:
  In Progress
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 upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure-edge package in Ubuntu:
  Invalid
Status in linux-azure-edge source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.14.0-1002.2 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
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1738206/+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 1737944] Re: linux-gcp: 4.13.0-1003.6 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

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

Title:
  linux-gcp: 4.13.0-1003.6 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
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 snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp 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 --
  kernel-stable-master-bug: 1737942
  phase: Packaging

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

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => 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/1737925

Title:
  linux-raspi2: 4.4.0-1081.89 -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:
  New
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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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 --
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

[Brad Figg]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => 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/1737927

Title:
  linux-snapdragon: 4.4.0-1083.88 -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:
  New
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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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 --
  kernel-stable-master-bug: 1737916
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737927/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

[Nicholas Skaggs]

** Changed in: juju
   Status: Triaged => Invalid

** Tags removed: verification-needed

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1737640/+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 1737927] Re: linux-snapdragon: 4.4.0-1083.88 -proposed tracker

[Brad Figg]

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

** Description changed:

  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 --
  kernel-stable-master-bug: 1737916
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 15. December 2017 15:30 UTC

** Description changed:

  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 --
  kernel-stable-master-bug: 1737916
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 15. December 2017 15:30 UTC
+ phase: Uploaded

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

Title:
  linux-snapdragon: 4.4.0-1083.88 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon 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 --
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

[Brad Figg]

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

** Description changed:

  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 --
  kernel-stable-master-bug: 1737916
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 15. December 2017 15:30 UTC

** Description changed:

  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 --
  kernel-stable-master-bug: 1737916
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 15. December 2017 15:30 UTC
+ phase: Uploaded

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

Title:
  linux-raspi2: 4.4.0-1081.89 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
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 snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi2 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 --
  kernel-stable-master-bug: 1737916
  phase: Uploaded

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

[Brad Figg]

** 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/regression-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

** Description changed:

  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: 1737916
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 15. December 2017 14:30 UTC

** Description changed:

  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: 1737916
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 15. December 2017 14:30 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-aws: 4.4.0-1045.54 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws 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: 1737916
  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/1737920/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

[Narinder Gupta]

The workaround by adding the proposed repository into package
repositories in MAAS worked for me.

** Also affects: opnfv
   Importance: Undecided
   Status: New

** Changed in: opnfv
   Status: New => Fix Committed

** Changed in: opnfv
   Importance: Undecided => Critical

** Changed in: opnfv
 Assignee: (unassigned) => Narinder Gupta (narindergupta)

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Triaged
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1737640/+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 1723198] Re: [SRU] upgrade from 14.04 to 16.04 fails with: ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned

[Eric Desrochers]

** Also affects: ca-certificates-java (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: dpkg (Ubuntu Zesty)

** No longer affects: dpkg (Ubuntu Xenial)

** No longer affects: dpkg (Ubuntu)

** Changed in: ca-certificates-java (Ubuntu)
   Status: New => Fix Released

** Changed in: ca-certificates-java (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: ca-certificates-java (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: ca-certificates-java (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: ca-certificates-java (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: ca-certificates-java (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: ca-certificates-java (Ubuntu Zesty)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Description changed:

  [Impact]
  
  ca-certificates-java currently depend on openjdk-7 which no longer exist
  after Trusty. It triggers failures while doing release upgrade, due to
- the triggers loop.
+ triggers loop.
  
  [Test Case]
  
  # Install Ubuntu server 14.04.5 + all the updates
  (I used "uvt-kvm create trustylp1723198 release=trusty")
  
  sudo apt update
  sudo apt upgrade
  
  # Install ca-certificates-java and man-db
  sudo apt install ca-certificates-java man-db
  
  # Upgrade to 16.04 LTS with do-release-upgrade and proceed with the upgrade
  sudo do-release-upgrade
  
  output:
  Removing ca-certificates-java (20130815ubuntu1) ...
  Removing openjdk-7-jre-headless:amd64 (7u151-2.6.11-2ubuntu0.14.04.1) ...
  dpkg: cycle found while processing triggers:
  chain of packages whose triggers are or may be responsible:
  man-db -> ca-certificates
  packages' pending triggers which are or may be unresolvable:
  ca-certificates: update-ca-certificates
  man-db: /usr/share/man
  dpkg: error processing package ca-certificates (--remove):
  triggers looping, abandoned
  
  [Regression Potential]
  
   * Regression is low, Xenial and late doesn't have openjdk-7 available
  as it has openjdk-8. This will have the effect to make the upgrade work
  correctly.
  
  [Other Info]
  
   * Debian bug :
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863803
  
   * Debian commit:
   
https://anonscm.debian.org/cgit/pkg-java/ca-certificates-java.git/commit/?id=0ddf3c9
  
  [Original Description]
  Test Case:
  1. Install Ubuntu server 14.04.5 + all the updates
  2. Install ca-certificates-java and man-db
  3. Reboot
  4. Upgrade to 16.04 LTS with do-release-upgrade and proceed with the upgrade
  
  Actual Result
  Upgrade fails with
  Removing ca-certificates-java (20130815ubuntu1) ...
  Removing openjdk-7-jre-headless:amd64 (7u151-2.6.11-2ubuntu0.14.04.1) ...
  dpkg: cycle found while processing triggers:
   chain of packages whose triggers are or may be responsible:
    man-db -> ca-certificates
   packages' pending triggers which are or may be unresolvable:
    ca-certificates: update-ca-certificates
    man-db: /usr/share/man
  dpkg: error processing package ca-certificates (--remove):
   triggers looping, abandoned
  
  I have no further information to give at this time except to say that
  there were several errors during the upgrade process from 14.04.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ca-certificates 20170717~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Oct 12 17:52:19 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2013-11-16 (1425 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: ca-certificates
  Title: package ca-certificates 20170717~16.04.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2017-10-12 (0 days ago)

** Description changed:

  [Impact]
  
  ca-certificates-java currently depend on openjdk-7 which no longer exist
  after Trusty. It triggers failures while doing release upgrade, due to
  triggers loop.
  
  [Test Case]
  
- # Install Ubuntu server 14.04.5 + all the updates
+ # Install Ubuntu server 14.04.5 + all the updates.
  (I used "uvt-kvm create trustylp1723198 release=trusty")
  
- sudo apt update
- sudo apt upgrade
+ sudo apt-get update
+ sudo apt-get dist-upgrade
  
- # Install ca-certificates-java and man-db
- sudo apt install ca-certificates-java man-db
+ # Install ca-certificates-java and man-db.
+ sudo apt-get install ca-certificates-java man-db
  
- # Upgrade to 16.04 LTS with do-release-upgrade and proceed with the upgrade
+ # Upgrade to 16.04 LTS.
  sudo do-release-upgrade
  
- output:
+ # Error:
+ ..
  Removing ca-certificates-java (20130815ubuntu1) ...
  

[Group.of.nepali.translators] [Bug 1737916] Re: linux: 4.4.0-105.128 -proposed tracker

[Brad Figg]

** 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/regression-testing
   Status: New => Confirmed

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

** Description changed:

  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
  
  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Thursday, 14. December 2017 12:03 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 15. December 2017 12:33 UTC

** Description changed:

  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
  
  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 15. December 2017 12:33 UTC
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 4.4.0-105.128 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
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 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:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux 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

  backports: 1737918,1737919
  derivatives: 1737920,1737921,1737922,1737923,1737925,1737927
  -- swm properties --
  boot-testing-requested: true
  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/1737916/+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 1737520] Re: linux-snapdragon: 4.4.0-1082.87 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

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

** Changed in: kernel-sru-workflow
   Status: In Progress => Fix Released

** Description changed:

  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: 1737511
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Friday, 15. December 2017 10:32 UTC

** Description changed:

  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: 1737511
- phase: Promoted to proposed
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Friday, 15. December 2017 10:32 UTC

** Tags removed: kernel-release-tracking-bug-live

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

Title:
  linux-snapdragon: 4.4.0-1082.87 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Fix Released

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: 1737511
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1737520/+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 1614248] Re: Package autofs does not include autofs.service file

[ChristianEhrhardt]

Per Debian fix in 5.1.2-1
"AFAIKS, autofs is providing a .service now with an After=sssd"
This is in Ubuntu as of Zesty.

I'll mark the tasks accordingly.

Adding the service in Xenial in general might have too much risk to cause other 
regressions - not sure thou - I beg your pardon - this is just an area I rarely 
work on.
Is there a way to express this in the sysv that xenial has, maybe via [1].
I can envision a setup with autofs and no ssh, so it is not required, but maybe 
"should".
So maybe in header of /etc/init.d/autofs:
  Should-Start: ssh

I wonder how that carries over into the systemd generator used in
Xenial.

Could one affected give it a try instead of adding the full .service file to 
add that and then run the following to pick up the changes
$ sudo systemctl daemon-reload

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

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

** Changed in: autofs (Ubuntu)
   Status: Triaged => 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/1614248

Title:
  Package autofs does not include autofs.service file

Status in autofs:
  Fix Released
Status in autofs package in Ubuntu:
  Fix Released
Status in autofs source package in Xenial:
  Confirmed

Bug description:
  Package autofs in Ubuntu 16.04 includes SysV startup script
  (/etc/init.d/autofs) and Upstart unit (/etc/init/autofs.conf), but
  does not include systemd service file. As a result, systemd starts
  autofs as part of its LSB (sysv) processing, which makes it difficult
  to ensure that autofs is started after services that it requires for
  proper functioning. In particular, unit autogenerated by systemd-sysv-
  generator for autofs does not include dependency on sssd.service.

  It appears that on the installation that I tested, systemd starts LSB
  services well after sssd is started, so the issue does not cause any
  visible problems, but this startup sequence is accidental. Given the
  number of other issues related to autofs startup in Xenial, requiring
  users to get their hands dirty just to have autofs run properly after
  boot, I think it would be advantageous to fix this simple oversight.
  (See bug 1566508, bug 1584818, bug 1588915)

  I attach an example service file for autofs that fixes this problem.
  In addition to sssd.service, this unit could also list nslcd.service,
  slapd.service and ypbind.service/nis.service in its After= line.
  However, these service files are also missing from their respective
  packages, and I am not even sure how NIS client service file would be
  called.

  $lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $apt-cache policy autofs
  autofs:
Installed: 5.1.1-1ubuntu3
Candidate: 5.1.1-1ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/autofs/+bug/1614248/+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 1737520] Re: linux-snapdragon: 4.4.0-1082.87 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-snapdragon - 4.4.0-1082.87

---
linux-snapdragon (4.4.0-1082.87) xenial; urgency=low

  * linux-snapdragon: 4.4.0-1082.87 -proposed tracker (LP: #1737520)

  [ Ubuntu: 4.4.0-104.127 ]

  * linux: 4.4.0-104.127 -proposed tracker (LP: #1737511)
  * upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file
system connection (LP: #1737033)
- Revert "libceph: MOSDOpReply v7 encoding"
- Revert "libceph: advertise support for TUNABLES5"
- Revert "crush: decode and initialize chooseleaf_stable"
- Revert "crush: add chooseleaf_stable tunable"
- Revert "crush: ensure take bucket value is valid"
- Revert "crush: ensure bucket id is valid before indexing buckets array"

 -- Kleber Sacilotto de Souza   Mon, 11 Dec
2017 15:18:19 +0100

** Changed in: linux-snapdragon (Ubuntu Xenial)
   Status: Confirmed => Fix Released

** Changed in: linux-snapdragon (Ubuntu Xenial)
   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/1737520

Title:
  linux-snapdragon: 4.4.0-1082.87 -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 promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Committed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-snapdragon package in Ubuntu:
  Invalid
Status in linux-snapdragon source package in Xenial:
  Fix Released

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: 1737511
  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/1737520/+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