[Group.of.nepali.translators] [Bug 1767166] Re: IBMCloud datasource does not recognize provisioning in debug mode.

[Chad Smith]

** Changed in: cloud-init (Ubuntu)
   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/1767166

Title:
  IBMCloud datasource does not recognize provisioning in debug mode.

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Cosmic:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Cloud-init is disabled in the provisioning state. If provisioning
  artifacts are left around after debug mode, cloud-init remains disabled
  and doesn't properly configure the instance.

  This issue only affects images that are being tested by IBM before official
  publication.  Once officially published, the images will have a 'production'
  tag, and bug does not reproduce.

  As such, it is believed that a regular end user is not really able to
  produce.

  [Test Case]
  cat > sethostname.yaml < /run/runcmd-ran.txt']
  EOF

  VM_IP=`launch-softlayer --pubkey-file ~/.ssh/id_rsa.pub -u
  sethostname.yaml -i os:xenial | awk '/primary ip/{printf "root@%s",
  $3}'`

  ssh root@$VM_IP -- dpkg-query --show cloud-init;
  ssh root@$VM_IP -- cloud-init status --long;
  ssh root@$VM_IP -- cloud-init analyze show;
  ssh root@$VM_IP -- sh -c '
mirror=http://archive.ubuntu.com/ubuntu
echo deb $mirror $(lsb_release -sc)-proposed main | tee 
/etc/apt/sources.list.d/proposed.list
apt-get update -q
apt-get install -qy cloud-init';
  ssh root@$VM_IP -- DEBUG_LEVEL=2 DI_LOG=stderr 
/usr/lib/cloud-init/ds-identify --force 2>&1 | grep provision
  ssh root@$VM_IP -- cloud-init clean --logs --reboot;
  ssh root@$VM_IP -- egrep 'provisioning|swinstall' /var/log/cloud-init.log
  ssh root@$VM_IP -- grep provision /run/cloud-init/ds-identify.log

  [Regression Potential]
  Regression will still be limited to softlayer instances as code changes are
  limited to softlayer datasource detection in ds-identify and
  DataSourceIBMCloud.

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

  This bug is currently fixed in bionic-proposed version
  (18.2-27-g6ef92c98-0ubuntu1~18.04.1) and
  cloud-init trunk, so first upload to ubuntu 'cc' will have it fixed.

  === End SRU Template ===

  
  When IBMCloud deploys from a template, artifacts from the
  provisioning stage are normally cleaned up.  Cloud-init relied'
  on that behavior to determine the provisioning boot from the subsequent
  post-provisioning boot.

  However, when testing, the provisioning stage will leave artifacts
  in place (/root/provisioningConfiguration.cfg).  This caused cloud-init
  to permenantly believe that it was in the provisioning stage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1767166/+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 1859725] Re: sru cloud-init (19.3.41 to 19.4.33) Xenial, Bionic and Eoan

[Chad Smith]

** Changed in: cloud-init (Ubuntu)
   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/1859725

Title:
  sru cloud-init (19.3.41 to 19.4.33) Xenial, Bionic and Eoan

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Eoan:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:

  - util: move uptime's else branch into its own boottime function (#53)
    [Igor Galić]
  - net: fix rendering of 'static6' in network config (#77)
  - fixed minor bug with mkswap in cc_disk_setup.py (#143) [andreaf74]
  - Add support for the amazon variant in cloud.cfg.tmpl (#119)
    [Frederick Lefebvre]
  - modules: drop cc_snap_config config module (#134)
  - cc_snappy: remove deprecated module (#127)
  - cloud-init: fix capitalisation of SSH (#126)
  - rbxcloud: fix dsname in RbxCloud [Adam Dobrawy]
  - apport: Add RbxCloud ds [Adam Dobrawy]
  - settings: Add RbxCloud [Adam Dobrawy]
  - cloudinit/netinfo: remove unused getgateway (#111)
  - azure: avoid re-running cloud-init when instance-id is byte-swapped
    (#84) [AOhassan]
  - ds_identify: if /sys is not available use dmidecode (#42) [Igor Galić]
  - network_state: handle empty v1 config (#45)
  - Multiple file fix for AuthorizedKeysFile config (#60) [Eduardo Otubo]
  - setup.py: Amazon Linux sets libexec to /usr/libexec (#52)
    [Frederick Lefebvre]

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates

  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.

  * Automated Test Results
  DONE: attach automated cloud-init-proposed test artifacts from tests for each 
release with lxd artifacts
  DONE: attach automated cloud-init-proposed test artifacts from tests for each 
release with kvm artifacts
  DONE: attach automated curtin vmtest with cloud-init proposed
  DONE: attach Solutions Testing team test results for each Bionic

  * Manual Test Results
  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on ec2 datasource
  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on gce datasource
  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on azure datasource

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  [Discussion]

  
  == End SRU Template ==

  == Full changelog ==
  - Only use gpart if it is the BSD gpart (#131) [Conrad Hoffmann]
  - freebsd: remove superfluous exception mapping (#166) [Gonéri Le Bouder]
  - ssh_auth_key_fingerprints_disable test: fix capitalization (#165)
    [Paride Legovini]
  - util: move uptime's else branch into its own boottime function (#53)
    [Igor Galić]
  - workflows: add contributor license agreement checker (#155)
  - net: fix rendering of 'static6' in network config (#77)
  - Make tests work with Python 3.8 (#139) [Conrad Hoffmann]
  - fixed minor bug with mkswap in cc_disk_setup.py (#143) [andreaf74]
  - freebsd: fix create_group() cmd (#146) [Gonéri Le Bouder]
  - doc: make apt_update example consistent (#154)
  - doc: add modules page toc with links (#153)
  - Add support for the amazon variant in cloud.cfg.tmpl (#119)
    [Frederick Lefebvre]
  - ci: remove Python 2.7 from CI runs (#137)
  - modules: drop cc_snap_config config module (#134)
  - migrate-lp-user-to-github: ensure Launchpad repo exists (#136)
  - docs: add initial troubleshooting to FAQ (#104) [Joshua Powers]
  - doc: update cc_set_hostname frequency and descrip (#109) [Joshua Powers]
  - freebsd: introduce the freebsd renderer (#61) [Gonéri Le Bouder]
  - cc_snappy: remove deprecated module (#127)
  - HACKING.rst: clarify that everyone needs to do the LP->GH dance (#130)
  - freebsd: cloudinit service requires devd (#132) [Gonéri Le Bouder]
  - cloud-init: fix capitalisation of SSH (#126)
  - doc: update cc_ssh clarify host and auth keys [Joshua Powers]
  - ci: emit names of tests run in Travis (#120)
  - Release 19.4
  - rbxcloud: fix 

[Group.of.nepali.translators] [Bug 1881018] Re: sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal

[Chad Smith]

** Changed in: cloud-init (Ubuntu)
   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/1881018

Title:
  sru cloud-init (19.4.33 to 20.2-45) Xenial, Bionic, Eoan and Focal

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Eoan:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:

  * d/control: drop python3-nose, python3-contextlib, python3-unittest2,
    python3-pyflakes, python3-six and python3-pep8 from build-deps
  * net: ubuntu focal prioritize netplan over eni even if both present
    (#267) (LP: #1867029)  # Focal-only, disabled on Xenial,Bionic, Eoan
  * d/cloud-init.templates: add RbxCloud datasource to dpkg config options
  * d/patches: to retain original behavior on Xenial, Bionic and Eoan
    - ec2 will not render full network config from IMDS unless 
apply_full_imds_network_config is True
     - network renderers default priority remains eni, netplan, sysconfig
   Focal and later prioritize netplan, eni, sysconfig

  * security (Use CVE-2020-8631, CVE-2020-8632)
  - cc_set_password: increase random pwlength from 9 to 20 (#189)
    (LP: #1860795)
  - utils: use SystemRandom when generating random password. (#204)
    [Dimitri John Ledkov]
  - Print ssh key fingerprints using sha256 hash (#188) (LP: #1860789)

  * aws:
    - DataSourceEc2: use metadata's NIC ordering to determine
  route-metrics (#342) (LP: #1876312)
   - ec2: render network on all NICs and add secondary IPs as static
     (#114) (LP: #1866930)
   - ec2: Do not fallback to IMDSv1 on EC2 (#216)
   - ec2: Do not log IMDSv2 token values, instead use REDACTED (#219)
     (LP: #1863943)
   - cloud-init analyze dump log support for Amazon Linux log formats
   - distros: drop leading/trailing hyphens from mirror URL labels (#296)
   - distros: replace invalid characters in mirror URLs with hyphens (#291)
     (LP: #1868232)
   - azurecloud: fix issues with instances not starting
     (#205) (LP: #1861921)
   - Add support for the amazon variant in cloud.cfg.tmpl (#119)
     [Frederick Lefebvre]
   - Add an Amazon distro in the redhat OS family [Frederick Lefebvre]

  * azure:
   - avoid re-running cloud-init when instance-id is byte-swapped
     (#84) [AOhassan]
   - drop reliance waalinux agent for fabric negotiation on Xenial

  * openstack
   - Add physical network type: cascading to openstack helpers (#200)
     [sab-systems]
   - Identify SAP Converged Cloud as OpenStack [Silvio Knizek]

  - rbxcloud: gracefully handle arping errors (#262) [Adam Dobrawy]
  - rbxcloud: fix dsname in RbxCloud [Adam Dobrawy] (LP: #1855196)
  - apport: Add RbxCloud ds [Adam Dobrawy]
  - VMWware: support to update guest info gc status if enabled (#261)
    [xiaofengw-vmware]
  - Scaleway: Fix DatasourceScaleway to avoid backtrace (#128)
    [Louis Bouchard]

  * tools
  - cloud-config schema validation for chef, apt_configure, cc_locale
  - instance-data: add cloud-init merged_cfg and sys_info keys to json
    (#214) (LP: #1865969)
  - util: read_cc_from_cmdline handle urlencoded yaml content (#275)

  * storage
  - cc_mounts: fix incorrect format specifiers (#316) (LP: #1872836)
  - swap file "size" being used before checked if str (#315) [Eduardo Otubo]
  - cc_disk_setup: fix RuntimeError (#270) (LP: #1868327)
  - cc_disk_setup: add swap filesystem force flag (#207)
  - Do not use fallocate in swap file creation on xfs. (#70)
    [Eduardo Otubo] (LP: #1781781)
  - fixed minor bug with mkswap in cc_disk_setup.py (#143) [andreaf74]

  * network
   - net: ignore 'renderer' key in netplan config (#306) (LP: #1870421)
   - net: support network-config:disabled on the kernel commandline (#232)
     (LP: #1862702)
   - Add support for NFS/EFS mounts (#300) [Andrew Beresford]
     (LP: #1870370)
   - net/cmdline: correctly handle static ip= config (#201)
     [Dimitri John Ledkov] (LP: #1861412)
   - net: fix rendering of 'static6' in network config (#77) (LP: #1850988)

  - cc_snappy: remove deprecated module (#127)
  - cc_grub_dpkg: determine idevs in more robust manner with grub-probe
    (#358) [Matthew Ruffell] (LP: #1877491)

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates

  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  

[Group.of.nepali.translators] [Bug 1950813] Re: version 27.3: on unattached machines update_status_timer incorrectly pings contracts.canonical.com/v1/resources

[Chad Smith]

Marking this bug as closed as the fix has now published in version
27.4.1 to Xenial, Bionic, Focal, Hirsute and Impish -updates pockets on
Nov 17th.

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Impish)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Hirsute)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  version 27.3: on unattached machines update_status_timer incorrectly
  pings contracts.canonical.com/v1/resources

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released
Status in ubuntu-advantage-tools source package in Focal:
  Fix Released
Status in ubuntu-advantage-tools source package in Hirsute:
  Fix Released
Status in ubuntu-advantage-tools source package in Impish:
  Fix Released

Bug description:
  Version 27.3 introduced a new systemd timer which runs a job named
  update_status_timer every 12 hours to update the status of supported
  UA services on machines which are attached to an Ubuntu Advantage
  licese.

  This job should not be run on machines without an active Ubuntu Advantage 
license attached because
  "unattached" Ubuntu machines no need to request available or applicable UA 
resources for the machine.

  In order to update_status information of UA services, this call results in 
GET against contracts.canonical.com/v1/resources providing the following data 
as querystring parameters:
   - kernel
   - ubuntu release name
   - architecture

  This ephemeral data is only used by the contract service to properly
  report what services are available or applicable to that running
  kernel, Ubuntu release and CPU architecture and is not logged or
  persisted.

  This bug is currently fixed and committed upstream to avoid calling
  this endpoint on unattached Ubuntu machines and queued for release to
  Xenial, Bionic, Focal, Hirsute and Jammy as version 27.4.1. Expected
  published fix within a week.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1950813/+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 1950813] [NEW] version 27.3: on unattached machines update_status_timer incorrectly pings contracts.canonical.com/v1/resources

[Chad Smith]

Public bug reported:

Version 27.3 introduced a new systemd timer which runs a job named
update_status_timer every 12 hours to update the status of supported UA
services on machines which are attached to an Ubuntu Advantage licese.

This job should not be run on machines without an active Ubuntu Advantage 
license attached because
"unattached" Ubuntu machines no need to request available or applicable UA 
resources for the machine.

In order to update_status information of UA services, this call results in GET 
against contracts.canonical.com/v1/resources providing the following data as 
querystring parameters:
 - kernel
 - ubuntu release name
 - architecture

This ephemeral data is only used by the contract service to properly
report what services are available or applicable to that running kernel,
Ubuntu release and CPU architecture and is not logged or persisted.

This bug is currently fixed and committed upstream to avoid calling this
endpoint on unattached Ubuntu machines and queued for release to Xenial,
Bionic, Focal, Hirsute and Jammy as version 27.4.1. Expected published
fix within a week.

** Affects: ubuntu-advantage-tools (Ubuntu)
 Importance: Critical
 Status: Fix Committed

** Affects: ubuntu-advantage-tools (Ubuntu Xenial)
 Importance: Critical
 Status: Fix Committed

** Affects: ubuntu-advantage-tools (Ubuntu Bionic)
 Importance: Critical
 Status: Fix Committed

** Affects: ubuntu-advantage-tools (Ubuntu Focal)
 Importance: Critical
 Status: Fix Committed

** Affects: ubuntu-advantage-tools (Ubuntu Hirsute)
 Importance: Critical
 Status: Fix Committed

** Affects: ubuntu-advantage-tools (Ubuntu Impish)
 Importance: Critical
 Status: Fix Committed

** Also affects: ubuntu-advantage-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: ubuntu-advantage-tools (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: ubuntu-advantage-tools (Ubuntu Hirsute)
   Status: New => Fix Committed

** Changed in: ubuntu-advantage-tools (Ubuntu Impish)
   Status: New => Fix Committed

** Description changed:

  Version 27.3 introduced a new systemd timer which runs a job named
  update_status_timer every 12 hours to update the status of supported UA
  services on machines which are attached to an Ubuntu Advantage licese.
  
- 
- This job should not be run on machines without an active Ubuntu Advantage 
license attached because 
+ This job should not be run on machines without an active Ubuntu Advantage 
license attached because
  "unattached" Ubuntu machines no need to request available or applicable UA 
resources for the machine.
  
  In order to update_status information of UA services, this call results in 
GET against contracts.canonical.com/v1/resources providing the following data 
as querystring parameters:
-  - kernel
-  - ubuntu release name 
-  - architecture
+  - kernel
+  - ubuntu release name
+  - architecture
  
- 
- This ephemeral data is only used by the contract service to properly report 
what services are available or applicable to that running kernel, Ubuntu 
release and CPU architecture. 
+ This ephemeral data is only used by the contract service to properly
+ report what services are available or applicable to that running kernel,
+ Ubuntu release and CPU architecture and is not logged or persisted.
  
  This bug is currently fixed and committed upstream to avoid calling this
  endpoint on unattached Ubuntu machines and queued for release to Xenial,
  Bionic, Focal, Hirsute and Jammy as version 27.4.1. Expected published
  fix within a week.

** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
   Importance: Undecided => Critical

** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: ubuntu-advantage-tools (Ubuntu Focal)
   Importance: Undecided => Critical

** Changed in: ubuntu-advantage-tools (Ubuntu Hirsute)
   Importance: Undecided => Critical

** Changed in: ubuntu-advantage-tools (Ubuntu Impish)
   Importance: Undecided => Critical

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

Title:
  version 27.3: on unattached machines update_status_timer incorrectly
  pings 

[Group.of.nepali.translators] [Bug 1920836] Re: Show Extended Security Maintenence status

[Chad Smith]

# Impish desktop results: SUCCESS non-LTS has neither ESM-Infra nor ESM-Apps 
support or availability.
# so  1. it will not expose "Extend..." links to provide ESM information in 
Updates tab
# and 2. When attached no ESM information will be represented in Updates tab


1. # install proposed

$ cat > setup_proposed.sh  Fix Committed

** Changed in: software-properties (Ubuntu Impish)
   Importance: Undecided => High

** Changed in: software-properties (Ubuntu Impish)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Show Extended Security Maintenence status

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Committed
Status in software-properties source package in Hirsute:
  Fix Committed
Status in software-properties source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  There is not currently a graphical method of determining if a system is 
subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) 
updates. This is resolved by adding some [new 
UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to 
the software properties application.

  [Test Case]
  1. Install latest version of Ubuntu advantage:
  $ sudo add-apt-repository ppa:ua-client/stable
  $ sudo apt update
  $ sudo apt upgrade
  2. Open Software Properties
  3. Go to Updates tab.

  Expected result:
  Information is shown that indicates if this system is using Extended Security 
Maintenance updates, when updates will supported until, and a link to upgrade 
to ESM.

  Observed result:
  No ESM information currently shown.

  [Where problems could occur]
  - Software properties could hit a bug getting a response from the ua app. The 
current code carefully checks if and what is returned, falling back to a safe 
default behavior.
  - Launching software properties could trigger a bug in the ua app.
  - Software properties could show incorrect information, causing confusion 

[Group.of.nepali.translators] [Bug 1930741] Re: 20apt-esm-hook.conf is missing semicolons at end of option

[Chad Smith]

** Changed in: ubuntu-advantage-tools (Ubuntu Groovy)
   Status: New => Won't Fix

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

Title:
  20apt-esm-hook.conf is missing semicolons at end of option

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Bionic:
  New
Status in ubuntu-advantage-tools source package in Focal:
  New
Status in ubuntu-advantage-tools source package in Groovy:
  Won't Fix
Status in ubuntu-advantage-tools source package in Hirsute:
  New
Status in ubuntu-advantage-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]

  This bug caused aptdaemon to miss two configuration options that
  ubuntu-advantage-tools relies on for updating its messaging based on
  apt state. Apt itself parsed the options despite the syntax mistake,
  which led to a difference in understanding between apt and aptdaemon.
  This difference caused autopkgtest failures.

  Further, because aptdaemon could not parse these two options, it may
  result in operations triggered through aptdaemon not properly updating
  ubuntu advantage esm messaging. This means ubuntu-advantage-tools may
  print confusing or out of date messages related to esm in some cases.

  The fix is to add the semicolons required in the apt config syntax
  that we missed. This fix allows aptdaemon to parse all of our config
  settings, and means apt and aptdaemon will have a shared understanding
  of the configuration again.

  [Test Plan]

  These test steps assume that the proposed version of ua to release is
  available in ppa:ua-client/staging - check with the ubuntu-advantage-
  tools team before proceeding to make sure this is the case.

  Start a container of an affected release (tested in xenial, but should work 
on any affected release). Inside the container:
  ```
  sudo apt update
  sudo apt install aptdaemon
  ```

  Now run the following python3 script
  ```
  from aptdaemon import config
  c = config.ConfigWriter()
  uataptconf = open("/etc/apt/apt.conf.d/20apt-esm-hook.conf")
  lines = uataptconf.readlines()
  print(c.parse(lines).keys())
  uataptconf.close()
  ```

  You should see output like the following:
  ```
  dict_keys(['apt::install::post-invoke-success', 
'apt::update::post-invoke-stats'])
  ```
  Note that the above only includes 2 out of the 4 intended config settings 
from our config file.

  Now install the fixed version:
  ```
  sudo add-apt-repository ppa:ua-client/staging
  sudo apt-get update
  sudo apt install ubuntu-advantage-tools
  ```

  And run the above python script again. You should see output like the 
following:
  ```
  dict_keys(['apt::install::pre-invoke', 'apt::install::post-invoke-success', 
'apt::update::post-invoke-stats', 'aptcli::hooks::upgrade'])
  ```

  Notice that it now finds all of the intended config settings.

  
  [Where problems could occur]

  The fix is adding two semicolons to the apt config file. The only
  problem that could occur is that, if a mistake was made, a similar apt
  config parsing problem could occur. Perhaps if this caused additional
  config parsing problems, then our message updating hooks would be
  broken in a different way from this bug. This would result in lack of,
  or out-of-date, messaging about esm packages from ubuntu-advantage-
  tools.

  [Other Info]
   
  A hotfix was already released to impish as 27.1.1 to stop the autopkgtest 
failures and unblock work that was interrupted by this bug. It successfully 
solved the issue.

  [Original Description]

  Recently aptdaemon started having autopkgtest failures with its
  tests.test_configparser.ConfigurationParserTestCase test. The failure
  follows:

  Test if credentials of repositories are store securely in a ... ok

  ==
  ERROR: test_ (tests.test_configparser.ConfigurationParserTestCase)
  --
  Traceback (most recent call last):
    File "/tmp/autopkgtest.cp3vHc/build.adU/src/tests/test_configparser.py", 
line 82, in test_
  config[key.lower()]]
  KeyError: 'apt::install::pre-invoke'

  --
  Ran 79 tests in 109.732s

  FAILED (errors=1, skipped=21)
  Test failed: 
  error: Test failed: 

  The "APT::Install::Pre-Invoke" key is provided by
  /etc/apt/apt.conf.d/20apt-esm-hook.conf which is from ubuntu-
  advantage-tools, so I'd guess this started happening when it moved to
  -updates (on 20210513). This would also explain why it is affecting
  every release.

To manage notifications about this bug go to:

[Group.of.nepali.translators] [Bug 1934902] Re: [SRU] ubuntu-advantage-tools (27.1 -> 27.2) Xenial, Bionic, Focal, Hirsute

[Chad Smith]

27.2~21.10.1 released to impish


** Changed in: ubuntu-advantage-tools (Ubuntu Impish)
   Status: New => Fix Released

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

Title:
   [SRU] ubuntu-advantage-tools (27.1 -> 27.2) Xenial, Bionic, Focal,
  Hirsute

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Bionic:
  New
Status in ubuntu-advantage-tools source package in Focal:
  New
Status in ubuntu-advantage-tools source package in Hirsute:
  New
Status in ubuntu-advantage-tools source package in Impish:
  Fix Released

Bug description:
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:

    * Schema of `ua status --format=json` has been updated to include more
  information and better organize the information already present.
    * `yaml` is now a format option for `ua status`
    * `http_proxy` and `https_proxy` configuration fields were added
    - When set, `ua` will use the specified proxy.
    - When set, `ua` will configure snap (if installed) and livepatch
  (if enabled) to use the specified proxy
    * `apt_http_proxy` and `apt_https_proxy` configuration fields were added
    - When set, `ua` will configure apt to use the specified proxy
    * `ua refresh` now accepts optional sub commands: `ua refresh contract`
  and `ua refresh config`. `ua refresh contract` does what `ua refresh`
  used to do. `ua refresh config` re-processes the uaclient config file.
  `ua refresh` with no sub command does the equivalent of `ua refresh
  config && ua refresh contract`.
    * `ua config set key=val` is a new command that edits a key in
  uaclient's config file.
    * `ua config unset key` is a new command that removes the value of a key
  uaclient's config file
    * `ua config show` is a new command that shows the current value of
  uaclient config options.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdates

  The ubuntu-advantage-tools team will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug.
  ubuntu-advantage-tools team members will not mark ‘verification-done’
  until this has happened.

  * Automated Test Results
  
  Attach or link the following automated integration test runs for 
ubuntu-advantage-tools on each affected LTS release:

  - lxd.container platform
  - lxd.kvm platform
  - AWS Ubuntu PRO
  - AWS Ubuntu cloud-images (non-Pro)
  - Azure Ubuntu PRO
  - Azure Ubuntu cloud-images (non-Pro)
  - GCP Ubuntu PRO
  - GCP Ubuntu cloud-images (non-Pro)
  

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  The changes most likely to produce an unexpected regression are the
  changes to the output of `ua status --format=json`. We had (and still
  have) a notice in the output that tools should _not_ rely on the
  structure of the output of this command; however, we know of at least
  one tool that does, and others may as well despite the warning. We
  have avoided changes that we know will break others, but it is
  possible that we broke some unknown integration.

  The behavior of `ua refresh` has slightly changed. It now processes
  the proxy configuration before refreshing the contract. Since the
  proxy configuration is also new with this release, it is unlikely that
  any existing use of `ua refresh` will start doing anything new, unless
  the user also adds the new proxy config fields.

  This update also changes the schema of some of our state that we keep
  in a json file. We're introducing a basic migration mechanism
  specifically to avoid anything breaking if the json file on disk is
  the old version. In the worst case if the migration script doesn't
  work, then running `ua status` with root privileges will overwrite the
  existing json file with the new version, which will resolve any
  problems.

  [Discussion]

  In this release, we're starting to lay the foundation for more proper
  schema versioning of `ua status` output. In the future when we need to
  change the output again, we plan to properly bump the schema version
  and implement a way to select the version the caller expects. At that
  time we will remove our warning from the output and start to guarantee
  version compatibility.

  [Changelog]

  

To manage notifications about this bug go to:

[Group.of.nepali.translators] [Bug 1911228] Re: enable-fips doesn't work on bionic

[Chad Smith]

** Changed in: ubuntu-advantage-tools (Ubuntu)
   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/1911228

Title:
  enable-fips doesn't work on bionic

Status in ubuntu-advantage-script:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released

Bug description:
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu 
  DISTRIB_RELEASE=18.04 
  DISTRIB_CODENAME=bionic 
  DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"

  $ sudo ua enable-fips TOKEN Sorry, but Canonical FIPS 140-2 Modules is not 
supported on bionic
  $ sudo ua enable-fips-updates TOKEN Sorry, but Canonical FIPS 140-2 Modules 
is not supported on bionic

  FIPS is supported on bionic now. Either the client should be able to
  enable it, or the tool should state that it isn't able to and point
  people to the correct instructions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1911228/+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 1855415] Re: cannot enable esm-infra for ubuntu 14, amd 64

[Chad Smith]

Just an update here while cleaning out stale bugs. 
  This fix for better error messaging has been released to Xenial 16.04 and 
more recent Ubuntu released with the publish of ubuntu-advantage-tools version 
27.0. The messaging fix will not make it into Trusty 14.04. As such I have 
added specific FixReleased bug items to mark it as fixed in newer Ubuntu.


** Also affects: ubuntu-advantage-tools (Ubuntu Impish)
   Importance: Undecided
   Status: Triaged

** Also affects: ubuntu-advantage-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-advantage-tools (Ubuntu Trusty)
   Status: New => Won't Fix

** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Hirsute)
   Status: New => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Impish)
   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/1855415

Title:
  cannot enable esm-infra for ubuntu 14, amd 64

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Won't Fix
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released
Status in ubuntu-advantage-tools source package in Focal:
  Fix Released
Status in ubuntu-advantage-tools source package in Groovy:
  Fix Released
Status in ubuntu-advantage-tools source package in Hirsute:
  Fix Released
Status in ubuntu-advantage-tools source package in Impish:
  Fix Released

Bug description:
  I have attached the machine using "sudo ua attach ###code".
  then the following happens:
  #command & output
  $ sudo ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cc-ealyes   n/a   Common Criteria EAL2 Provisioning Packages
  cis-audit no— Center for Internet Security Audit Tools
  esm-infra yes   disabled  UA Infra: Extended Security Maintenance
  fips  yes   n/a   NIST-certified FIPS modules
  fips-updates  yes   n/a   Uncertified security updates to FIPS modules
  livepatch yes   n/a   Canonical Livepatch service

  Enable services with: ua enable 

   Account: samratghosh9...@gmail.com
  Subscription: samratghosh9...@gmail.com

  When I am trying to enable esm-infra, I am getting;
  ~$ sudo ua enable esm-infra
  One moment, checking your subscription first
  Updating package lists
  Updating package lists
  APT update failed.

  I have tried
  $ sudo rm -vf /var/lib/apt/lists/* -vf
  $ sudo apt-get clean
  $ sudo apt-get update
  $ sudo ua enable esm-infra

  But no luck. Please help.

  $ lsb_release -rd
  Description:  Ubuntu 14.04.6 LTS
  Release:  14.04

  $ apt-cache policy ubuntu-advantage-tools
  ubuntu-advantage-tools:
    Installed: 19.6~ubuntu14.04.3
    Candidate: 19.6~ubuntu14.04.3
    Version table:
   *** 19.6~ubuntu14.04.3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1855415/+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 1911228] Re: enable-fips doesn't work on bionic

[Chad Smith]

This was fully resolved by an official SRU of the new ubuntu-advantage-
tools version 27.0 to Xenial and Bionic  on  2021-04-29.

The new UA client requires obtaining a contract token from
https://ubuntu.com/advantage and using that global contract token on the
commandline


   sudo ua attach 
   # to enable fips if not auto-enabled by your contract
   sudo ua enable fips


The security documentation referenced has been updated since the SRU to reflect 
these steps if needed.
https://security-certs.docs.ubuntu.com/en/fips#manual-installation

** Changed in: ubuntu-advantage-tools (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: ubuntu-advantage-tools (Ubuntu Bionic)
   Status: New => Fix Released

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

Title:
  enable-fips doesn't work on bionic

Status in ubuntu-advantage-script:
  Fix Released
Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Committed
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Bionic:
  Fix Released

Bug description:
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu 
  DISTRIB_RELEASE=18.04 
  DISTRIB_CODENAME=bionic 
  DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"

  $ sudo ua enable-fips TOKEN Sorry, but Canonical FIPS 140-2 Modules is not 
supported on bionic
  $ sudo ua enable-fips-updates TOKEN Sorry, but Canonical FIPS 140-2 Modules 
is not supported on bionic

  FIPS is supported on bionic now. Either the client should be able to
  enable it, or the tool should state that it isn't able to and point
  people to the correct instructions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1911228/+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 1926949] Re: FTBFS: apt can't resolve `dh-systemd | debhelper (>= 13.3)`

[Chad Smith]

** Also affects: ubuntu-advantage-tools (Ubuntu Impish)
   Importance: Low
 Assignee: Grant Orndorff (orndorffgrant)
   Status: Fix Committed

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

Title:
  FTBFS: apt can't resolve `dh-systemd | debhelper (>= 13.3)`

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Committed
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Bionic:
  New
Status in ubuntu-advantage-tools source package in Focal:
  New
Status in ubuntu-advantage-tools source package in Groovy:
  New
Status in ubuntu-advantage-tools source package in Hirsute:
  New
Status in ubuntu-advantage-tools source package in Impish:
  Fix Committed

Bug description:
  [Impact] 
  For sbuild users attempting to build this package locally results in pkg 
build failures due to inability of sbuild to handle the build deps alternatives 
when running:
   sbuild -s --source-only-changes

  [Test Plan]
  $ git ubuntu clone ubuntu-advantage-tools
  $ cd ubuntu-advantage-tools

  
  case ($release) in
hirsute)
resolve_alt="";;
xenial|bionic|focal|groovy)
resolve_alt="--resolve-alternatives;;
  esac

  $ sbuild -s --source-only-changes -d $release $resolve_alt


  [Where problems could occur]

   * Due to using the same d/control on all Ubuntu releases, simpler
  sbuild commandline will require use of `--resolve-alternatives`
  parameter on older releases where sbuild doesn't "seed" those build
  deps alternatives by default.

   * This should be low risk as PPAs ppa:ua-client/staging & ppa-
  uaclient/daily are building successfully with these Build-Depends and
  genereally sbuild allows for workarounds with using --resolve-
  alternatives.

  [Other Info]
   ...

  [Original Description]

  Hello,

  [Problem]
  =

  It looks like apt isn't able to resolve `dh-systemd | debhelper (>=
  13.3)`. Whilst the line in logical and makes sense, that is, use dh-
  systemd for Groovy and older releases (since it's not present in
  Hirsute and thereafter) and use debhelper (...) for newer releases, et
  al.

  However, apt is failing to resolve that for some reasons and it's thus
  results in FTBFS.

  [Logs]
  ==

  Install main build dependencies (apt-based resolver)
  

  Installing build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   sbuild-build-depends-main-dummy : Depends: dh-systemd but it is not 
installable
  E: Unable to correct problems, you have held broken packages.
  apt-get failed.
  E: Package installation failed
  Not removing build depends: cloned chroot in use

  [Reproducer]
  

  $ git ubuntu clone ubuntu-advantage-tools
  $ cd ubuntu-advantage-tools
  $ sbuild -s --source-only-changes

  and that should yield a failed build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926949/+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 1927886] Re: xenial powerpc build failures golang dependency issues

[Chad Smith]

** Also affects: ubuntu-advantage-tools (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => Fix Committed

** Also affects: ubuntu-advantage-tools (Ubuntu Impish)
   Importance: Undecided
   Status: Fix Committed

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

Title:
  xenial powerpc build failures golang dependency issues

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Committed
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Bionic:
  New
Status in ubuntu-advantage-tools source package in Focal:
  New
Status in ubuntu-advantage-tools source package in Groovy:
  New
Status in ubuntu-advantage-tools source package in Hirsute:
  New
Status in ubuntu-advantage-tools source package in Impish:
  Fix Committed

Bug description:
  ubuntu-advantage-tools 27.0~16.04.1 fails to build from source in PPAs
  or locally via sbuild on powerpc platform due to golang package
  dependency issues:

  $ sbuild --resolve-alternatives --dist=xenial --arch=powerpc --arch-all 
../out/ubuntu-advantage-tools_27.0~16.04.1.dsc
  

  Merged Build-Depends: bash-completion, debhelper (>= 9), debianutils, 
dh-python, dh-systemd | debhelper (>= 13.3), gettext, git, golang, 
libapt-pkg-dev, po-debconf, python3 (>= 3.4), distro-info, python3-flake8, 
python3-mock, python3-pytest, python3-setuptools, python3-yaml, 
build-essential, fakeroot
  Filtered Build-Depends: bash-completion, debhelper (>= 9), debianutils, 
dh-python, dh-systemd | debhelper (>= 13.3), gettext, git, golang, 
libapt-pkg-dev, po-debconf, python3 (>= 3.4), distro-info, python3-flake8, 
python3-mock, python3-pytest, python3-setuptools, python3-yaml, 
build-essential, fakeroot
  dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
'/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
  Ign:1 copy:/<>/apt_archive ./ InRelease
  Get:2 copy:/<>/apt_archive ./ Release [957 B]
  Ign:3 copy:/<>/apt_archive ./ Release.gpg
  Get:4 copy:/<>/apt_archive ./ Sources [481 B]
  Get:5 copy:/<>/apt_archive ./ Packages [565 B]
  Fetched 2003 B in 0s (9192 B/s)
  Reading package lists...
  Reading package lists...

  Install main build dependencies (apt-based resolver)
  

  Installing build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   sbuild-build-depends-main-dummy : Depends: golang but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.
  apt-get failed.
  E: Package installation failed

  ...
 missing:
   pkg:
package: golang:powerpc
version: 2:1.6-1ubuntu4
architecture: all
essential: false
unsat-dependency: golang-src:powerpc (>= 2:1.6-1ubuntu4)
   depchains:
-
 depchain:
  -
   package: sbuild-build-depends-main-dummy:powerpc
   version: 0.invalid.0
   architecture: powerpc
   essential: false
   depends: golang:powerpc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927886/+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 1926361] [NEW] sru ubuntu-advantage-tools (10ubuntu0.16.04.1 -> 27.0) Xenial, Bionic, Focal, Hirsute

[Chad Smith]

Public bug reported:

== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:

   * 

See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdate

The ubuntu-advantage-tools team will be in charge of attaching the artifacts and
console output of the appropriate run to the bug.  ubuntu-advantage-tools team
members will not mark ‘verification-done’ until this has happened.

* Automated Test Results

Attach or link the following automated integration test runs for 
ubuntu-advantage-tools on each affected LTS release:

- lxd.container platform
- lxd.kvm platform
- AWS Ubuntu PRO
- AWS Ubuntu cloud-images (non-Pro)

- Azure Ubuntu PRO
- Azure Ubuntu cloud-images (non-Pro)

- GCP Ubuntu PRO
- GCP Ubuntu cloud-images (non-Pro)


* Manual Test Results
If trusty targeted:

For all SRUs:



[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned integration tests are attached to this bug.

[Discussion]


== End SRU Template ==



** Affects: ubuntu-advantage-tools (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-advantage-tools (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: ubuntu-advantage-tools (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: ubuntu-advantage-tools (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: ubuntu-advantage-tools (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-advantage-tools (Ubuntu Hirsute)
   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/1926361

Title:
  sru ubuntu-advantage-tools (10ubuntu0.16.04.1 -> 27.0) Xenial, Bionic,
  Focal, Hirsute

Status in ubuntu-advantage-tools package in Ubuntu:
  New
Status in ubuntu-advantage-tools source package in Xenial:
  New
Status in ubuntu-advantage-tools source package in Bionic:
  New
Status in ubuntu-advantage-tools source package in Focal:
  New
Status in ubuntu-advantage-tools source package in Hirsute:
  New

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:

 * 

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/UbuntuAdvantageToolsUpdate

  The ubuntu-advantage-tools team will be in charge of attaching the artifacts 
and
  console output of the appropriate run to the bug.  ubuntu-advantage-tools team
  members will not mark ‘verification-done’ until this has happened.

  * Automated Test Results
  
  Attach or link the following automated integration test runs for 
ubuntu-advantage-tools on each affected LTS release:

  - lxd.container platform
  - lxd.kvm platform
  - AWS Ubuntu PRO
  - AWS Ubuntu cloud-images (non-Pro)

  - Azure Ubuntu PRO
  - Azure Ubuntu cloud-images (non-Pro)

  - GCP Ubuntu PRO
  - GCP Ubuntu cloud-images (non-Pro)
  

  * Manual Test Results
  If trusty targeted:
  
  For all SRUs:
  

  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  [Discussion]
  

  == End SRU Template ==

  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926361/+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 1905599] Re: sru cloud-init (20.3-2 to 20.4-0ubuntu1) Xenial, Bionic, Focal, and Groovy

[Chad Smith]

** Changed in: cloud-init (Ubuntu)
   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/1905599

Title:
  sru cloud-init (20.3-2 to 20.4-0ubuntu1) Xenial, Bionic, Focal, and
  Groovy

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released
Status in cloud-init source package in Groovy:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:

  - Explicit set IPV6_AUTOCONF and IPV6_FORCE_ACCEPT_RA on static6 (#634)
  [Eduardo Otubo]
  - get_interfaces: don't exclude Open vSwitch bridge/bond members (#608)
  [Lukas Märdian] (LP: #1898997)
  - stages: don't reset permissions of cloud-init.log every boot (#624)
  (LP: #1900837)
  - cc_mounts: correctly fallback to dd if fallocate fails (#585)
  (LP: #1897099)
  - ssh_util: handle non-default AuthorizedKeysFile config (#586)
  [Eduardo Otubo]
  - openstack: consider product_name as valid chassis tag (#580)
  [Adrian Vladu] (LP: #1895976)
  - net: add the ability to blacklist network interfaces based on driver
  during enumeration of physical network devices (#591) [Anh Vo]
  - Add vendor-data support to seedfrom parameter for NoCloud and OVF (#570)
  [Johann Queuniet]
  - Hetzner: Fix instance_id / SMBIOS serial comparison (#640)
  [Markus Schade]
  - Hetzner: initialize instance_id from system-serial-number (#630)
  [Markus Schade] (LP: #1885527)
  - Fix not sourcing default 50-cloud-init ENI file on Debian (#598)
  [WebSpider]
  - DataSourceAzure: write marker file after report ready in preprovisioning
  (#590) [Johnson Shi]
  - Azure parse_network_config uses fallback cfg when generate IMDS network
  cfg fails (#549) [Johnson Shi]
  - Add config modules for controlling IBM PowerVM RMC. (#584)
  [Aman306] (LP: #1895979)

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates

  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug. cloud-init team
  members will not mark ‘verification-done’ until this has happened.

  * Automated Test Results
  
  
  
  

  * Manual Test Results
  
  
  

  
  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  == End SRU Template ==

  == Changelog ==
  - cla: add xnox (#692) [Dimitri John Ledkov]
  - Collect logs from integration test runs (#675) [James Falcon]
  - Release 20.4 (#686) [James Falcon] (LP: #1905440)
  - tox: avoid tox testenv subsvars for xenial support (#684)
  - Ensure proper root permissions in integration tests (#664) [James 
Falcon]
  - LXD VM support in integration tests (#678) [James Falcon]
  - Integration test for fallocate falling back to dd (#681) [James Falcon]
  - .travis.yml: correctly integration test the built .deb (#683)
  - Ability to hot-attach NICs to preprovisioned VMs before reprovisioning
    (#613) [aswinrajamannar]
  - Support configuring SSH host certificates. (#660) [Jonathan Lung]
  - add integration test for LP: #1900837 (#679)
  - cc_resizefs on FreeBSD: Fix _can_skip_ufs_resize (#655)
    [Mina Galić] (LP: #1901958, #1901958)
  - DataSourceAzure: push dmesg log to KVP (#670) [Anh Vo]
  - Make mount in place for tests work (#667) [James Falcon]
  - integration_tests: restore emission of settings to log (#657)
  - DataSourceAzure: update password for defuser if exists (#671) [Anh Vo]
  - tox.ini: only select "ci" marked tests for CI runs (#677)
  - Azure helper: Increase Azure Endpoint HTTP retries (#619) [Johnson Shi]
  - DataSourceAzure: send failure signal on Azure datasource failure (#594)
    [Johnson Shi]
  - test_persistence: simplify VersionIsPoppedFromState (#674)
  - only run a subset of integration tests in CI (#672)
  - cli: add --system param to allow validating system user-data on a
    machine (#575)
  - test_persistence: add VersionIsPoppedFromState test (#673)
  - introduce an upgrade framework and related testing (#659)
  - add --no-tty option to gpg (#669) [Till Riedel] (LP: #1813396)
  - Pin pycloudlib to a working commit (#666) [James Falcon]
  - DataSourceOpenNebula: exclude SRANDOM from context output (#665)
  - cloud_tests: 

[Group.of.nepali.translators] [Bug 1910835] Re: Azure IMDS publicKeys contain \r\n which prevents ssh access to vms using cloud-generated ssh keys.

[Chad Smith]

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

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

Title:
  Azure IMDS publicKeys contain \r\n which prevents ssh access to vms
  using cloud-generated ssh keys.

Status in cloud-init:
  Confirmed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Bionic:
  Fix Committed
Status in cloud-init source package in Focal:
  Fix Committed
Status in cloud-init source package in Groovy:
  Fix Committed
Status in cloud-init source package in Hirsute:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  The previous version of cloud-init used OpenSSL to process the SSH keys 
provided by the Azure platform.  cloud-init 20.4 replaced that code with a more 
efficient implementation, but one which did not use OpenSSL: this meant that 
users passing certificates to instances, or users generating SSH keys in 
Azure's web UI (which inserts \r\n sequences into the public key content), were 
regressed: their certificates and malformed SSH keys were no longer handled, so 
they could fail to gain access to newly-launched instances.

  This release is only a single functional cherry-pick which solely
  affects Azure platform. It is a critical bug we wish to release as
  soon as possible

    * Azure: cherry-pick 4f62ae8d: Fix regression with handling of IMDS ssh keys
  (#760) (LP: #1910835)

  The functional changeset here introduces a raise KeyError exception
  which forces cloud-init to revert to previous released logic of the
  previous cloud-init public release 20.3.

  [Test Case]

  As this is a single commit backport, the cloud-init SRU exception need
  not apply.  An upstream integration test has been written for this
  issue (https://github.com/canonical/cloud-
  init/blob/master/tests/integration_tests/bugs/test_lp1910835.py).

  A full run of the upstream test suite on Azure will therefore
  regression test the update generally and test this issue specifically:
  a log of a test run for each suite will be attached.

  [Regression Potential]

  The proposed change only modifies code paths used on Azure,
  specifically to revert to a previous behaviour: users unaffected by
  the bug should see no change (their keys will get to their instance
  via a different route), and users affected by the bug would have been
  unable to access their instances before (so cannot be relying on this
  behaviour in a way which we could break by fixing it).

  [Discussion]
  This should only affect public Azure VM launched which use Azure to 
--generate-ssh-keys either from the dashboard or from the `az cli`

  Any other cloud-platform is not affected by this change.

  == End SRU Template ==

    * cherry-pick 4f62ae8d: Fix regression with handling of IMDS ssh keys
  (#760) (LP: #1910835)

  == Original Description ==

  cloud-init 20.4 or later will incorrectly add Azure publicKeys to
  .ssh/authorized_keys preventing ssh access for cloud-generated keys.

  To reproduce: launch an ubuntu VM from the portal.azure.com  choosing
  to generate new ssh key.

  When the instance is launched you can see that the ssh-rsa content
  provided in the metadata publicKeys value  contains CRLF characters
  (\r\n) thus splitting the content of the pubkey onto multiple lines
  when it is rendered into .ssh/authorized_keys.

  the solution is either for IMDS to stop adding the CRLF characters or
  cloud-init to strip them out.

  Here is the IMDS value provided to cloud-init

  cloud-init query --format '{{ds.meta_data.imds.compute.publicKeys}}'

  [{'keyData': 'ssh-rsa
  
B3NzaC1yc2EDAQABAAABgQCllNnyHXFWlMb9EKD9LZrOxt1d\r\nk/QxYwQ0HYEP8n6TUWoUsN3mv/Qk/qWH76Pa6f33hefzTFRiom7Ls/tJMcr/ki8R\r\n9FqyYOu0xxHmpXTUWFoZQCZtGRMtvDl/s76Wr1sCsE/ez+EcAPeGGm/B7jHtDAUW\r\nlkINfuPVBDfRtSfmnlCKS+sIf1XOqvRASGWi05zAW921T4OkiattyXyhaOimJOwq\r\n4jAXmydwtNCN2iGGKWS8YeXbtgveReqZVVKtcDKevgWdNyqZa69uq9tRujobjCh7\r\n6xxCkQcdCLospgqX79GBbdRys6mVxVgc349RIWjQwglRQpJwNzkeOG5Q+La2MEhu\r\niKqKJMvYVhil3khzMuZwzmTrGbRx0E8AS+Cm064RBgbcdjCW8dDYGLuk2eQ2v9Ht\r\n6eERfxMBNg3udv1jmiKpjjHIg99HDU4VqhL3aHmg+TSrxByd0cAgFBV+H0CiUVC9\r\nS2mLJ6Peu/HDwd88E8Wqiv3eAsjcaCRH3QiQVaU=
  generated-by-azure\r\n', 'path': '/home/ubuntu/.ssh/authorized_keys'}]

  cloud-init  renders this directly to .ssh/authorized_keys without
  processing the string, resulting in an invalid keyline:

  ssh-rsa B3NzaC1yc2EDAQABAAABgQCllNnyHXFWlMb9EKD9LZrOxt1d 
k/QxYwQ0HYEP8n6TUWoUsN3mv/Qk/qWH76Pa6f33hefzTFRiom7Ls/tJMcr/ki8R^M
  9FqyYOu0xxHmpXTUWFoZQCZtGRMtvDl/s76Wr1sCsE/ez+EcAPeGGm/B7jHtDAUW^M
  lkINfuPVBDfRtSfmnlCKS+sIf1XOqvRASGWi05zAW921T4OkiattyXyhaOimJOwq^M
  4jAXmydwtNCN2iGGKWS8YeXbtgveReqZVVKtcDKevgWdNyqZa69uq9tRujobjCh7^M
  

[Group.of.nepali.translators] [Bug 1893064] Re: sru cloud-init (20.2-45 to 20.3-2) Xenial, Bionic, and Focal

[Chad Smith]

** Changed in: cloud-init (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: cloud-init (Ubuntu)
   Status: Won't Fix => Fix Committed

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

Title:
  sru cloud-init (20.2-45 to 20.3-2) Xenial, Bionic, and Focal

Status in cloud-init package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:

   Packaging:
  - Xenial/Bionic/Focal:
     * d/cloud-init.postinst: fix the grub install device for NVMe-rooted
  instances on upgrade.  (LP: #1889555)
  - Xenial-only:
  * d/control: add python3-pytest-catchlog to Build-Depends

   General:
  - query: do not handle non-decodable non-gzipped content (#543)
  - Update the list of valid ssh keys. (#487)
    [Ole-Martin Bratteng] (LP: #1877869)
  - cmd: cloud-init query to handle compressed userdata (#516) (LP: 
#1889938)
  - cli: add devel make-mime subcommand (#518)
  - user-data: only verify mime-types for TYPE_NEEDED and x-shellscript
    (#511) (LP: #122)
  - Recognize LABEL_FATBOOT labels (#513) [James Falcon] (LP: #1841466)
  - cc_ca_certs.py: fix blank line problem when removing CAs and adding
    new one (#483) [dermotbradley]
  - networking: refactor wait_for_physdevs from cloudinit.net (#466)
    (LP: #1884626)
  - cc_mounts: handle missing fstab (#484) (LP: #1886531)
  - networking: refactor is_physical from cloudinit.net (#457) (LP: 
#1884619)
  - Add schema for cc_chef module (#375) [lucasmoura] (LP: #185)
  - cc_final_message: don't create directories when writing boot-finished
    (#445) (LP: #1883903)
  - util: add ensure_dir_exists parameter to write_file (#443)
  - Default to UTF-8 in /var/log/cloud-init.log (#427) [James Falcon]
  - Fixes KeyError for bridge with no "parameters:" setting (#423)
    [Brian Candler] (LP: #1879673)
  - cc_grub_dpkg: determine idevs in more robust manner with grub-probe
    (#358) [Matthew Ruffell] (LP: #1877491)
  - Enable chef_license support for chef infra client (#389) [Bipin Bachhao]
  - Add schema to apt configure config (#357) [lucasmoura] (LP: #1858884)
  - cc_locale: introduce schema (#335)

  Clouds:
  - Azure: Add netplan driver filter when using hv_netvsc driver (#539)
    [James Falcon] (LP: #1830740)
  - Azure: Pushing cloud-init log to the KVP (#529) [Moustafa Moustafa]
  - Refactor Azure report ready code (#468) [Johnson Shi]
  - azure: disable bouncing hostname when setting hostname fails (#494)
    [Anh Vo]
  - analyze/dump: add support for Amazon Linux 2 log lines (#346)
    (LP: #1876323)
  - Enhance poll imds logging (#365) [Moustafa Moustafa]
  - DataSourceAzure: Use ValueError when JSONDecodeError is not available
    (#490) [Anh Vo]
  - DataSourceEc2: use metadata's NIC ordering to determine route-metrics
    (#342) (LP: #1876312)
  - Disable ec2 mirror for non aws instances (#390)
    [lucasmoura] (LP: #1456277)
  - Hetzner: support reading user-data that is base64 encoded. (#448)
    [Scott Moser] (LP: #1884071)
  - DataSourceOracle: retry twice (and document why we retry at all) (#536)
  - DataSourceOracle: refactor to use only OPC v1 endpoint (#493)
  - Support Oracle IMDSv2 API (#528) [James Falcon]
  - VMware: Support parsing DEFAULT-RUN-POST-CUST-SCRIPT (#441)
    [xiaofengw-vmware]
  - When tools.conf does not exist, running cmd "vmware-toolbox-cmd
    config get deployPkg enable-custom-scripts", the return code will
    be EX_UNAVAILABLE(69), on this condition, it should not take it as
    error. (#413) [chengcheng-chcheng]

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates

  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  == End SRU Template ==

  == Changelog ==
  - Release 20.3 (#547) [James Falcon] (LP: #1892878)
  - tox: bump the pylint version to 2.6.0 in the default run (#544)
    

[Group.of.nepali.translators] [Bug 1630274] Re: mount-image-callback may not mount overlay when it could

[Chad Smith]

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

** Changed in: cloud-utils (Ubuntu Xenial)
   Status: New => In Progress

** Description changed:

+ === Begin SRU Template ===
+ [Impact]
+ The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
+ the 'overlay' filesystem via name 'overlayfs'.  This broke overlayroot as
+ it explicitly tried to to use 'overlayfs' by name in loading of modules and
+ also in entry in /etc/fstab.
+ 
+ Without this fix, overlayroot will simply not work on any upstream kernel
+ or Ubuntu kernel of 16.10 (yakkety) or later.
+ 
+ [Test Case]
+ Note, not applying proposed as shown in step 3 below will recreate failure.
+ 
+ 1.) Start an instance of a cloud image.
+ 
+ 2.) get a suitable 4.8 kernel
+ On 16.10 or later, this is already done.  On 16.04, we currently need to
+ install the kernel team's PPA to get one.
+ 
+ $ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
+ $ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge 
http://archive.ubuntu.com/ubuntu $rel-proposed main" |
+ $ sudo tee /etc/apt/sources.list.d/proposed.list
+ $ sudo apt update -qy && sudo apt install -qy overlayroot http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/overlayroot/scripts/init-bottom/overlayroot
+ [2] 
http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/revision/115
+ 
+ === End SRU Template ===
+ 
+ 
+ === Original Description ===
+ As mentioned in LP: #1411294, it's now called 'overlay' instead of 
'overlayfs'.
+ Ubuntu had patched the kernel for compatibility.
+ 
+ The Ubuntu kernels as of 4.8 (16.10 kernel) and possibly a bit before no
+ longer have a overlayfs module either.  Thus, this is now affecting
+ yakkety.
+ 
+ (The original reporter is @~gpo-9.)
+ 
  The changes recently added to mount-image-callback under bug 1493188
  that were targeted at supporting 'overlay' filesystem type while still
  supporting 'overlayfs' may result in exiting with "unsupported" when a
  mount would work.
  
  The changes basically said:
    if overlay in /proc/filesystems:
   return GOOD
    modprobe --quiet --use-blacklist overlay
   if overlay in /proc/filesystems:
  return GOOD
    return BAD
  
  the path that fails now that previously succeeded is when 'modprobe'
  would not work, but 'mount -t overlay' *would*.  This occurs in build
  systems where the running kernel is of one version and code is running
  in a chroot that does not have access to the kernel modules in
  /lib/modules/.
  
  'mount -t overlay' works in this scenario because the mount abi call passes 
the filesystem type 'overlay', and the kernel then does:
     fs/filesystems.c:   if (!fs && (request_module("fs-%.*s", len, name) 
== 0))
  
  The kernel's scope is not chrooted, so the module gets loaded and
  everything is happy.
  
  The new changes are to instead basically do:
-   for fstype in overlay overlayfs; do
-  mount -t $fstype  && return GOOD
-  if /proc/filesystems is readable and $fstype in /proc/filesystems; then
-  return FAIL
-  fi
-   done
+   for fstype in overlay overlayfs; do
+  mount -t $fstype  && return GOOD
+  if /proc/filesystems is readable and $fstype in /proc/filesystems; then
+  return FAIL
+  fi
+   done

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

Title:
  mount-image-callback may not mount overlay when it could

Status in cloud-utils:
  Fix Released
Status in cloud-utils package in Ubuntu:
  Fix Released
Status in cloud-utils source package in Xenial:
  In Progress

Bug description:
  === Begin SRU Template ===
  [Impact]
  The 16.10 kernel dropped a legacy kernel module alias that allowed usage of
  the 'overlay' filesystem via name 'overlayfs'.  This broke overlayroot as
  it explicitly tried to to use 'overlayfs' by name in loading of modules and
  also in entry in /etc/fstab.

  Without this fix, overlayroot will simply not work on any upstream kernel
  or Ubuntu kernel of 16.10 (yakkety) or later.

  [Test Case]
  Note, not applying proposed as shown in step 3 below will recreate failure.

  1.) Start an instance of a cloud image.

  2.) get a suitable 4.8 kernel
  On 16.10 or later, this is already done.  On 16.04, we currently need to
  install the kernel team's PPA to get one.

  $ sudo apt-add-repository -y ppa:canonical-kernel-team/ppa
  $ sudo apt update -q && sudo apt install -y linux-virtual-hwe-16.04-edge 
http://archive.ubuntu.com/ubuntu $rel-proposed main" |
  $ sudo tee /etc/apt/sources.list.d/proposed.list
  $ sudo apt update -qy && sudo apt install -qy overlayroot 

[Group.of.nepali.translators] [Bug 1893717] Re: Add Ubuntu Advantage service apt urls to valid mirrors

[Chad Smith]

** Changed in: ubuntu-release-upgrader (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
   Status: New => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
 Assignee: (unassigned) => Chad Smith (chad.smith)

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

Title:
  Add Ubuntu Advantage service apt urls to valid mirrors

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  New
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in ubuntu-release-upgrader source package in Focal:
  In Progress
Status in ubuntu-release-upgrader source package in Groovy:
  Fix Released

Bug description:
  Ensure Apt mirror urls supported by Ubuntu Advantage services are
  included as valid mirrors instead of being treated as third party
  repositories and getting disabled by do-release-upgrade.

  
  The following APT mirror urls are supported for current and/or imminent 
Ubuntu Advantage apt-based services on Xenial and later:

  
  https://esm.ubuntu.com/ubuntu/
  https://esm.ubuntu.com/apps/ubuntu/
  https://esm.ubuntu.com/cc/ubuntu/
  https://esm.ubuntu.com/infra/ubuntu/
  https://esm.ubuntu.com/fips/ubuntu/
  https://esm.ubuntu.com/fips-updates/ubuntu/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1893717/+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 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)

[Chad Smith]

### Eoan esm-apps * esm-infra verification on stock Eoan cloudimages
# This test will show no regression in unattended-upgrades because there are no 
ESM offerings
# on Eoan.


test script:
#!/bin/bash

if [ $# != 1 ]; then
 echo "usage: $0 "
 exit 1
fi
SERIES=$1
LXC_NAME=test-sru-$SERIES
echo 1. Launch ubuntu-daily $SERIES lxc
#lxc launch ubuntu-daily:$SERIES $LXC_NAME
echo 2. Run unattended-upgrades to confirm Allowed origins does not find esm 
packages
lxc exec $LXC_NAME -- unattended-upgrades --dry-run --verbose  2>&1 | egrep -i 
'Allowed|esm'
echo 3. Install unattended-upgrades from -proposed suites
cat > setup_proposed.sh &1 | grep unattended-upgrades
echo 5.Run unattended-upgrades to confirm -proposed Allowed origins does cause 
regressions
lxc exec $LXC_NAME -- unattended-upgrades --dry-run --verbose 2>&1


### Verification output

$ ./sru.sh eoan
1. Launch ubuntu-daily eoan lxc
2. Run unattended-upgrades to confirm Allowed origins does not find esm packages
Allowed origins are: o=Ubuntu,a=eoan, o=Ubuntu,a=eoan-security, 
o=UbuntuESM,a=eoan, o=UbuntuESM,a=eoan-security, o=UbuntuESM,a=eoan-security
3. Install unattended-upgrades from -proposed suites
  unattended-upgrades
Get:1 http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 
unattended-upgrades all 1.14ubuntu1.2 [47.6 kB]
Preparing to unpack .../unattended-upgrades_1.14ubuntu1.2_all.deb ...
Unpacking unattended-upgrades (1.14ubuntu1.2) over (1.14ubuntu1.1) ...
Setting up unattended-upgrades (1.14ubuntu1.2) ...
Replacing config file /etc/apt/apt.conf.d/50unattended-upgrades with new version
5.Run unattended-upgrades to confirm -proposed Allowed origins does cause 
regressions
Initial blacklist : 
Initial whitelist: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=eoan, o=Ubuntu,a=eoan-security, 
o=UbuntuESMApps,a=eoan-apps-security, o=UbuntuESM,a=eoan-infra-security, 
o=UbuntuESM,a=eoan-security
No packages found that can be upgraded unattended and no pending auto-removals
csmith@uptown:~/src/ubuntu-advantage-client$ echo $?
0


** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

** Changed in: unattended-upgrades (Ubuntu Trusty)
   Status: In Progress => Won't Fix

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

Title:
  Please add ${distro_id}ESM:${distro_codename}-infra-security  and
  ${distro_id}ESMApps:${distro_codename}-apps-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * Changes to the ESM repo naming and the introduction of the new esm-infra 
and esm-apps suites require an update to unattended-upgrades to ensure the 
security pockets are used.
   * This change will ensure users are actually receiving updates, where as 
today they will not without making manual changes.

  [Test Case]

   * 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
   * 2) Trusty ESM

  [Regression Potential]

   * This change is ensuring users actually receive security updates when using 
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty 
will be the only users affected.
   * The possible issue would be if/when users receive actual security updates 
that then regress or cause issues to the system.

  [Other Info]
   
  Previous description:

  ESM -infra-security and -apps-security will need to
  participate in unattended upgrades.

  Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}ESM:${distro_codename}";
  }

  Given that there have been ESM apt pocket renames over the last few
  months, the above ESM allowed-origin should not apply anymore and can
  be dropped or replaced.

  See RT #C122697 and #C121067 for the pocket/suite renames related to
  ESM

  What is needed after the ESM apt pocket/suite renames:

  Support for unattended upgrades for ESM for Infrastructure customers:

  Unattended-Upgrade::Allowed-Origins {
    // Extended Security Maintenance; doesn't necessarily exist for
    // every release and this system may not have it installed, but if
    // available, the policy for updates is such that unattended-upgrades
    // should also install from here by default.
    

[Group.of.nepali.translators] [Bug 1861452] Re: sru curtin 2020-01-30 - 19.3-17-g50ffca46-0ubuntu1

[Chad Smith]

dropping upstream project curtin task from this SRU process bug as
typically we only target it to the ubuntu series tasks.

** No longer affects: curtin

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

Title:
  sru curtin 2020-01-30 - 19.3-17-g50ffca46-0ubuntu1

Status in curtin package in Ubuntu:
  Confirmed
Status in curtin source package in Xenial:
  Fix Committed
Status in curtin source package in Bionic:
  Fix Committed
Status in curtin source package in Eoan:
  Fix Committed

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these improvements.
  The notable ones are:

- multipath removal handling
- centos8 support
- curthooks update initramfs only once for faster deployment
- block schema updates for raid, vtoc and ptable
- vmtest arch support for ppc64le and aarch64

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CurtinUpdates

  Curtin now contains an extensive integration test suite that is ran using
  the SRU package for each releases. These suite has documentation here:
  https://curtin.readthedocs.io/en/latest/topics/integration-testing.html

  In order to avoid regression to existing MAAS product, the MAAS team will
  run their continuous integration test against the curtin that is in
  -proposed.  A successful run will be required before the proposed curtin
  can be let into -updates.

  The curtin team will be in charge of attaching the artifacts and console
  output of the appropriate run to the bug.  Curtin team members will not
  mark ‘verification-done’ until this has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  
  

  [Discussion]
  

  == End SRU Template ==

  == changelog ==

  - clear-holders: ensure we wipe device even if multipath enabled not not 
mp
  - block_meta: use reliable fs_spec entries for block devices (LP: 
#1851899)
  - multipath: handle removal of multipath partitions correctly
(LP: #1857042)
  - vmtests: skip Focal deploying Centos70 ScsiBasic
  - vmtests: fix network mtu tests, separating ifupdown vs networkd
  - doc: Fix kexec documentation bug. [Mike Pontillo]
  - vmtests: Add Focal Fossa
  - centos: Add centos/rhel 8 support, enable UEFI Secure Boot
[Lee Trager] (LP: #1788088)
  - Bump XFS /boot skip-by date out a while
  - vmtest: Fix a missing unset of OUTPUT_FSTAB
  - curthooks: handle s390x/aarch64 kernel install hooks (LP: #1856038)
  - clear-holders: handle arbitrary order of devices to clear
  - curthooks: only run update-initramfs in target once (LP: #1842264)
  - test_network_mtu: bump fixby date for MTU tests
  - block-discover: don't skip partitions on virtual devices (LP: #1853018)
  - block-discover: handle partial probe data (LP: #1852351)
  - Fix parsing of squashfs: uri prefix for installation sources
[Daniel Fox] (LP: #1851271)
  - Release 19.3 (LP: #1851390)
  - Update HACKING.rst with Josh Powers contact info.
  - t/jenkins-runner: replace $EPOCHSECONDS with 'date +%s' [Paride 
Legovini]
  - curthooks: skip setup_kernel_img_conf on eoan and newer (LP: #1847257)
  - block_meta: use lookup for wwn, fix fallback from wwn, serial, path
(LP: #1849322)
  - vmtest: Adjust TestScsiBasic to use dnames to find correct disk
  - schema: Add ptable value 'unsupported' (LP: #1848535)
  - tools/xkvm: add -nographic to speed up devopt query
  - test_block_dasd: fix random_device_id to only generate valid IDs
(LP: #1849549)
  - vmtest: update skip_if_arch message
  - Add skip_by_date to eoan ipv6 vlan test
  - storage_config: interpret value, not presence, of
DM_MULTIPATH_DEVICE_PATH [Michael Hudson-Doyle]
  - vmtest: Add skip_by_date for test_ip_output on eoan + vlans
  - block-schema: update raid schema for preserve and metadata
  - dasd: update partition table value to 'vtoc' (LP: #1847073)
  - clear-holders: increase the level for devices with holders by one
(LP: #1844543)
  - tests: mock timestamp used in collect-log file creation (LP: #1847138)
  - ChrootableTarget: mount /run to resolve lvm/mdadm issues which
require it.
  - block-discover: handle multipath disks (LP: #1839915)
  - Handle partial raid on partitions (LP: #1835091)
  - install: export zpools if present in the storage-config (LP: #1838278)
  - block-schema: allow 'mac' as partition table type (LP: #1845611)
  - 

[Group.of.nepali.translators] [Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS

[Chad Smith]

This bug is believed to be fixed in cloud-init in version 19.2-55. If
this is still a problem for you, please make a comment and set the state
back to New

Thank you.

** Changed in: cloud-init
   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/1846535

Title:
  cloud-init 19.2.36 fails with python exception "Not all expected
  physical devices present ..."  during bionic image deployment from
  MAAS

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Disco:
  Fix Released
Status in cloud-init source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  Any instances launched with bridges or bonds in their network
  configuration will fail to bring up networking.

  [Test Case]
  # Juju bootstrap on maas of a machine sets up a network bridge that triggers 
a failure in cloud-init init stage.
  # This results in a maas machine deployment failure and the machine gets 
released

  Procedure:

  # Alternate steps on a maas machine with a bridge already created
  A1. confirm a bridge interface is configured for the target machine on 
interface eno1, name it broam, attach it to a subnet and select auto-assign for 
IP
  A2. click deploy -> bionic
  A3. Once manual deployment fails go to step  2 below

  # Alternative 2 juju bootstrap failure on maas
  B1: juju bootrap mymaas --no-gui
  B2: Once bootstrap fails go to step 2

  2. After deployment failure and machine is powered off click on the 
failed/released node in the MAAS UI
  3. Click Rescue Mode from the 'Take Action' drop down in the MAAS UI
  4. Grab the IP from the interfaces tab
  5. ssh ubuntu@ -- cloud-init status --long
  # Expect failure message
  6. Click Exit Rescue Mode on the node in MAAS UI.

  7. ssh to the maas server add the following lines to
  /etc/maas/preseeds/curtin_userdata to test official *-proposed
  packages:

  system_upgrade: {enabled: True}
  apt:
    sources:
  proposed.list:
     source: deb $MIRROR $RELEASE-proposed main universe   # upstream 
-proposed

  8. Repeat step 1 and expect bootstrap success
  # expect to see MAASDatasource from bootstrapped machine and no errors
  9. juju ssh 0 -- cloud-init status --long

  Additional verification checks to avoid regression
   - DONE oracle
   - DONE ec2
   - DONE openstack
   - DONE gce
   - DONE azure
   - DONE nocloud kvm
   - DONE nocloud lxd

  [Regression Potential]

  The change being SRU'd adds more conditions to an existing
  conditional.  There is potential to regress the cases that the
  existing conditional was introduced to cover, so we will be testing
  those specifically.  Other than that, there was some minor refactoring
  of the existing conditional statement (which did not change the logic
  it checks), which could cause issues for Oracle netfailover
  interfaces.  We will also specifically test on Oracle.

  [Original Report]

  Symptoms
  

  After deployment of Ubuntu Bionic image on MAAS provider (deploying to
  a bare metal server) juju cannot access any deployed machine due to
  missing SSH keys and machines are stuck in pending state:

  $ juju ssh 0
  ERROR retrieving SSH host keys for "0": keys not found

  $ juju machines
  Machine  StateDNSInst id  Series  AZ   Message
  0pending  172.20.10.125  block-3  bionic  AZ3  Deployed
  1pending  172.20.10.124  block-2  bionic  AZ2  Deployed
  2pending  172.20.10.126  block-1  bionic  AZ1  Deployed
  3pending  172.20.10.127  object-2 bionic  AZ1  Deployed
  4pending  172.20.10.128  object-1 bionic  AZ2  Deployed
  5pending  172.20.10.129  object-3 bionic  AZ3  Deployed

  It worth mentioning that pods can be successfully deployed with MAAS,
  only bare metal deployment fails.

  We checked different bionic images: cloud-init 19.2.24 works, and
  cloud-init 19.2.36 doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1846535/+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 1823376] Re: Please add ${distro_id}ESM:${distro_codename}-security to allowed origins (on Ubuntu)

[Chad Smith]

This bug was fixed (and seems available in Eoan and Focal) but this
feature Unattended upgrades setting was not backported to trusty, xenial
or bionic. Please consider this backport to support ESM
-security origins on trusty, xenial and bionic.

** Also affects: unattended-upgrades (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Trusty)
   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/1823376

Title:
  Please add ${distro_id}ESM:${distro_codename}-security to allowed
  origins (on Ubuntu)

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  New
Status in unattended-upgrades source package in Xenial:
  New
Status in unattended-upgrades source package in Bionic:
  New

Bug description:
  .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823376/+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 1842510] [NEW] Xenial: Enable IBMCloud in default datasource_list template

[Chad Smith]

Public bug reported:

IBMCloud support is currently expected to be run on Xenial  due to extra
configuration written to
/etc/cloud/cloud.cfg.d/99_networklayer_common.cfg

...
datasource_list: [ IBMCloud ]


Cloud-init packaging templates should also add IBMCloud to the default package 
list of discoverable datasources with a commit like

 
https://git.launchpad.net/cloud-init/commit/?id=abe6bcdfacdf2f6745e3acf5c76b332380b9c493
or 

 https://git.launchpad.net/cloud-
init/commit/?id=a3ccba259e862145dfa51322d33f5d321d9298b4

** Affects: cloud-init (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: cloud-init (Ubuntu Xenial)
 Importance: Undecided
 Status: Confirmed

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

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

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

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

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

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

Title:
  Xenial: Enable IBMCloud in default datasource_list template

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

Bug description:
  IBMCloud support is currently expected to be run on Xenial  due to
  extra configuration written to
  /etc/cloud/cloud.cfg.d/99_networklayer_common.cfg

  ...
  datasource_list: [ IBMCloud ]

  
  Cloud-init packaging templates should also add IBMCloud to the default 
package list of discoverable datasources with a commit like

   
https://git.launchpad.net/cloud-init/commit/?id=abe6bcdfacdf2f6745e3acf5c76b332380b9c493
  or 

   https://git.launchpad.net/cloud-
  init/commit/?id=a3ccba259e862145dfa51322d33f5d321d9298b4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1842510/+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 1841099] [NEW] SRU cloud-init (19.1.1 to 19.2.21): Xenial, Bionic, and Disco

[Chad Smith]

Public bug reported:

== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:

- ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA
- DataSourceOracle: prefer DS network config over initramfs
- Azure: Record boot timestamps, system information, and diagnostic events
  [Anh Vo]
- DataSourceOracle: configure secondary NICs on Virtual Machines
- azure/net: generate_fallback_nic emits network v2 config instead of v1
- Add support for publishing host keys to GCE guest attributes
  [Rick Wright]
- New data source for the Exoscale.com cloud platform [Chris Glass]
- net/cmdline: split interfaces_by_mac and init network config
  determination
- stages: allow data sources to override network config source order
- Fix bug rendering MTU on bond or vlan when input was netplan.
  [Scott Moser]
- net: add rfc3442 (classless static routes) to EphemeralDHCP
- templates/ntp.conf.debian.tmpl: fix missing newline for pools
- Add a cdrom size checker for OVF ds to ds-identify [Pengpeng Sun]
- VMWare: Trigger the post customization script via cc_scripts module.
  [Xiaofeng Wang]
- Cloud-init analyze module: Added ability to analyze boot events.
  [Sam Gilson]
- Update debian eni network configuration location, retain Ubuntu setting
  [Janos Lenart]
- net: skip bond interfaces in get_interfaces [Stanislav Makar]
- Add missing dsname for Hetzner Cloud datasource [Markus Schade]
- azure: add region and AZ properties from imds compute location metadata
- Allow identification of OpenStack by Asset Tag [Mark T. Voelker]
- netplan: update netplan key mappings for gratuitous-arp


See the changelog entry below for a full list of changes and bugs.

[Test Case]
The following development and SRU process was followed:
https://wiki.ubuntu.com/CloudinitUpdates

The cloud-init team will be in charge of attaching the artifacts and
console output of the appropriate run to the bug. cloud-init team
members will not mark ‘verification-done’ until this has happened.

* Automated Test Results
TODO: attach automated cloud-init-proposed test artifacts

TODO: attach automated cloud-init-proposed test artifacts from tests for
each release with kvm artifacts

TODO: attach Solutions Testing team test results for each LTS


TODO: attach MAAS Team test results for each LTS
sru-artifact-maas-xenial

* Manual Test Results
TODO: attach manual cloud-init-proposed test artifacts from tests for each 
release on ec2 datasource

TODO: attach manual cloud-init-proposed test artifacts from tests for
each release on gce datasource

TODO: attach manual cloud-init-proposed test artifacts from tests for
each release on azure datasource


[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned integration tests are attached to this bug.

[Discussion]

== End SRU Template ==

== Changelog ==
   - ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA
- Add missing #cloud-config comment on first example in documentation.
  [Florian Müller]
- ubuntu-drivers: emit latelink=true debconf to accept nvidia eula
- DataSourceOracle: prefer DS network config over initramfs
- format.rst: add text/jinja2 to list of content types (+ cleanups)
- Add GitHub pull request template to point people at hacking doc
- cloudinit/distros/parsers/sys_conf: add docstring to SysConf
- pyflakes: remove unused variable [Joshua Powers]
- Azure: Record boot timestamps, system information, and diagnostic events
  [Anh Vo]
- DataSourceOracle: configure secondary NICs on Virtual Machines
- distros: fix confusing variable names
- azure/net: generate_fallback_nic emits network v2 config instead of v1
- Add support for publishing host keys to GCE guest attributes
  [Rick Wright]
- New data source for the Exoscale.com cloud platform [Chris Glass]
- doc: remove intersphinx extension
- cc_set_passwords: rewrite documentation
- net/cmdline: split interfaces_by_mac and init network config
  determination
- stages: allow data sources to override network config source order
- cloud_tests: updates and fixes
- Fix bug rendering MTU on bond or vlan when input was netplan.
  [Scott Moser]
- net: update net sequence, include wait on netdevs, opensuse netrules path
- Release 19.2
- net: add rfc3442 (classless static routes) to EphemeralDHCP
- templates/ntp.conf.debian.tmpl: fix missing newline for pools
- Support netplan renderer in Arch Linux [Conrad Hoffmann]
- Fix typo in publicly viewable documentation. [David Medberry]
- Add a cdrom size checker for OVF ds to ds-identify [Pengpeng Sun]
- VMWare: Trigger the post customization script via cc_scripts module.
  

[Group.of.nepali.translators] [Bug 1799779] Re: LXD module installs the wrong ZFS package if it's missing

[Chad Smith]

This bug is believed to be fixed in cloud-init in version 19.1. If this
is still a problem for you, please make a comment and set the state back
to New

Thank you.

** Changed in: cloud-init
   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/1799779

Title:
  LXD module installs the wrong ZFS package if it's missing

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Committed
Status in cloud-init source package in Cosmic:
  Fix Committed
Status in cloud-init source package in Disco:
  Fix Released

Bug description:
  When using the LXD module cloud-init will attempt to install ZFS if it
  does not exist on the target system. However instead of installing the
  `zfsutils-linux` package it attempts to install `zfs` resulting in an
  error.

  This was captured from a MAAS deployed server however the bug is
  platform agnostic.

  ###
  ubuntu@node10ob68:~$ cloud-init --version
  /usr/bin/cloud-init 18.3-9-g2e62cb8a-0ubuntu1~18.04.2

  ### 
  less /var/log/cloud-init.log
  ...
  2018-10-24 19:23:54,255 - util.py[DEBUG]: apt-install [eatmydata apt-get 
--option=Dpkg::Options::=--force-confold 
--option=Dpkg::options::=--force-unsafe-io --assume-yes --quiet install zfs] 
took 0.302 seconds
  2018-10-24 19:23:54,255 - cc_lxd.py[WARNING]: failed to install packages 
['zfs']: Unexpected error while running command.
  Command: ['eatmydata', 'apt-get', '--option=Dpkg::Options::=--force-confold', 
'--option=Dpkg::options::=--force-unsafe-io', '--assume-yes', '--quiet', 
'install', 'zfs']
  Exit code: 100
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1799779/+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 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment

[Chad Smith]

** Changed in: cloud-init
   Status: Fix Released => Confirmed

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

Title:
  Collect all logs needed to debug curtin/cloud-init for each deployment

Status in cloud-init:
  Confirmed
Status in MAAS:
  Incomplete
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released

Bug description:
  According to https://bugs.launchpad.net/maas/+bug/1604962/comments/12,
  these logs are needed to debug curtin/cloud-init issues but aren't
  collected automatically by MAAS:

  - /var/log/cloud-init*
  - /run/cloud-init*
  - /var/log/cloud
  - /tmp/install.log

  We need these to be automatically collected by MAAS so we can
  automatically collect them as artifacts in the case of failures in
  OIL.  curtin/cloud-init issues can be race conditions that are
  difficult to reproduce manually, so we need to grab the logs required
  to debug the first time it happens.

  
  http://pad.lv/1607345
  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1607345

  === Begin SRU Template ===
  [Impact]
  ubuntu-bug cloud-init now collects cloud-init-related information for a 
bug-report

  [Test Case]

  # Launch instance under test
  $ for release in xenial zesty;
do
  ref=$release-proposed;
  lxc-proposed-snapshot --proposed --publish $release $ref;
  lxc launch $ref $name;
  sleep 10;
  lxc exec $name ubuntu-bug cloud-init  # And follow the prompts to report 
a bogus bug
done

  [Regression Potential]
  Worst case scenario is the apport wrapper doesn't work and the developer has 
to file a bug manually instead.

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

  === End SRU Template ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1607345/+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 1802073] Re: No network in AWS (EC-Classic) after stopping and starting instance

[Chad Smith]

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

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

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

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

Title:
  No network in AWS (EC-Classic) after stopping and starting instance

Status in cloud-init package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Bionic:
  New
Status in cloud-init source package in Cosmic:
  New

Bug description:
  I don't know is this cloud-init or netplan or what, but this is not
  good.

  Background:
  # lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  # apt-cache policy cloud-init
  cloud-init:
Installed: 18.4-0ubuntu1~18.04.1
Candidate: 18.4-0ubuntu1~18.04.1
Version table:
   *** 18.4-0ubuntu1~18.04.1 500
  500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu 
bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   18.2-14-g6d48d265-0ubuntu1 500
  500 http://eu-west-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64 
Packages

  
  1. Get newest image to use

  $ aws --region eu-west-1 ec2 describe-images --owners 099720109477
  --filters Name=root-device-type,Values=ebs
  Name=architecture,Values=x86_64 Name=name,Values='*hvm-ssd/ubuntu-
  bionic-18.04*' --query 'sort_by(Images, )[-1].ImageId'

  "ami-08596fdd2d5b64915"

  2. Start instance to EC2-Classic with that image.

  3. Try to SSH. Everything is ok.

  # cat /var/log/cloud-init-output.log
  Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init-local' at Wed, 07 Nov 2018 
08:12:16 +. Up 10.51 seconds.
  Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'init' at Wed, 07 Nov 2018 
08:12:21 +. Up 15.50 seconds.
  ci-info: +++Net device 
info
  ci-info: 
++--+-+-++---+
  ci-info: | Device |  Up  |   Address   |   Mask  | 
Scope  | Hw-Address|
  ci-info: 
++--+-+-++---+
  ci-info: |  eth0  | True | 10.74.200.25| 255.255.255.192 | 
global | 22:00:0a:4a:c8:19 |
  ci-info: |  eth0  | True | fe80::2000:aff:fe4a:c819/64 |.|  
link  | 22:00:0a:4a:c8:19 |
  ci-info: |   lo   | True |  127.0.0.1  |255.0.0.0|  
host  | . |
  ci-info: |   lo   | True |   ::1/128   |.|  
host  | . |
  ci-info: 
++--+-+-++---+
  ...
  Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'modules:config' at Wed, 07 Nov 
2018 08:12:41 +. Up 35.63 seconds.
  Cloud-init v. 18.4-0ubuntu1~18.04.1 running 'modules:final' at Wed, 07 Nov 
2018 08:12:44 +. Up 38.98 seconds.
  Cloud-init v. 18.4-0ubuntu1~18.04.1 finished at Wed, 07 Nov 2018 08:12:45 
+. Datasource DataSourceEc2Local.  Up 39.38 seconds

  4. Stop the instance.

  5. Start the instance.

  6. Try to SSH.
  Expected to happen: Instance has network and is working.
  What happens: Instance has no working network

  Getting instance log we can see:
  [   11.342357] cloud-init[412]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 
'init-local' at Wed, 07 Nov 2018 08:21:07 +. Up 10.77 seconds.
  [  OK  ] Started Initial cloud-init job (pre-networking).
  [  OK  ] Reached target Network (Pre).
   Starting Network Service...
  [  OK  ] Started Network Service.
   Starting Network Name Resolution...
   Starting Wait for Network to be Configured...
  [  OK  ] Started Wait for Network to be Configured.
   Starting Initial cloud-init job (metadata service crawler)...
  [  OK  ] Started Network Name Resolution.
  [  OK  ] Reached target Host and Network Name Lookups.
  [  OK  ] Reached target Network.
  [   13.036207] cloud-init[637]: Cloud-init v. 18.4-0ubuntu1~18.04.1 running 
'init' at Wed, 07 Nov 2018 08:21:08 +. Up 12.55 seconds.
  [   13.052849] cloud-init[637]: ci-info: +++Net 
device info
  [   13.100325] cloud-init[637]: ci-info: 
++---+---+---+---+---+
  [   13.121790] cloud-init[637]: ci-info: | Device |   Up  |  Address  |
Mask   | Scope | Hw-Address|
  [   13.129189] cloud-init[637]: ci-info: 
++---+---+---+---+---+
  [   13.144839] cloud-init[637]: 

[Group.of.nepali.translators] [Bug 1795953] Re: sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1)

[Chad Smith]

** Summary changed:

- sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1~18.04.1)
+ sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1)

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

Title:
  sru cloud-init (18.3.9-g2e62cb8a-0ubuntu1) to (18.4-0ubuntu1)

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  New
Status in cloud-init source package in Bionic:
  New

Bug description:
  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones that affect Ubuntu are:

   - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]
   - cli: add cloud-init query subcommand to query instance metadata
   - OpenStack: Support setting mac address on bond.
    [Fabian Wiesel] (LP: #1682064)
   - EphemeralIPv4Network: Be more explicit when adding default route.
    (LP: #1792415)
   - OpenStack: support reading of newer versions of metdata.
   - OpenStack: fix bug causing 'latest' version to be used from network.
    (LP: #1792157)
   - user-data: jinja template to render instance-data.json in cloud-config
    (LP: #1791781)
   - config: disable ssh access to a configured user account
   - sysconfig: refactor sysconfig to accept distro specific templates paths
   - hyperv_reporting_handler: simplify threaded publisher
   - VMWare: Fix a network config bug in vm with static IPv4 and no gateway.
    [Pengpeng Sun] (LP: #1766538)
   - logging: Add logging config type hyperv for reporting via Azure KVP
    [Andy Liu]
   - Add oracle datasource to debian/cloud-init.templates
   - Add datasource Oracle Compute Infrastructure (OCI).
   - azure: allow azure to generate network configuration from IMDS per boot.
   - Scaleway: Add network configuration to the DataSource [Louis Bouchard]
    [Wesley Gao]
   - netplan: Correctly render macaddress on a bonds and bridges when
    provided. (LP: #1784699)
   - tools: Add 'net-convert' subcommand command to 'cloud-init devel'.
   - Use typeset or local in profile.d scripts. (LP: #1784713)
   - OpenNebula: Fix null gateway6 [Akihiko Ota] (LP: #1768547)
   - oracle: fix detect_openstack to report True on OracleCloud.com DMI data
    (LP: #1784685)
   - update_metadata re-config on every boot comments and tests not quite
    right [Mike Gerdts]
   - get_linux_distro: add support for centos6 and rawhide flavors of redhat
    (LP: #1781229)

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/CloudinitUpdates

  The cloud-init team will be in charge of attaching the artifacts and
  console output of the appropriate run to the bug.  cloud-init team
  members will not mark ‘verification-done’ until this has happened.

  * Automated Test Results
  
  
  
  

  * Manual Test Results
  
  
  

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned integration tests are attached to this bug.

  [Discussion]
  

  == End SRU Template ==

  == Complete ChangeLog ==
  - release 18.4
  - tests: allow skipping an entire cloud_test without running.
  - tests: disable lxd tests on cosmic
  - cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps
  - lxd: adjust to snap installed lxd.
  - docs: surface experimental doc in instance-data.json
  - tests: fix ec2 integration tests. process meta_data instead of meta-data
  - Add support for Infiniband network interfaces (IPoIB). [Mark Goddard]
  - cli: add cloud-init query subcommand to query instance metadata
  - tools/tox-venv: update for new features.
  - pylint: ignore warning assignment-from-no-return for _write_network
  - stages: Fix bug causing datasource to have incorrect sys_cfg.
  - Remove dead-code _write_network distro implementations.
  - net_util: ensure static configs have netmask in translate_network result
    [Thomas Berger]
  - Fall back to root:root on syslog permissions if other options fail.
    [Robert Schweikert]
  - tests: Add mock for util.get_hostname. [Robert Schweikert]
  - ds-identify: doc string cleanup.
  - OpenStack: Support setting mac address on bond. [Fabian Wiesel]
  - bash_completion/cloud-init: fix shell syntax error.
  - EphemeralIPv4Network: Be more explicit when adding default route.
  - OpenStack: support reading of newer versions of metdata.
  - OpenStack: fix bug causing 'latest' version to be used from network.
  

[Group.of.nepali.translators] [Bug 1771198] Re: Support disable_root-esque behaviour for other users

[Chad Smith]

** Changed in: cloud-init
   Status: Triaged => Fix Released

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

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

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

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

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

** Changed in: cloud-init (Ubuntu Cosmic)
 Assignee: (unassigned) => Chad Smith (chad.smith)

** Changed in: cloud-init (Ubuntu Bionic)
   Status: New => Triaged

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

** Merge proposal linked:
   
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/354496

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

Title:
  Support disable_root-esque behaviour for other users

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Triaged
Status in cloud-init source package in Bionic:
  Triaged
Status in cloud-init source package in Cosmic:
  Fix Released

Bug description:
  When building Ubuntu cloud images, we prefer to name the default user
  "ubuntu" where possible, to maintain a consistent user experience
  between substrates.  Some clouds, however, like to have a consistent
  user name across all of their various image offerings.  This is an
  inherent conflict.  One way in which we have agreed to resolve this is
  to use the messaging that the disable_root behaviour currently
  provides on the cloud-specific user, to point to the ubuntu user.
  This means, at least, that users are given some direction (rather than
  being left wondering if their instance has provisioned correctly, or
  if their SSH keys are invalid, or )

  I propose a new cloud.cfg key named "ssh_disable_users" which defines
  a list of users.  For each of these users, cloud-init will ensure they
  exist, and configure the system so that users SSH'ing to that user
  will be redirected to the default user (a la disable_root behaviour
  currently).

  (`disable_root: True` would translate as `ssh_disable_users:
  ["root"]`.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1771198/+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 1770712] Re: It would be nice if cloud-init provides full version in logs

[Chad Smith]

won't fixed artful as it is EOL as of June 20th,

** Tags removed: verification-needed verification-needed-artful 
verification-needed-xenial
** Tags added: verification-done verification-done-artful 
verification-done-xenial

** Tags removed: verification-done-artful verification-needed-bionic
** Tags added: verification-done-bionic

** Description changed:

+ === Begin SRU Template ===
+ [Impact]
+ Cloud-init logs should now contain full packaged version of cloud-init on 
xenial, artful and bionic.
+ 
+ [Test Case]
+ # We should see specific version and patch information
+ for series in xenial artful bionic;
+ do
+echo '=== BEGIN ' $series ' ==='
+ref=$series-proposed;
+lxc delete test-$series --force;
+lxc-proposed-snapshot -p -P $series $ref | egrep 'Creating|cloud-init';
+lxc init $ref test-$series;
+lxc start test-$series;
+packaged_version=`lxc exec test-$series -- dpkg-query --show -f 
'${version}' cloud-init`;
+lxc exec test-$series -- grep $packaged_version /var/log/cloud-init.log;
+lxc exec test-$series -- cloud-init --version;
+ done
+ 
+ # Also, cloud-init --version should show the packaged version
+ # it should contain a -0ubuntu portion.
+ 
+ $ cloud-init --version
+ /usr/bin/cloud-init 18.3-9-g2e62cb8a-0ubuntu1
+ 
+ [Regression Potential]
+ This really should be low chance of regression.  The chance would be
+ if something is running 'cloud-init --version' and parsing the output,
+ or parsing the output of /var/log/cloud-init.log (or the console log).
+ 
+ Such specific parsing of a log seems brittle anyway. Parsing output
+ of --version that expected to not have a -0ubuntuX in it would need to
+ be updated.
+ 
+ [Other Info]
+ Upstream commit at
+   https://git.launchpad.net/cloud-init/commit/?id=525a9e8f
+ 
+ === End SRU Template ===
+ 
+ 
  [Test Case]
  # We should see specific version and patch information
  $ packaged_version=$(dpkg-query --show -f '${version}' cloud-init)
  $ grep $packaged_version /var/log/cloud-init.log  # Expect to stage header 
logs
  ...
  2018-07-10 19:33:16,406 - util.py[DEBUG]: Cloud-init v. 
18.3-9-g2e62cb8a-0ubuntu1 running 'init-local' at Tue, 10 Jul 2018 19:33:16 
+. Up 1.00 seconds.
  
  # Also, cloud-init --version should show the packaged version
  # it should contain a -0ubuntu portion.
  
  $ cloud-init --version
  /usr/bin/cloud-init 18.3-9-g2e62cb8a-0ubuntu1
  
  [Regression Potential]
  This really should be low chance of regression.  The chance would be
  if something is running 'cloud-init --version' and parsing the output,
  or parsing the output of /var/log/cloud-init.log (or the console log).
  
  Such specific parsing of a log seems brittle anyway. Parsing output
  of --version that expected to not have a -0ubuntuX in it would need to
  be updated.
  
  [Other Info]
  Upstream commit at
-   https://git.launchpad.net/cloud-init/commit/?id=525a9e8f
+   https://git.launchpad.net/cloud-init/commit/?id=525a9e8f
  
  === End SRU Template ===
  
  
+ === Original Description ===
  Cloud-init rsyslog has the major version of cloud-init:
  
  May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2
  running 'init-local' at Fri, 11 May 2018 17:40:47 +. Up 15.63
  seconds.
  
  However, it would be nice if it places the whole version, so that we can
  now exactly what version of cloud-init its running, e.g:
  
  May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2
  (27-g6ef92c98-0ubuntu1~18.04.1) running 'init-local' at Fri, 11 May 2018
  17:40:47 +. Up 15.63 seconds.

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

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

Title:
  It would be nice if cloud-init provides full version in logs

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Artful:
  Won't Fix
Status in cloud-init source package in Bionic:
  Fix Committed
Status in cloud-init source package in Cosmic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Cloud-init logs should now contain full packaged version of cloud-init on 
xenial, artful and bionic.

  [Test Case]
  # We should see specific version and patch information
  for series in xenial artful bionic;
  do
 echo '=== BEGIN ' $series ' ==='
 ref=$series-proposed;
 lxc delete test-$series --force;
 lxc-proposed-snapshot -p -P $series $ref | egrep 'Creating|cloud-init';
 lxc init $ref test-$series;
 lxc start test-$series;
 packaged_version=`lxc exec test-$series -- dpkg-query --show -f 
'${version}' cloud-init`;
 lxc exec test-$series -- grep $packaged_version /var/log/cloud-init.log;
 lxc exec test-$series 

[Group.of.nepali.translators] [Bug 1777912] Re: sru cloud-init (18.2-4-g05926e48-0ubuntu1) to (18.3-9ubuntu1)

[Chad Smith]

Dropping Artful from this SRU as it is now officially EOL
https://meta.askubuntu.com/questions/18032/eol-notice-artful-
aardvark-17-10-reached-end-of-life-on-july-19-2018

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

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

Title:
  sru cloud-init (18.2-4-g05926e48-0ubuntu1) to (18.3-9ubuntu1)

Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Artful:
  Won't Fix
Status in cloud-init source package in Bionic:
  Fix Committed

Bug description:
  UPDATE#2 07/31/2018:
  2nd SRU regresssion found by FrancisGinther testing Oracle. Expected 
OpenStack datasource not detected across dirty reboot after upgrade.
  Cherry-picking fix for LP: #1784685 before this SRU is let through.

  UPDATE:
  SRU regression found during 18.3.0 -proposed validation. fix is queued 
present in 18.3.9 for bug https://bugs.launchpad.net/cloud-init/+bug/1780481.

  Updated description of changes for minor SRU-update to 18.3 targets
  Xenial, Artful and Bionic.

   18.2.4 -> 18.3 changeset contains

   - OpenStack now runs at local time frame network config can be rendered from 
network_data.json if configured "apply_network_config: true".
   - Fix utf-8 content in user-data (LP: #1768600)
   - many SmartOS improvements

  == Begin SRU Template ==
  [Impact]
  This release sports both bug-fixes and new features and we would like to
  make sure all of our supported customers have access to these
  improvements. The notable ones are:

  - Explicitly prevent `sudo` access for user module [Jacob Bednarz]
  - lxd: Delete default network and detach device if lxd-init created them.
  - openstack: avoid unneeded metadata probe on non-openstack platforms
  - stages: fix tracebacks if a module stage is undefined or empty
    [Robert Schweikert]
  - Be more safe on string/bytes when writing multipart user-data to disk.
  - Fix get_proc_env for pids that have non-utf8 content in environment.
  - netplan: fix mtu if provided by network config for all rendered types
  - subp: support combine_capture argument.
  - util: add get_linux_distro function to replace platform.dist
  - Enable SmartOS network metadata to work with netplan via per-subnet
    routes [Dan McDonald]
  - openstack: Allow discovery in init-local using dhclient in a sandbox.
  - yaml_load/schema: Add invalid line and column nums to error message
  - Azure: Ignore NTFS mount errors when checking ephemeral drive
    [Paul Meyer]
  - Update version.version_string to contain packaged version.
  - cc_mounts: Do not add devices to fstab that are already present.
    [Lars Kellogg-Stedman]
  - ds-identify: ensure that we have certain tokens in PATH.
  - read_file_or_url: move to url_helper, fix bug in its FileResponse.
  - ds-identify: recognize container-other as a container, test SmartOS.
  - cloud-config.service: run After snap.seeded.service.
  - SmartOS: fix get_interfaces for nics that do not have addr_assign_type.
  - azure: Add reported ready marker file. [Joshua Chan]
  - FreeBSD: Invoke growfs on ufs filesystems such that it does not prompt.
  - netinfo: fix netdev_pformat when a nic does not have an address 
assigned.
  - collect-logs: add -v flag, write to stderr, limit journal to single 
boot.
  - IBMCloud: Disable config-drive and nocloud only if IBMCloud is enabled.
  - Add reporting events and log_time around early source of blocking time
   --- Addtional changelog delta for Xenial, Artful 
  - net: detect unstable network names and trigger a settle if needed
  - DataSourceSmartOS: add locking of serial device. [Mike Gerdts]
  - DataSourceSmartOS: sdc:hostname is ignored [Mike Gerdts]
  - DataSourceSmartOS: list() should always return a list [Mike Gerdts]
  - schema: in validation, raise ImportError if strict but no jsonschema.
  - set_passwords: Add newline to end of sshd config, only restart if
    updated.
  - Schema: do not warn on duplicate items in commands.
  - net: Depend on iproute2's ip instead of net-tools ifconfig or route
  - DataSourceSmartOS: fix hang when metadata service is down [Mike Gerdts]
  - DataSourceSmartOS: change default fs on ephemeral disk from ext3 to
    ext4. [Mike Gerdts]
  - Implement bash completion script for cloud-init command line
  - renderer: support unicode in render_from_file.
  - Implement ntp client spec with auto support for distro selection
  - Apport: add Brightbox, IBM, LXD, and OpenTelekomCloud to list of clouds.

  [Test Case]
  The following development and SRU process was followed:
  

[Group.of.nepali.translators] [Bug 1774666] Re: Bond interfaces stuck at 1500 MTU on Bionic

[Chad Smith]

This is a cloud-init issue only. Once cloud-init is SRU'd netplan will
properly set mtu.

** Changed in: netplan.io (Ubuntu Xenial)
   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/1774666

Title:
  Bond interfaces stuck at 1500 MTU on Bionic

Status in cloud-init:
  Fix Committed
Status in MAAS:
  Invalid
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in cloud-init source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in cloud-init source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Invalid
Status in cloud-init source package in Cosmic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Confirmed

Bug description:
  When deploying a machine through MAAS with bonded network interfaces,
  the bond does not have a 9000 byte MTU applied despite the attached
  VLANs having had a 9000 MTU explicitly set. The MTU size is set on the
  bond members, but not on the bond itself in Netplan. Consequently,
  when the bond is brought up, the interface MTU is decreased from 9000
  to 1500. Manually changing the interface MTU after boot is successful.

  This is not observed when deploying Xenial on the same machine. The
  bond comes up at the expected 9000 byte MTU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1774666/+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 1774666] Re: Bond interfaces stuck at 1500 MTU on Bionic

[Chad Smith]

This is a cloud-init issue only. Once cloud-init is SRU'd netplan will
properly set mtu.

** Changed in: netplan.io (Ubuntu Artful)
   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/1774666

Title:
  Bond interfaces stuck at 1500 MTU on Bionic

Status in cloud-init:
  Fix Committed
Status in MAAS:
  Invalid
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in cloud-init source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in cloud-init source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Invalid
Status in cloud-init source package in Cosmic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Confirmed

Bug description:
  When deploying a machine through MAAS with bonded network interfaces,
  the bond does not have a 9000 byte MTU applied despite the attached
  VLANs having had a 9000 MTU explicitly set. The MTU size is set on the
  bond members, but not on the bond itself in Netplan. Consequently,
  when the bond is brought up, the interface MTU is decreased from 9000
  to 1500. Manually changing the interface MTU after boot is successful.

  This is not observed when deploying Xenial on the same machine. The
  bond comes up at the expected 9000 byte MTU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1774666/+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 1774666] Re: Bond interfaces stuck at 1500 MTU on Bionic

[Chad Smith]

This is a cloud-init issue only. Once cloud-init is SRU'd netplan will
properly set mtu.

** Changed in: netplan.io (Ubuntu Bionic)
   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/1774666

Title:
  Bond interfaces stuck at 1500 MTU on Bionic

Status in cloud-init:
  Fix Committed
Status in MAAS:
  Invalid
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  New
Status in netplan.io source package in Xenial:
  Invalid
Status in cloud-init source package in Artful:
  New
Status in netplan.io source package in Artful:
  Invalid
Status in cloud-init source package in Bionic:
  New
Status in netplan.io source package in Bionic:
  Invalid
Status in cloud-init source package in Cosmic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Confirmed

Bug description:
  When deploying a machine through MAAS with bonded network interfaces,
  the bond does not have a 9000 byte MTU applied despite the attached
  VLANs having had a 9000 MTU explicitly set. The MTU size is set on the
  bond members, but not on the bond itself in Netplan. Consequently,
  when the bond is brought up, the interface MTU is decreased from 9000
  to 1500. Manually changing the interface MTU after boot is successful.

  This is not observed when deploying Xenial on the same machine. The
  bond comes up at the expected 9000 byte MTU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1774666/+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 1767166] Re: IBMCloud datasource does not recognize provisioning in debug mode.

[Chad Smith]

This bug is believed to be fixed in cloud-init in
version18.2-27-g6ef92c98-0ubuntu1~18.04.1. If this is still a problem
for you, please make a comment and set the state back to New

Thank you.

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

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

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

Title:
  IBMCloud datasource does not recognize provisioning in debug mode.

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Committed
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released
Status in cloud-init source package in Cosmic:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Cloud-init is disabled in the provisioning state. If provisioning
  artifacts are left around after debug mode, cloud-init remains disabled
  and doesn't properly configure the instance.

  This issue only affects images that are being tested by IBM before official
  publication.  Once officially published, the images will have a 'production'
  tag, and bug does not reproduce.

  As such, it is believed that a regular end user is not really able to
  produce.

  [Test Case]
  cat > sethostname.yaml < /run/runcmd-ran.txt']
  EOF

  VM_IP=`launch-softlayer --pubkey-file ~/.ssh/id_rsa.pub -u
  sethostname.yaml -i os:xenial | awk '/primary ip/{printf "root@%s",
  $3}'`

  ssh root@$VM_IP -- dpkg-query --show cloud-init;
  ssh root@$VM_IP -- cloud-init status --long;
  ssh root@$VM_IP -- cloud-init analyze show;
  ssh root@$VM_IP -- sh -c '
mirror=http://archive.ubuntu.com/ubuntu
echo deb $mirror $(lsb_release -sc)-proposed main | tee 
/etc/apt/sources.list.d/proposed.list
apt-get update -q
apt-get install -qy cloud-init';
  ssh root@$VM_IP -- DEBUG_LEVEL=2 DI_LOG=stderr 
/usr/lib/cloud-init/ds-identify --force 2>&1 | grep provision
  ssh root@$VM_IP -- cloud-init clean --logs --reboot;
  ssh root@$VM_IP -- egrep 'provisioning|swinstall' /var/log/cloud-init.log
  ssh root@$VM_IP -- grep provision /run/cloud-init/ds-identify.log

  [Regression Potential]
  Regression will still be limited to softlayer instances as code changes are
  limited to softlayer datasource detection in ds-identify and
  DataSourceIBMCloud.

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

  This bug is currently fixed in bionic-proposed version
  (18.2-27-g6ef92c98-0ubuntu1~18.04.1) and
  cloud-init trunk, so first upload to ubuntu 'cc' will have it fixed.

  === End SRU Template ===

  
  When IBMCloud deploys from a template, artifacts from the
  provisioning stage are normally cleaned up.  Cloud-init relied'
  on that behavior to determine the provisioning boot from the subsequent
  post-provisioning boot.

  However, when testing, the provisioning stage will leave artifacts
  in place (/root/provisioningConfiguration.cfg).  This caused cloud-init
  to permenantly believe that it was in the provisioning stage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1767166/+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 1752711] Re: cloud-init no longer processes user data on GCE in artful

[Chad Smith]

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

Thank you.

** Changed in: cloud-init
   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/1752711

Title:
  cloud-init no longer processes user data on GCE in artful

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Any user-data provided when creating google cloud instances is ignored so no 
instance customization is observed. This is a silent failure and no tracebacks 
in cloud-init represent that failure to the user.

  Providing a simple cloud-config to set a hostname will provide a quick
  validation of cloud-init observing user-data.

  [Test Case]

  # Create cloud-config which should change the hostname, and cli prompt
  $ cat > sethostname.yaml 

[Group.of.nepali.translators] [Bug 1735821] Re: netplan needs bridge port-priority support

[Chad Smith]

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

Thank you.

** Changed in: cloud-init
   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/1735821

Title:
  netplan needs bridge port-priority support

Status in cloud-init:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in nplan source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Users of netplan configuring any bridge. Port priority is a very common 
setting to change when setting up bridge devices that might have multiple 
interfaces.

  [Test case]
  1) Write a netplan configuration:
  network:
  version: 2
  ethernets:
  eth0:
  match:
  name: eth0
  bridges:
  br0:
  addresses:
  - 192.168.14.2/24
  interfaces:
  - eth0
  parameters:
  path-cost:
  eth0: 50
  priority: 22
  port-priority:
  eth0: 14

  2) Run 'sudo netplan apply'

  3) Validate that the config generated by netplan is correct:

  In /run/systemd/network/10-netplan-eth0.network:

  [...]
  [Bridge]
  [...]
  Priority=14

  4) Validate that the port-priority value for the bridge has been
  correctly set:

  $ cat /sys/class/net/mybr/brif/eth0/priority


  [Regression potential]
  This might impact STP behavior, such that while the port priority for a 
bridge changes, the general network topology might change -- this may lead to 
loss of connectivity on the bridge itself or on other devices on the network, 
invalid packet traffic (packets showing up where they should not), etc.

  ---

  Now that systemd supports port-priority for bridges (LP: #1668347)
  netplan should handle port-priority like it does path-cost.

  1) % lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  1) # lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2) # apt-cache policy nplan
  nplan:
    Installed: 0.30
    Candidate: 0.32
    Version table:
   0.32 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
   *** 0.30 100
  100 /var/lib/dpkg/status

  3) netplan generate renders a networkd .network file which has
  [Bridge] section including  Priority  value set on each of the bridge
  ports specified

  4) netplan fails to parse the input yaml with

  Sample config that should parse:

  % cat br-pp.yaml
  network:
  version: 2
  ethernets:
  eth0:
  match:
  macaddress: '52:54:00:12:34:04'
  bridges:
  br0:
  addresses:
  - 192.168.14.2/24
  interfaces:
  - eth0
  parameters:
  path-cost:
  eth0: 50
  priority: 22
  port-priority:
  eth0: 14

  % netplan generate
  Error in network definition br-pp.yaml line 13 column 16: unknown key 
port-priority

  If fixed, then I would expect a /run/systemd/network/10-netplan-eth0.network 
that looks like
  [Match]
  MACAddress=52:54:00:12:34:00
  Name=eth0

  [Network]
  Bridge=br0
  LinkLocalAddressing=no
  IPv6AcceptRA=no

  [Bridge]
  Cost=50
  Priority=14

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1735821/+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 1721579] Re: azure: remove sriov device configuration

[Chad Smith]

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

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

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

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

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

** Changed in: cloud-init (Ubuntu Artful)
   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/1721579

Title:
  azure: remove sriov device configuration

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

Bug description:
  Microsoft has requested that we remove the VF/sriov specific changes
  we made to the Azure datasource under private bug 1695119.

  There is another solution in place now in the linux kernel that
  will suffice.

  Essentially, this means backing out much of the commit
   ebc9ecbc8a76bdf511a456fb72339a7eb4c20568
  https://git.launchpad.net/cloud-init/commit/?id=ebc9ecbc8a7

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1721579/+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 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment

[Chad Smith]

=== cloud-init SRU Verification output ===
--- xenial 
root@test-xenial:~# ubuntu-bug cloud-init

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.
*** Your device details (lshw) may be useful to developers when addressing this 
bug, but gathering it requires admin privileges. Would you like to include this 
info?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y
  
*** Is this machine running in a cloud environment?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y

*** Please select the cloud vendor or environment in which this instance
is running


Choices:
  1: Amazon - Ec2
  2: AliYun
  3: AltCloud
  4: Azure
  5: Bigstep
  6: CloudSigma
  7: CloudStack
  8: DigitalOcean
  9: GCE - Google Compute Engine
  10: MAAS
  11: NoCloud
  12: OpenNebula
  13: OpenStack
  14: OVF
  15: Scaleway
  16: SmartOS
  17: VMware
  18: Other
  C: Cancel
Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 6
.
*** Your user-data or cloud-config file can optionally be provided from 
/var/lib/cloud/instance/user-data.txt and could be useful to developers when 
addressing this bug. Do you wish to attach user-data to this bug?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y
..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (85.6 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): v

What would you like to do? Your options are:
  S: Send report (85.6 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): k
Problem report file: /tmp/apport.cloud-init.7_ilbqj5.apport


root@test-xenial:~# egrep 'user_data|Cloud|lshw' 
/tmp/apport.cloud-init.7_ilbqj5.apport
CloudName: CloudSigma
 Cloud-init v. 17.1 running 'init-local' at Mon, 16 Oct 2017 20:21:45 +. Up 
0.00 seconds.
 Cloud-init v. 17.1 running 'init' at Mon, 16 Oct 2017 20:21:49 +. Up 4.00 
seconds.
 Cloud-init v. 17.1 running 'modules:config' at Mon, 16 Oct 2017 20:21:50 
+. Up 5.00 seconds.
 Cloud-init v. 17.1 running 'modules:final' at Mon, 16 Oct 2017 20:21:51 +. 
Up 6.00 seconds.
 Cloud-init v. 17.1 finished at Mon, 16 Oct 2017 20:22:26 +. Datasource 
DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net].  Up 41.00 
seconds
lshw.txt:
user_data.txt:

---zesty
root@test-zesty:~# ubuntu-bug cloud-init

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.

*** Your device details (lshw) may be useful to developers when addressing this 
bug, but gathering it requires admin privileges. Would you like to include this 
info?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y

*** Is this machine running in a cloud environment?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y

*** Please select the cloud vendor or environment in which this instance
is running


Choices:
  1: Amazon - Ec2
  2: AliYun
  3: AltCloud
  4: Azure
  5: Bigstep
  6: CloudSigma
  7: CloudStack
  8: DigitalOcean
  9: GCE - Google Compute Engine
  10: MAAS
  11: NoCloud
  12: OpenNebula
  13: OpenStack
  14: OVF
  15: Scaleway
  16: SmartOS
  17: VMware
  18: Other
  C: Cancel
Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 5

*** Your user-data or cloud-config file can optionally be provided from
/var/lib/cloud/instance/user-data.txt and could be useful to developers
when addressing this bug. Do you wish to attach user-data to this bug?


What would you like to do? Your options are:
  Y: Yes
  N: No
  C: Cancel
Please choose (Y/N/C): y
..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (102.7 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): k
Problem report file: /tmp/apport.cloud-init.c2rk91_3.apport
root@test-zesty:~# egrep 'user_data|cloud|lshw' 
/tmp/apport.cloud-init.c2rk91_3.apport 
 cloud-guest-utils 0.30-0ubuntu2
 Oct 16 20:25:24 hostname systemd[1]: cloud-init-local.service: 

[Group.of.nepali.translators] [Bug 1725067] Re: cloud-init resizefs fails when booting with root=PARTUUID=

[Chad Smith]

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

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

** Changed in: cloud-init
   Status: In Progress => Fix Released

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

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

** Changed in: cloud-init (Ubuntu Zesty)
   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/1725067

Title:
  cloud-init resizefs fails when booting with root=PARTUUID=

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

Bug description:
  http://pad.lv/1725067
  https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1725067

  === Begin SRU Template ===
  [Impact]
  Growing the root partition would if:
   a.) if the device /dev/root did not exist
   b.) the kernel command line included PARTUUID=

  [Test Case]
  get-proposed-image is

https://github.com/cloud-init/qa-scripts/blob/master/scripts/get-proposed-cloudimg
  It downloads a cloud image of a given release, and then creates a -proposed
  image with cloud-init upgraded.

  A script 'recreate.sh' will run each of the steps below automated.

https://github.com/cloud-init/ubuntu-sru/blob/master/bugs/lp-1684869/recreate.sh

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

  2.) get the partition uuid of the first partition
 # for xenial images that are dos partition table rather than gpt
 # we need to convert that with:
 #sgdisk --mbrtogpt $raw
 $ raw=yakkety-server-cloudimg-amd64-proposed.raw
 $ ptuuid=$(sfdisk --part-uuid $raw 1)

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

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

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

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

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

  
  [Regression Potential]
  Regressions would surface as the root filesystem not being correctly resized.
  The user would find themselves with not as much disk as expected.

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

  Note that this was a regression of changes added in
   * bug 1684869: growing root partition does not always work with 
root=PARTUUID=
   * bug 1677376: growing partitions does not work when booted without initramfs

  The issue probably is only seen if using the version of cloud-init
  in xenial-proposed.  Zesty and artful kernels or userspace made the change
  actually not regress.  However we will verify functionality for the uploaded
  version in each of x, z, a.

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

  === End SRU Template ===

  A freshly built Ubuntu 17.10 image that's configured to boot without
  initramfs by passing root=PARTUUID= on the kernel commandline
  comes up degraded because cloud-init fails to resize the root
  partition.

  Oct 20 00:07:30 ubuntu cloud-init[493]: 2017-10-20 00:07:30,656 - 
util.py[WARNING]: Failed to resize filesystem (cmd=('resize2fs', '/dev/root'))
  Oct 20 00:07:30 ubuntu cloud-init[493]: 2017-10-20 00:07:30,662 - 
util.py[WARNING]: Running module resizefs () failed

  Looking at the code, I see that there are two separate implementations
  of rootdev_from_cmdline, one in