[Group.of.nepali.translators] [Bug 1829196] Re: linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

2019-05-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1829847 (linux-gcp)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829200
- phase: Testing
- phase-changed: Monday, 20. May 2019 18:14 UTC
+ phase: Signoff
+ phase-changed: Monday, 27. May 2019 17:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
promote-to-updates: Pending -- Nvidia object not found -- 
current-driver-4.15.0-1033-gcp-amd64
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-gcp: 4.15.0-1033.35~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

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

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

  derivatives: bug 1829847 (linux-gcp)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829200
  phase: Signoff
  phase-changed: Monday, 27. May 2019 17:14 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-updates: Pending -- Nvidia object not found -- 
current-driver-4.15.0-1033-gcp-amd64
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829196/+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 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
19.1-1-gbaa47854-0ubuntu1~18.04.1

---
cloud-init (19.1-1-gbaa47854-0ubuntu1~18.04.1) bionic; urgency=medium

  * debian/patches/ubuntu-advantage-revert-tip.patch
Revert ubuntu-advantage config module changes until ubuntu-advantage-tools
19.1 publishes to Bionic (LP: #1828641)
  * New upstream snapshot. (LP: #1828637)
- Azure: Return static fallback address as if failed to find endpoint
  [Jason Zions (MSFT)]
- release 19.1
- freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]
- tests: add Eoan release [Paride Legovini]
- cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)]
- replace remaining occurrences of LOG.warn
- DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
- Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
- git tests: no longer show warning about safe yaml. [Scott Moser]
- tools/read-version: handle errors [Chad Miller]
- net/sysconfig: only indicate available on known sysconfig distros
- packages: update rpm specs for new bash completion path
- test_azure: mock util.SeLinuxGuard where needed [Jason Zions (MSFT)]
- setup.py: install bash completion script in new location
- mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder]
- cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]
- Revert "DataSource: move update_events from a class to an instance..."
- Change DataSourceNoCloud to ignore file system label's case.
  [Risto Oikarinen]
- cmd:main.py: Fix missing 'modules-init' key in modes dict
  [Antonio Romito]
- ubuntu_advantage: rewrite cloud-config module
- Azure: Treat _unset network configuration as if it were absent
  [Jason Zions (MSFT)]
- DatasourceAzure: add additional logging for azure datasource [Anh Vo]
- cloud_tests: fix apt_pipelining test-cases
- Azure: Ensure platform random_seed is always serializable as JSON.
  [Jason Zions (MSFT)]
- net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert]
- tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold]
- net: Fix ipv6 static routes when using eni renderer [Raphael Glon]
- Add ubuntu_drivers config module
- doc: Refresh Azure walinuxagent docs
- tox: bump pylint version to latest (2.3.1)
- DataSource: move update_events from a class to an instance attribute
- net/sysconfig: Handle default route setup for dhcp configured NICs
  [Robert Schweikert]
- DataSourceEc2: update RELEASE_BLOCKER to be more accurate

 -- Chad Smith   Fri, 10 May 2019 23:17:50
-0600

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

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

Title:
  sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco

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 Cosmic:
  Fix Released
Status in cloud-init source package in Disco:
  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:

  - Azure: Return static fallback address as if failed to find endpoint
    [Jason Zions (MSFT)]
  - cc_mounts: check if mount -a on no-change fstab path [Jason Zions 
(MSFT)]
  - replace remaining occurrences of LOG.warn
  - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
  - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
  - packages: update rpm specs for new bash completion path
  - setup.py: install bash completion script in new location
  - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder]
  - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]
  - Revert "DataSource: move update_events from a class to an instance..."
  - Change DataSourceNoCloud to ignore file system label's case.
    [Risto Oikarinen]
  - cmd:main.py: Fix missing 'modules-init' key in modes dict
    [Antonio Romito]
  - ubuntu_advantage: rewrite cloud-config module
  - Azure: Treat _unset network configuration as if it were absent
    [Jason Zions (MSFT)]
  - DatasourceAzure: add additional logging for azure datasource [Anh Vo]
  - Azure: Ensure platform random_seed is always serializable as JSON.
    [Jason Zions (MSFT)]
  - net: Fix ipv6 static routes when using eni renderer [Raphael Glon]
  - Add ubuntu_drivers config module
  - DataSource: move update_events 

[Group.of.nepali.translators] [Bug 1828641] Re: Xenial, Bionic, Cosmic revert ubuntu-advantage-tools config module changes from tip

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
19.1-1-gbaa47854-0ubuntu1~18.04.1

---
cloud-init (19.1-1-gbaa47854-0ubuntu1~18.04.1) bionic; urgency=medium

  * debian/patches/ubuntu-advantage-revert-tip.patch
Revert ubuntu-advantage config module changes until ubuntu-advantage-tools
19.1 publishes to Bionic (LP: #1828641)
  * New upstream snapshot. (LP: #1828637)
- Azure: Return static fallback address as if failed to find endpoint
  [Jason Zions (MSFT)]
- release 19.1
- freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]
- tests: add Eoan release [Paride Legovini]
- cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)]
- replace remaining occurrences of LOG.warn
- DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
- Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
- git tests: no longer show warning about safe yaml. [Scott Moser]
- tools/read-version: handle errors [Chad Miller]
- net/sysconfig: only indicate available on known sysconfig distros
- packages: update rpm specs for new bash completion path
- test_azure: mock util.SeLinuxGuard where needed [Jason Zions (MSFT)]
- setup.py: install bash completion script in new location
- mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder]
- cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]
- Revert "DataSource: move update_events from a class to an instance..."
- Change DataSourceNoCloud to ignore file system label's case.
  [Risto Oikarinen]
- cmd:main.py: Fix missing 'modules-init' key in modes dict
  [Antonio Romito]
- ubuntu_advantage: rewrite cloud-config module
- Azure: Treat _unset network configuration as if it were absent
  [Jason Zions (MSFT)]
- DatasourceAzure: add additional logging for azure datasource [Anh Vo]
- cloud_tests: fix apt_pipelining test-cases
- Azure: Ensure platform random_seed is always serializable as JSON.
  [Jason Zions (MSFT)]
- net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert]
- tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold]
- net: Fix ipv6 static routes when using eni renderer [Raphael Glon]
- Add ubuntu_drivers config module
- doc: Refresh Azure walinuxagent docs
- tox: bump pylint version to latest (2.3.1)
- DataSource: move update_events from a class to an instance attribute
- net/sysconfig: Handle default route setup for dhcp configured NICs
  [Robert Schweikert]
- DataSourceEc2: update RELEASE_BLOCKER to be more accurate

 -- Chad Smith   Fri, 10 May 2019 23:17:50
-0600

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

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

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

Title:
  Xenial, Bionic, Cosmic revert ubuntu-advantage-tools config module
  changes from tip

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  New
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 Cosmic:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  Ubuntu-advantage-tools package version 19 introduced a new command line 
client that is backwards incompatible with previous ubuntu-advantage-tools 
releases.

  Changes in cloud-init 19.1 support only the new ubuntu-advantage-tools
  CLI.

  To avoid breaking the cc_ubuntu_advantage cloud-config module, we need
  to revert changes in cloud-init tip to avoid tracebacks for customers
  in Xenial, Bionic and Cosmic using ubuntu-advantage: declarating in
  their cloud-config.

  Once ubuntu-advantage-tools >= 19 is SRU'd to Xenial, Bionic and
  Cosmic. This debian patch can be dropped.

  [Test Case]
  # Use old ubuntu-advantage cloud-config syntax to enable livepatch on a kvm 
instance to enable livepatch

  Note: there are a number of expected failures
   * Xenial: Bug: #1830154 snap not in $PATH
   * Cosmic: livepatch is not supported on Cosmic
   * Disco: Bug: #1829788  KeyError traceback

  [Test Case]
  cat > pre-disco-ua.yaml <
  EOF

  cat > disco-ua.yaml <
    enable: [livepatch]
  EOF

  cat > setup_proposed.sh 

[Group.of.nepali.translators] [Bug 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
19.1-1-gbaa47854-0ubuntu1~19.04.1

---
cloud-init (19.1-1-gbaa47854-0ubuntu1~19.04.1) disco; urgency=medium

  * New upstream snapshot. (LP: #1828637)
- Azure: Return static fallback address as if failed to find endpoint
  [Jason Zions (MSFT)]
- release 19.1
- freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]
- tests: add Eoan release [Paride Legovini]
- cc_mounts: check if mount -a on no-change fstab path
  [Jason Zions (MSFT)]
- replace remaining occurrences of LOG.warn
- DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
- Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
- git tests: no longer show warning about safe yaml. [Scott Moser]
- tools/read-version: handle errors [Chad Miller]
- net/sysconfig: only indicate available on known sysconfig distros
- packages: update rpm specs for new bash completion path
- test_azure: mock util.SeLinuxGuard where needed
  [Jason Zions (MSFT)]
- setup.py: install bash completion script in new location
- mount_cb: do not pass sync and rw options to mount
  [Gonéri Le Bouder]
- cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]

 -- Chad Smith   Fri, 10 May 2019 21:11:57
-0600

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

Title:
  sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco

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 Cosmic:
  Fix Released
Status in cloud-init source package in Disco:
  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:

  - Azure: Return static fallback address as if failed to find endpoint
    [Jason Zions (MSFT)]
  - cc_mounts: check if mount -a on no-change fstab path [Jason Zions 
(MSFT)]
  - replace remaining occurrences of LOG.warn
  - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
  - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
  - packages: update rpm specs for new bash completion path
  - setup.py: install bash completion script in new location
  - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder]
  - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]
  - Revert "DataSource: move update_events from a class to an instance..."
  - Change DataSourceNoCloud to ignore file system label's case.
    [Risto Oikarinen]
  - cmd:main.py: Fix missing 'modules-init' key in modes dict
    [Antonio Romito]
  - ubuntu_advantage: rewrite cloud-config module
  - Azure: Treat _unset network configuration as if it were absent
    [Jason Zions (MSFT)]
  - DatasourceAzure: add additional logging for azure datasource [Anh Vo]
  - Azure: Ensure platform random_seed is always serializable as JSON.
    [Jason Zions (MSFT)]
  - net: Fix ipv6 static routes when using eni renderer [Raphael Glon]
  - Add ubuntu_drivers config module
  - DataSource: move update_events from a class to an instance attribute

  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
  nocloud-lxd-sru-19.1.1.txt

  DONE: attach automated cloud-init-proposed test artifacts from tests for each 
release with kvm artifacts
  nocloud-kvm-sru-19.1.1.txt

  DONE: attach Solutions Testing team test results for each LTS
  cloud_init_xenial_mass_install.log
  cloud_init_bionic_mass_install.log

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

  * Manual Test Results
  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on ec2 datasource
  ec2-sru-19.1.1.txt

  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on gce datasource
  gce-sru-19.1.1.txt

  DONE: attach manual cloud-init-proposed test artifacts from tests for each 
release on azure datasource
  azure-sru-19.1.1.txt

  [Regression Potential]
  In order to mitigate the regression 

[Group.of.nepali.translators] [Bug 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
19.1-1-gbaa47854-0ubuntu1~18.10.1

---
cloud-init (19.1-1-gbaa47854-0ubuntu1~18.10.1) cosmic; urgency=medium

  * debian/patches/ubuntu-advantage-revert-tip.patch
Revert ubuntu-advantage config module changes until ubuntu-advantage-tools
19.1 publishes to Cosmic (LP: #1828641)
  * New upstream snapshot. (LP: #1828637)
- Azure: Return static fallback address as if failed to find endpoint
  [Jason Zions (MSFT)]
- release 19.1
- freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]
- tests: add Eoan release [Paride Legovini]
- cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)]
- replace remaining occurrences of LOG.warn
- DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
- Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
- git tests: no longer show warning about safe yaml. [Scott Moser]
- tools/read-version: handle errors [Chad Miller]
- net/sysconfig: only indicate available on known sysconfig distros
- packages: update rpm specs for new bash completion path
- test_azure: mock util.SeLinuxGuard where needed [Jason Zions (MSFT)]
- setup.py: install bash completion script in new location
- mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder]
- cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]
- Revert "DataSource: move update_events from a class to an instance..."
- Change DataSourceNoCloud to ignore file system label's case.
  [Risto Oikarinen]
- cmd:main.py: Fix missing 'modules-init' key in modes dict
  [Antonio Romito]
- ubuntu_advantage: rewrite cloud-config module
- Azure: Treat _unset network configuration as if it were absent
  [Jason Zions (MSFT)]
- DatasourceAzure: add additional logging for azure datasource [Anh Vo]
- cloud_tests: fix apt_pipelining test-cases
- Azure: Ensure platform random_seed is always serializable as JSON.
  [Jason Zions (MSFT)]
- net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert]
- tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold]
- net: Fix ipv6 static routes when using eni renderer [Raphael Glon]
- Add ubuntu_drivers config module
- doc: Refresh Azure walinuxagent docs
- tox: bump pylint version to latest (2.3.1)
- DataSource: move update_events from a class to an instance attribute
- net/sysconfig: Handle default route setup for dhcp configured NICs
  [Robert Schweikert]
- DataSourceEc2: update RELEASE_BLOCKER to be more accurate

 -- Chad Smith   Sun, 12 May 2019 20:10:17
-0600

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

Title:
  sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco

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 Cosmic:
  Fix Released
Status in cloud-init source package in Disco:
  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:

  - Azure: Return static fallback address as if failed to find endpoint
    [Jason Zions (MSFT)]
  - cc_mounts: check if mount -a on no-change fstab path [Jason Zions 
(MSFT)]
  - replace remaining occurrences of LOG.warn
  - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
  - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
  - packages: update rpm specs for new bash completion path
  - setup.py: install bash completion script in new location
  - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder]
  - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]
  - Revert "DataSource: move update_events from a class to an instance..."
  - Change DataSourceNoCloud to ignore file system label's case.
    [Risto Oikarinen]
  - cmd:main.py: Fix missing 'modules-init' key in modes dict
    [Antonio Romito]
  - ubuntu_advantage: rewrite cloud-config module
  - Azure: Treat _unset network configuration as if it were absent
    [Jason Zions (MSFT)]
  - DatasourceAzure: add additional logging for azure datasource [Anh Vo]
  - Azure: Ensure platform random_seed is always serializable as JSON.
    [Jason Zions (MSFT)]
  - net: Fix ipv6 static routes when using eni renderer 

[Group.of.nepali.translators] [Bug 1828641] Re: Xenial, Bionic, Cosmic revert ubuntu-advantage-tools config module changes from tip

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package cloud-init -
19.1-1-gbaa47854-0ubuntu1~18.10.1

---
cloud-init (19.1-1-gbaa47854-0ubuntu1~18.10.1) cosmic; urgency=medium

  * debian/patches/ubuntu-advantage-revert-tip.patch
Revert ubuntu-advantage config module changes until ubuntu-advantage-tools
19.1 publishes to Cosmic (LP: #1828641)
  * New upstream snapshot. (LP: #1828637)
- Azure: Return static fallback address as if failed to find endpoint
  [Jason Zions (MSFT)]
- release 19.1
- freebsd: add chpasswd pkg in the image [Gonéri Le Bouder]
- tests: add Eoan release [Paride Legovini]
- cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)]
- replace remaining occurrences of LOG.warn
- DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo]
- Azure: Changes to the Hyper-V KVP Reporter [Anh Vo]
- git tests: no longer show warning about safe yaml. [Scott Moser]
- tools/read-version: handle errors [Chad Miller]
- net/sysconfig: only indicate available on known sysconfig distros
- packages: update rpm specs for new bash completion path
- test_azure: mock util.SeLinuxGuard where needed [Jason Zions (MSFT)]
- setup.py: install bash completion script in new location
- mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder]
- cc_apt_configure: fix typo in apt documentation [Dominic Schlegel]
- Revert "DataSource: move update_events from a class to an instance..."
- Change DataSourceNoCloud to ignore file system label's case.
  [Risto Oikarinen]
- cmd:main.py: Fix missing 'modules-init' key in modes dict
  [Antonio Romito]
- ubuntu_advantage: rewrite cloud-config module
- Azure: Treat _unset network configuration as if it were absent
  [Jason Zions (MSFT)]
- DatasourceAzure: add additional logging for azure datasource [Anh Vo]
- cloud_tests: fix apt_pipelining test-cases
- Azure: Ensure platform random_seed is always serializable as JSON.
  [Jason Zions (MSFT)]
- net/sysconfig: write out SUSE-compatible IPv6 config [Robert Schweikert]
- tox: Update testenv for openSUSE Leap to 15.0 [Thomas Bechtold]
- net: Fix ipv6 static routes when using eni renderer [Raphael Glon]
- Add ubuntu_drivers config module
- doc: Refresh Azure walinuxagent docs
- tox: bump pylint version to latest (2.3.1)
- DataSource: move update_events from a class to an instance attribute
- net/sysconfig: Handle default route setup for dhcp configured NICs
  [Robert Schweikert]
- DataSourceEc2: update RELEASE_BLOCKER to be more accurate

 -- Chad Smith   Sun, 12 May 2019 20:10:17
-0600

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

Title:
  Xenial, Bionic, Cosmic revert ubuntu-advantage-tools config module
  changes from tip

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  New
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 Cosmic:
  Fix Released

Bug description:
  == Begin SRU Template ==
  [Impact]
  Ubuntu-advantage-tools package version 19 introduced a new command line 
client that is backwards incompatible with previous ubuntu-advantage-tools 
releases.

  Changes in cloud-init 19.1 support only the new ubuntu-advantage-tools
  CLI.

  To avoid breaking the cc_ubuntu_advantage cloud-config module, we need
  to revert changes in cloud-init tip to avoid tracebacks for customers
  in Xenial, Bionic and Cosmic using ubuntu-advantage: declarating in
  their cloud-config.

  Once ubuntu-advantage-tools >= 19 is SRU'd to Xenial, Bionic and
  Cosmic. This debian patch can be dropped.

  [Test Case]
  # Use old ubuntu-advantage cloud-config syntax to enable livepatch on a kvm 
instance to enable livepatch

  Note: there are a number of expected failures
   * Xenial: Bug: #1830154 snap not in $PATH
   * Cosmic: livepatch is not supported on Cosmic
   * Disco: Bug: #1829788  KeyError traceback

  [Test Case]
  cat > pre-disco-ua.yaml <
  EOF

  cat > disco-ua.yaml <
    enable: [livepatch]
  EOF

  cat > setup_proposed.sh 

[Group.of.nepali.translators] [Bug 1830635] [NEW] Regression: xenial: Uses apt_pkg.Error, which is only available in later versions

2019-05-27 Thread Julian Andres Klode
Public bug reported:

[Impact]
The last SRU introduced a regression in error handling, where apt_pkg.Error is 
being caught - but that class is not available in xenial - it still uses 
SystemError

[Test case]

Run python3 -c "import apt; apt.Cache().update()" while running apt
update.

You should see:

# 
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
raise LockFailedException("Failed to lock %s" % lockfile)
apt.cache.LockFailedException: Failed to lock /var/lib/apt/lists/lock

Currently you see:
# 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
return self._lock.__enter__()
SystemError: E:Could not get lock /var/lib/apt/lists/lock - open (11: Resource 
temporarily unavailable)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
except apt_pkg.Error as e:
AttributeError: module 'apt_pkg' has no attribute 'Error'

[Regression potential]
It really can't get worse than this. But FWIW: This only affects code paths 
where we could not lock the lists/ or archives/ directory - they currently 
throw the AttributeError, and will then throw LockFailedException again - as 
they did before the SRU.

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: python-apt (Ubuntu Xenial)
 Importance: Undecided
 Status: Triaged

** Description changed:

  [Impact]
  The last SRU introduced a regression in error handling, where apt_pkg.Error 
is being caught - but that class is not available in xenial - it still uses 
SystemError
  
  [Test case]
  
  Run python3 -c "import apt; apt.Cache().update()" while running apt
  update.
  
- 
  You should see:
  
  # 
- Traceback (most recent call last):


  
-   File "", line 1, in 


  
-   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
- raise LockFailedException("Failed to lock %s" % lockfile)
+ Traceback (most recent call last):
+   File "", line 1, in 
+   File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
+ raise LockFailedException("Failed to lock %s" % lockfile)
  apt.cache.LockFailedException: Failed to lock /var/lib/apt/lists/lock
  
  Currently you see:
  # 
  Traceback (most recent call last):
-   File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
- return self._lock.__enter__()
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
+ return self._lock.__enter__()
  SystemError: E:Could not get lock /var/lib/apt/lists/lock - open (11: 
Resource temporarily unavailable)
  
  During handling of the above exception, another exception occurred:
  
  Traceback (most recent call last):
-   File "", line 1, in 
-   File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
- with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
-   File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
- except apt_pkg.Error as e:
+   File "", line 1, in 
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
+ with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
+ except apt_pkg.Error as e:
  AttributeError: module 'apt_pkg' has no attribute 'Error'
  
  [Regression potential]
- It really can't get worse than this.
+ It really can't get worse than this. But FWIW: This only affects code paths 
where we could not lock the lists/ or archives/ directory - they currently 
throw the AttributeError, and will then throw LockFailedException again - as 
they did before the SRU.

** Also affects: python-apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: python-apt (Ubuntu)
   Status: New => Invalid

** Changed in: python-apt (Ubuntu Xenial)
   Status: New => Triaged

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

Title:
  Regression: xenial: Uses 

[Group.of.nepali.translators] [Bug 1827924] Re: Panic or segfault in Samba

2019-05-27 Thread Marc Deslauriers
** Changed in: samba (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Panic or segfault in Samba

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Fix Released
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Bionic:
  Fix Released

Bug description:
  The Samba 'panic action' script, /usr/share/samba/panic-action,
  was called for PID 8336 (/usr/sbin/smbd).

  This means there was a problem with the program, such as a segfault.
  Below is a backtrace for this process generated with gdb, which shows
  the state of the program at the time the error occurred.  The Samba log
  files may contain additional information about the problem.

  If the problem persists, you are encouraged to first install the
  samba-dbg package, which contains the debugging symbols for the Samba
  binaries.  Then submit the provided information as a bug report to
  Ubuntu by visiting this link:
  https://launchpad.net/ubuntu/+source/samba/+filebug

  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7f892084507a in __GI___waitpid (pid=8341, 
stat_loc=stat_loc@entry=0x7ffcd9196290, options=options@entry=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  #0  0x7f892084507a in __GI___waitpid (pid=8341, 
stat_loc=stat_loc@entry=0x7ffcd9196290, options=options@entry=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  #1  0x7f89207bdfbb in do_system (line=) at 
../sysdeps/posix/system.c:148
  #2  0x7f89232698d1 in smb_panic_s3 () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0
  #3  0x7f8923fdcf1f in smb_panic () from 
/usr/lib/x86_64-linux-gnu/libsamba-util.so.0
  #4  0x7f8923fdd136 in ?? () from 
/usr/lib/x86_64-linux-gnu/libsamba-util.so.0
  #5  
  #6  0x7f8923bd5c6f in smbXsrv_session_create () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #7  0x7f8923b6e643 in reply_sesssetup_and_X () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #8  0x7f8923baae67 in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #9  0x7f8923bacbb3 in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #10 0x7f8923bae21c in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #11 0x7f8921efc917 in run_events_poll () from 
/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #12 0x7f8921efcb77 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #13 0x7f8920b46d3d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #14 0x7f8920b46edb in tevent_common_loop_wait () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #15 0x7f8923baf578 in smbd_process () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #16 0x5585ef73fe12 in ?? ()
  #17 0x7f8921efc917 in run_events_poll () from 
/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #18 0x7f8921efcb77 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #19 0x7f8920b46d3d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #20 0x7f8920b46edb in tevent_common_loop_wait () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #21 0x5585ef73e099 in main ()
  A debugging session is active.

  Inferior 1 [process 8336] will be detached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1827924/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-27 Thread Olivier Tilloy
** Bug watch added: gitlab.freedesktop.org/poppler/poppler-data/issues #2
   https://gitlab.freedesktop.org/poppler/poppler-data/issues/2

** Also affects: poppler via
   https://gitlab.freedesktop.org/poppler/poppler-data/issues/2
   Importance: Unknown
   Status: Unknown

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in Poppler:
  Unknown
Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  Fix Committed
Status in libreoffice-l10n source package in Xenial:
  Fix Committed
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gnome-characters source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice-l10n source package in Bionic:
  Fix Committed
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和)

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a 

[Group.of.nepali.translators] [Bug 1818024] Re: linux-gcp 4.15.0-1028.29~16.04.1 ADT test failure with linux-gcp 4.15.0-1028.29~16.04.1

2019-05-27 Thread Kleber Sacilotto de Souza
** Also affects: linux-gcp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: linux-gcp (Ubuntu Xenial)
   Status: New => 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/1818024

Title:
  linux-gcp 4.15.0-1028.29~16.04.1 ADT test failure with linux-gcp
  4.15.0-1028.29~16.04.1

Status in linux-gcp package in Ubuntu:
  New
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux-gcp/20190215_192509_f47b0@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1818024/+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 1829192] Re: linux-aws-hwe: 4.15.0-1040.42~16.04.1 -proposed tracker

2019-05-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829194
- phase: Testing
- phase-changed: Monday, 20. May 2019 17:14 UTC
+ phase: Signoff
+ phase-changed: Monday, 27. May 2019 13:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

Title:
  linux-aws-hwe: 4.15.0-1040.42~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws-hwe package in Ubuntu:
  Invalid
Status in linux-aws-hwe source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829194
  phase: Signoff
  phase-changed: Monday, 27. May 2019 13:43 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829192/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-27 Thread Olivier Tilloy
** Changed in: libreoffice-l10n (Ubuntu Cosmic)
   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/1828884

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

Status in fonts-noto-cjk package in Ubuntu:
  New
Status in gnome-characters package in Ubuntu:
  New
Status in gucharmap package in Ubuntu:
  New
Status in icu package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in mozc package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in poppler-data package in Ubuntu:
  New
Status in unicode-data package in Ubuntu:
  Fix Released
Status in gnome-characters source package in Xenial:
  New
Status in gucharmap source package in Xenial:
  New
Status in icu source package in Xenial:
  New
Status in libreoffice source package in Xenial:
  Fix Committed
Status in libreoffice-l10n source package in Xenial:
  New
Status in mozc source package in Xenial:
  Fix Released
Status in openjdk-8 source package in Xenial:
  New
Status in poppler-data source package in Xenial:
  New
Status in unicode-data source package in Xenial:
  New
Status in fonts-noto-cjk source package in Bionic:
  New
Status in gnome-characters source package in Bionic:
  New
Status in gucharmap source package in Bionic:
  New
Status in icu source package in Bionic:
  New
Status in libreoffice source package in Bionic:
  Fix Committed
Status in libreoffice-l10n source package in Bionic:
  New
Status in mozc source package in Bionic:
  Fix Released
Status in openjdk-8 source package in Bionic:
  New
Status in poppler-data source package in Bionic:
  New
Status in unicode-data source package in Bionic:
  New
Status in fonts-noto-cjk source package in Cosmic:
  New
Status in gnome-characters source package in Cosmic:
  New
Status in gucharmap source package in Cosmic:
  New
Status in icu source package in Cosmic:
  New
Status in libreoffice source package in Cosmic:
  Fix Released
Status in libreoffice-l10n source package in Cosmic:
  Fix Released
Status in mozc source package in Cosmic:
  Fix Released
Status in openjdk-8 source package in Cosmic:
  New
Status in poppler-data source package in Cosmic:
  New
Status in unicode-data source package in Cosmic:
  New
Status in fonts-noto-cjk source package in Disco:
  New
Status in gnome-characters source package in Disco:
  New
Status in gucharmap source package in Disco:
  New
Status in icu source package in Disco:
  New
Status in libreoffice source package in Disco:
  Fix Released
Status in libreoffice-l10n source package in Disco:
  Fix Released
Status in mozc source package in Disco:
  Fix Released
Status in openjdk-8 source package in Disco:
  New
Status in poppler-data source package in Disco:
  New
Status in unicode-data source package in Disco:
  New

Bug description:
  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和)

  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the
  work needed, and general test cases for verifying that things are
  working as expected.

  [Impact]
  Users who run Ubuntu in Japanese.

  [Test cases]

  == Date conversion ==

  On applications that support writing dates in long form, or with
  symbols to denote era (either in X00.00.00 format or in GG1G5G1G
  format  (G- glyph; X- character):

  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"

  == Date output ==

  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"

  === Displaying formatted year for Japanese era with glibc ===

  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)

  == Character maps / font support ==

  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)

  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the
  case, the unicode data supports the new character, but the selected
  font does not 

[Group.of.nepali.translators] [Bug 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

2019-05-27 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   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/1764628

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released

Bug description:
  [IMPACT]

  In xenial lscpu prints the wrong "Hypervisor vendor" and
  "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor
  and virtualization type reported in ubuntu 16.04.04 guest running in
  P8compat mode on P9 boston-LC.

  [TEST]

  Curent output:

  ubuntu@P8lpar3:~$ dpkg -l "*util-linux*"
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  util-linux 2.31.1-0.4ub ppc64el  miscellaneous system utilities
  un  util-linux-loc   (no description available)

  ubuntu@P8lpar3:~$ lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  128
  On-line CPU(s) list: 0-127
  Thread(s) per core:  8
  Core(s) per socket:  1
  Socket(s):   16
  NUMA node(s):2
  Model:   2.1 (pvr 004b 0201)
  Model name:  POWER8 (architected), altivec supported
  Hypervisor vendor: horizontal
  Virtualization type: full
  L1d cache:   64K
  L1i cache:   32K
  NUMA node0 CPU(s):
  NUMA node4 CPU(s):   0-127
  ubuntu@P8lpar3:~$

  Expected Output:

  $ lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):128
  On-line CPU(s) list:   0-127
  Thread(s) per core:8
  Core(s) per socket:1
  Socket(s): 16
  NUMA node(s):  2
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8 (architected), altivec supported
  Hypervisor vendor: pHyp
  Virtualization type:   para
  L1d cache: 64K
  L1i cache: 32K
  NUMA node0 CPU(s):
  NUMA node4 CPU(s): 0-127

  [Potential Regression]
  The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() 
this could introduce potential regression in platforms  that has incorrect DMI 
information.

  [Other Info]
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1

  Stack trace output:
   no

  Oops output:
   no

  We test what is coming along with distro. If you are not able to see
  issue with : https://launchpad.net/ubuntu/+source/util-
  linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+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 1829193] Re: linux-aws: 4.4.0-1084.94 -proposed tracker

2019-05-27 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829209
- phase: Testing
- phase-changed: Tuesday, 21. May 2019 15:06 UTC
+ phase: Signoff
+ phase-changed: Monday, 27. May 2019 13:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

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

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1829209
  phase: Signoff
  phase-changed: Monday, 27. May 2019 13:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829193/+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 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.7

---
util-linux (2.27.1-6ubuntu3.7) xenial; urgency=medium

  * d/patches/lscpu-cleanup-DMI-detection-return-codes.patch:
Cherry pick upstream patch to fix correctly identifying
virtualization type.
LP: #1764628

 -- Manoj Iyer   Tue, 02 Apr 2019 17:20:29
-0500

** Changed in: util-linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released

Bug description:
  [IMPACT]

  In xenial lscpu prints the wrong "Hypervisor vendor" and
  "Virtualization type" on PowerVM or KVM systems. Incorrect hypervisor
  and virtualization type reported in ubuntu 16.04.04 guest running in
  P8compat mode on P9 boston-LC.

  [TEST]

  Curent output:

  ubuntu@P8lpar3:~$ dpkg -l "*util-linux*"
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version  Architecture Description
  +++-==---=
  ii  util-linux 2.31.1-0.4ub ppc64el  miscellaneous system utilities
  un  util-linux-loc   (no description available)

  ubuntu@P8lpar3:~$ lscpu
  Architecture:ppc64le
  Byte Order:  Little Endian
  CPU(s):  128
  On-line CPU(s) list: 0-127
  Thread(s) per core:  8
  Core(s) per socket:  1
  Socket(s):   16
  NUMA node(s):2
  Model:   2.1 (pvr 004b 0201)
  Model name:  POWER8 (architected), altivec supported
  Hypervisor vendor: horizontal
  Virtualization type: full
  L1d cache:   64K
  L1i cache:   32K
  NUMA node0 CPU(s):
  NUMA node4 CPU(s):   0-127
  ubuntu@P8lpar3:~$

  Expected Output:

  $ lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):128
  On-line CPU(s) list:   0-127
  Thread(s) per core:8
  Core(s) per socket:1
  Socket(s): 16
  NUMA node(s):  2
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8 (architected), altivec supported
  Hypervisor vendor: pHyp
  Virtualization type:   para
  L1d cache: 64K
  L1i cache: 32K
  NUMA node0 CPU(s):
  NUMA node4 CPU(s): 0-127

  [Potential Regression]
  The fix changes the logic to how lscpu-dmi returns from read_hypervisor_dmi() 
this could introduce potential regression in platforms  that has incorrect DMI 
information.

  [Other Info]
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = boston-LC

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1

  Stack trace output:
   no

  Oops output:
   no

  We test what is coming along with distro. If you are not able to see
  issue with : https://launchpad.net/ubuntu/+source/util-
  linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+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 1827924] Re: Panic or segfault in Samba

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package samba - 2:4.7.6+dfsg~ubuntu-
0ubuntu2.11

---
samba (2:4.7.6+dfsg~ubuntu-0ubuntu2.11) bionic-security; urgency=medium

  * SECURITY REGRESSION: panics following recent update (LP: #1827924)
- debian/patches/bug13315.patch: do not crash if we fail to init the
  session table in source3/smbd/negprot.c.

 -- Marc Deslauriers   Thu, 23 May 2019
08:06:42 -0400

** Changed in: samba (Ubuntu Bionic)
   Status: Confirmed => Fix Released

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

Title:
  Panic or segfault in Samba

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Confirmed
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Bionic:
  Fix Released

Bug description:
  The Samba 'panic action' script, /usr/share/samba/panic-action,
  was called for PID 8336 (/usr/sbin/smbd).

  This means there was a problem with the program, such as a segfault.
  Below is a backtrace for this process generated with gdb, which shows
  the state of the program at the time the error occurred.  The Samba log
  files may contain additional information about the problem.

  If the problem persists, you are encouraged to first install the
  samba-dbg package, which contains the debugging symbols for the Samba
  binaries.  Then submit the provided information as a bug report to
  Ubuntu by visiting this link:
  https://launchpad.net/ubuntu/+source/samba/+filebug

  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7f892084507a in __GI___waitpid (pid=8341, 
stat_loc=stat_loc@entry=0x7ffcd9196290, options=options@entry=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  #0  0x7f892084507a in __GI___waitpid (pid=8341, 
stat_loc=stat_loc@entry=0x7ffcd9196290, options=options@entry=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  #1  0x7f89207bdfbb in do_system (line=) at 
../sysdeps/posix/system.c:148
  #2  0x7f89232698d1 in smb_panic_s3 () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0
  #3  0x7f8923fdcf1f in smb_panic () from 
/usr/lib/x86_64-linux-gnu/libsamba-util.so.0
  #4  0x7f8923fdd136 in ?? () from 
/usr/lib/x86_64-linux-gnu/libsamba-util.so.0
  #5  
  #6  0x7f8923bd5c6f in smbXsrv_session_create () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #7  0x7f8923b6e643 in reply_sesssetup_and_X () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #8  0x7f8923baae67 in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #9  0x7f8923bacbb3 in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #10 0x7f8923bae21c in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #11 0x7f8921efc917 in run_events_poll () from 
/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #12 0x7f8921efcb77 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #13 0x7f8920b46d3d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #14 0x7f8920b46edb in tevent_common_loop_wait () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #15 0x7f8923baf578 in smbd_process () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #16 0x5585ef73fe12 in ?? ()
  #17 0x7f8921efc917 in run_events_poll () from 
/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #18 0x7f8921efcb77 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #19 0x7f8920b46d3d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #20 0x7f8920b46edb in tevent_common_loop_wait () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #21 0x5585ef73e099 in main ()
  A debugging session is active.

  Inferior 1 [process 8336] will be detached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1827924/+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 1827924] Re: Panic or segfault in Samba

2019-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package samba - 2:4.3.11+dfsg-
0ubuntu0.16.04.21

---
samba (2:4.3.11+dfsg-0ubuntu0.16.04.21) xenial-security; urgency=medium

  * SECURITY REGRESSION: panics following recent update (LP: #1827924)
- debian/patches/bug13315.patch: do not crash if we fail to init the
  session table in source3/smbd/negprot.c.

 -- Marc Deslauriers   Thu, 23 May 2019
08:08:58 -0400

** Changed in: samba (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  Panic or segfault in Samba

Status in samba:
  Unknown
Status in samba package in Ubuntu:
  Confirmed
Status in samba source package in Xenial:
  Fix Released
Status in samba source package in Bionic:
  Confirmed

Bug description:
  The Samba 'panic action' script, /usr/share/samba/panic-action,
  was called for PID 8336 (/usr/sbin/smbd).

  This means there was a problem with the program, such as a segfault.
  Below is a backtrace for this process generated with gdb, which shows
  the state of the program at the time the error occurred.  The Samba log
  files may contain additional information about the problem.

  If the problem persists, you are encouraged to first install the
  samba-dbg package, which contains the debugging symbols for the Samba
  binaries.  Then submit the provided information as a bug report to
  Ubuntu by visiting this link:
  https://launchpad.net/ubuntu/+source/samba/+filebug

  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7f892084507a in __GI___waitpid (pid=8341, 
stat_loc=stat_loc@entry=0x7ffcd9196290, options=options@entry=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  #0  0x7f892084507a in __GI___waitpid (pid=8341, 
stat_loc=stat_loc@entry=0x7ffcd9196290, options=options@entry=0) at 
../sysdeps/unix/sysv/linux/waitpid.c:29
  #1  0x7f89207bdfbb in do_system (line=) at 
../sysdeps/posix/system.c:148
  #2  0x7f89232698d1 in smb_panic_s3 () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbregistry.so.0
  #3  0x7f8923fdcf1f in smb_panic () from 
/usr/lib/x86_64-linux-gnu/libsamba-util.so.0
  #4  0x7f8923fdd136 in ?? () from 
/usr/lib/x86_64-linux-gnu/libsamba-util.so.0
  #5  
  #6  0x7f8923bd5c6f in smbXsrv_session_create () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #7  0x7f8923b6e643 in reply_sesssetup_and_X () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #8  0x7f8923baae67 in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #9  0x7f8923bacbb3 in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #10 0x7f8923bae21c in ?? () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #11 0x7f8921efc917 in run_events_poll () from 
/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #12 0x7f8921efcb77 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #13 0x7f8920b46d3d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #14 0x7f8920b46edb in tevent_common_loop_wait () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #15 0x7f8923baf578 in smbd_process () from 
/usr/lib/x86_64-linux-gnu/samba/libsmbd-base.so.0
  #16 0x5585ef73fe12 in ?? ()
  #17 0x7f8921efc917 in run_events_poll () from 
/usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #18 0x7f8921efcb77 in ?? () from /usr/lib/x86_64-linux-gnu/libsmbconf.so.0
  #19 0x7f8920b46d3d in _tevent_loop_once () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #20 0x7f8920b46edb in tevent_common_loop_wait () from 
/usr/lib/x86_64-linux-gnu/libtevent.so.0
  #21 0x5585ef73e099 in main ()
  A debugging session is active.

  Inferior 1 [process 8336] will be detached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/1827924/+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 1830268] Re: libvirt caches nested vmx capability (in domcapabilities)

2019-05-27 Thread Christian Ehrhardt 
Currently libvirt tracks these elements to consider refreshing (they are
stored in the capability XMLs themselves).


  1558846766
  1557980947
  400

There are other ctime based caches as well like virQEMUCapsKVMUsable for
/dev/kvm.

The checker for the main caps is virQEMUCapsIsValid and so far checks:
- libvirt ctime (binary)
- libvirt version (internal build time value)
- qemu bin ctime (binary)
- do not not go further down if on emulated arch (won't change)
- /dev/kvm got accessible since last caching (DAC)
- /dev/kvm got unavailable since last caching (DAC)
- microcode changed (cpuinfo)
- kernel version changed
- Nesting is now supported

The latter sounds familiar right?
=> 
https://libvirt.org/git/?p=libvirt.git;a=commit;h=b183a75319b90d0af5512be513743e1eab950612

That is in 5.0 which means =>Disco already.
Lets check how backportable that is ...

** Also affects: libvirt (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

** Also affects: libvirt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: libvirt (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  libvirt caches nested vmx capability (in domcapabilities)

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  New
Status in libvirt source package in Bionic:
  New
Status in libvirt source package in Cosmic:
  New

Bug description:
  [impact]

  libvirt caches the 'nested vmx' capability of the host and does not
  update that even if the host's capability to handle nested vmx
  changes.  Having this domcapability missing means no guests are able
  to start any nested, kvm-accelerated, guests.  Additionally, since
  openstack live migration requires matching cpu features, this makes
  migrating guests that do have vmx enabled impossible to hosts where
  libvirt thinks nested vmx is disabled.

  Once the kernel module (kvm_intel) is reloaded with 'nested' enabled,
  libvirt does not update its domcapabilities cache, even over a
  libvirtd restart, or even over an entire system reboot.  Only certain
  conditions cause libvirt to update its capabilities cache (possibly
  libvirt upgrade, or qemu upgrade, or kernel upgrade...I haven't
  verified any of those yet)

  libvirt creates caches for its domcapabilities at 
/var/cache/libvirt/qemu/capabilities/.
  removing the cache xml files there and restarting libvirtd will cause the 
caches to be recreated with the correct current values.

  [test case]

  check the kvm_intel module nested parameter:
  $ cat /sys/module/kvm_intel/parameters/nested
  Y

  it can be Y or N.  make sure libvirt agrees with the current setting:
  $ virsh domcapabilities | grep vmx
    

  if 'nested' is Y, domcapabilities should include a vmx feature line;
  if 'nested' is N, it should have no output (i.e. vmx not supported in
  guests).

  Then, change the kernel nested setting, and re-check domcapabilities.
  Restarting libvirtd doesn't update the cache, and even rebooting the
  entire system doesn't update the cache.

  $ virsh domcapabilities | grep vmx
  $ cat /sys/module/kvm_intel/parameters/nested
  N
  $ sudo rmmod kvm_intel
  $ sudo modprobe kvm_intel nested=1
  $ cat /sys/module/kvm_intel/parameters/nested
  Y
  $ virsh domcapabilities | grep vmx
  $ sudo systemctl restart libvirtd
  $ virsh domcapabilities | grep vmx
  $

  [regression potential]

  TBD, but this should only require better invalidating of the caps
  cache, which seems very low for any regression potential.  More
  overhead to regenerate the cache more often maybe.

  [other info]

  related RH bugs, though no changes appear to have resulted from either:
  https://bugzilla.redhat.com/show_bug.cgi?id=1474874
  https://bugzilla.redhat.com/show_bug.cgi?id=1650950

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1830268/+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