[Group.of.nepali.translators] [Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
This bug was fixed in the package landscape-client -
16.03-0ubuntu2.16.04.5
---
landscape-client (16.03-0ubuntu2.16.04.5) xenial; urgency=medium
* debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor (LP: #1788219)
* Fixes for release-upgrade (LP: #1699179).
- debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu-
release-upgrader is running before apt-update. (LP: #1699179)
- debian/patches/release-upgrade-success.patch: Enable landscape-client to
survive trusty upgrade. (LP: #1670291)
- debian/patches/post-upgrade-reboot.patch: Force reboot operation in
case systemd fails. (LP: #1670291)
* debian/patches/1616116-resync-loop.patch:
Clear hash id database on package resync. (LP: #1616116)
-- Simon Poirier Tue, 27 Nov 2018
09:24:22 -0500
** Changed in: landscape-client (Ubuntu Trusty)
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/1616116
Title:
Unrecoverable resyncs if DB is restored from backup
Status in Landscape Client:
Fix Committed
Status in landscape-client package in Ubuntu:
Fix Released
Status in landscape-client source package in Trusty:
Fix Released
Status in landscape-client source package in Xenial:
Fix Released
Status in landscape-client source package in Bionic:
Fix Released
Status in landscape-client source package in Cosmic:
Fix Released
Bug description:
[Impact]
* In some cases generally involving backups/restore, client would get
inconsistent package data and keep that data upon resync, thus getting
stuck in a resync loop. This usually gets noticed through the stress
it adds on the server and though logs which grow abnormally.
[Test Case]
* deploy landscape-server quickstart from ppa:landscape/18.03
* register client against server. wait for package info
* pg_dumpall
* add a repo and wait for new package to show on in landscape.
* restore the postgres backup.
* run ./scripts/hash_id_databases.sh from the server to complete
the restore.
* trigger a package install from the new repo to create some package
info to update
* client should resync once then will re-fetch hash on the next run.
[Regression Potential]
* Modified code is used only during resync operations and removes
cached data when the client state is deemed inconsistent.
* In the unlikely event the code is called outside of the expected
cases, the end result would be limited to the package-monitor
having to re-download the hash-id databases, which shouldn't
cause issues as that is the behaviour at client registration.
[Other Info]
* Other cases than server restores have been noticed to generate the
bug but they are far less common.
[Original description]
Landscape with live clients cannot handle a DB restore to a point in
the past.
The scenario is Landscape running as usual, with live clients,
restoring to a DB backup taken in the past. After the service ir
brought up again with this data, clients will start resyncing and
becoming wedged with all sorts of tracebacks on the message server.
I left such a scenario running overnight, hoping that eventually the
resyncs would settle down and everything recover, but that didn't
happen. The resyncs continued, in the packages scope.
An interesting one in particular was this:
Aug 22 21:46:26 message-server-2 ERR Error handling message
'operation-result' for computer 104: {'status': 6, 'timestamp': 1471901963,
'result-text': u'Mon Aug 22 21:39:23 UTC 2016\n', 'api': '3.3', 'operation-id':
533, 'type': 'operation-result'}#012Traceback (most recent call last):#012
File "/opt/canonical/landscape/canonical/landscape/message/apis.py", line 358,
in _process_messages#012self.handle(message["type"], message)#012 File
"/opt/canonical/landscape/canonical/message/api.py", line 66, in handle#012
return handler(type, body)#012 File
"/opt/canonical/landscape/canonical/message/handler.py", line 30, in
__call__#012return function(self.message_api, type, body)#012 File
"/opt/canonical/landscape/canonical/lib/arguments.py", line 79, in
replacement#012return original(*new_args, **new_kwargs)#012 File
"/opt/canonical/landscape/canonical/landscape/message/handlers/activity.py",
line 32, in handle_activity_result#012activity.succeed(code=result_code,
text=result_text)#012AttributeError: 'NoneType' object has no attribute
'succeed'
That was about an activity that had been delivered already, but did
not exist in the restored DB.
To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions
___
Mailing list:
[Group.of.nepali.translators] [Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
This bug was fixed in the package landscape-client - 18.01-0ubuntu3.2
---
landscape-client (18.01-0ubuntu3.2) bionic; urgency=medium
* debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor. (LP: #1788219)
* Fixes for release-upgrade:
- debian/patches/release-upgrade-success.patch: Enable landscape-client to
survive trusty upgrade. (LP: #1670291)
- debian/patches/post-upgrade-reboot.patch: Force reboot operation in
case systemd fails. (LP: #1670291)
* debian/patches/unicode-tags-script.patch: Permit environments
containing unicode chars for script execution. (LP: #1765518)
* debian/patches/1616116-resync-loop.patch:
Clear hash id database on package resync. (LP: #1616116)
-- Simon Poirier Tue, 27 Nov 2018
09:24:22 -0500
** Changed in: landscape-client (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: landscape-client (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/1616116
Title:
Unrecoverable resyncs if DB is restored from backup
Status in Landscape Client:
Fix Committed
Status in landscape-client package in Ubuntu:
Fix Released
Status in landscape-client source package in Trusty:
Fix Released
Status in landscape-client source package in Xenial:
Fix Released
Status in landscape-client source package in Bionic:
Fix Released
Status in landscape-client source package in Cosmic:
Fix Released
Bug description:
[Impact]
* In some cases generally involving backups/restore, client would get
inconsistent package data and keep that data upon resync, thus getting
stuck in a resync loop. This usually gets noticed through the stress
it adds on the server and though logs which grow abnormally.
[Test Case]
* deploy landscape-server quickstart from ppa:landscape/18.03
* register client against server. wait for package info
* pg_dumpall
* add a repo and wait for new package to show on in landscape.
* restore the postgres backup.
* run ./scripts/hash_id_databases.sh from the server to complete
the restore.
* trigger a package install from the new repo to create some package
info to update
* client should resync once then will re-fetch hash on the next run.
[Regression Potential]
* Modified code is used only during resync operations and removes
cached data when the client state is deemed inconsistent.
* In the unlikely event the code is called outside of the expected
cases, the end result would be limited to the package-monitor
having to re-download the hash-id databases, which shouldn't
cause issues as that is the behaviour at client registration.
[Other Info]
* Other cases than server restores have been noticed to generate the
bug but they are far less common.
[Original description]
Landscape with live clients cannot handle a DB restore to a point in
the past.
The scenario is Landscape running as usual, with live clients,
restoring to a DB backup taken in the past. After the service ir
brought up again with this data, clients will start resyncing and
becoming wedged with all sorts of tracebacks on the message server.
I left such a scenario running overnight, hoping that eventually the
resyncs would settle down and everything recover, but that didn't
happen. The resyncs continued, in the packages scope.
An interesting one in particular was this:
Aug 22 21:46:26 message-server-2 ERR Error handling message
'operation-result' for computer 104: {'status': 6, 'timestamp': 1471901963,
'result-text': u'Mon Aug 22 21:39:23 UTC 2016\n', 'api': '3.3', 'operation-id':
533, 'type': 'operation-result'}#012Traceback (most recent call last):#012
File "/opt/canonical/landscape/canonical/landscape/message/apis.py", line 358,
in _process_messages#012self.handle(message["type"], message)#012 File
"/opt/canonical/landscape/canonical/message/api.py", line 66, in handle#012
return handler(type, body)#012 File
"/opt/canonical/landscape/canonical/message/handler.py", line 30, in
__call__#012return function(self.message_api, type, body)#012 File
"/opt/canonical/landscape/canonical/lib/arguments.py", line 79, in
replacement#012return original(*new_args, **new_kwargs)#012 File
"/opt/canonical/landscape/canonical/landscape/message/handlers/activity.py",
line 32, in handle_activity_result#012activity.succeed(code=result_code,
text=result_text)#012AttributeError: 'NoneType' object has no attribute
'succeed'
That was about an activity that had been delivered already, but did
not exist in the restored DB.
To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions
[Group.of.nepali.translators] [Bug 1616116] Re: Unrecoverable resyncs if DB is restored from backup
This bug was fixed in the package landscape-client - 18.01-0ubuntu4.1
---
landscape-client (18.01-0ubuntu4.1) cosmic; urgency=medium
* debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor. (LP: #1788219)
* Fixes for release-upgrade:
- debian/patches/release-upgrade-success.patch: Enable landscape-client to
survive trusty upgrade. (LP: #1670291)
- debian/patches/post-upgrade-reboot.patch: Force reboot operation in
case systemd fails. (LP: #1670291)
* debian/patches/unicode-tags-script.patch: Permit environments
containing unicode chars for script execution. (LP: #1765518)
* debian/patches/1616116-resync-loop.patch:
Clear hash id database on package resync. (LP: #1616116)
-- Simon Poirier Tue, 27 Nov 2018
09:24:22 -0500
** Changed in: landscape-client (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/1616116
Title:
Unrecoverable resyncs if DB is restored from backup
Status in Landscape Client:
Fix Committed
Status in landscape-client package in Ubuntu:
Fix Released
Status in landscape-client source package in Trusty:
Fix Released
Status in landscape-client source package in Xenial:
Fix Released
Status in landscape-client source package in Bionic:
Fix Released
Status in landscape-client source package in Cosmic:
Fix Released
Bug description:
[Impact]
* In some cases generally involving backups/restore, client would get
inconsistent package data and keep that data upon resync, thus getting
stuck in a resync loop. This usually gets noticed through the stress
it adds on the server and though logs which grow abnormally.
[Test Case]
* deploy landscape-server quickstart from ppa:landscape/18.03
* register client against server. wait for package info
* pg_dumpall
* add a repo and wait for new package to show on in landscape.
* restore the postgres backup.
* run ./scripts/hash_id_databases.sh from the server to complete
the restore.
* trigger a package install from the new repo to create some package
info to update
* client should resync once then will re-fetch hash on the next run.
[Regression Potential]
* Modified code is used only during resync operations and removes
cached data when the client state is deemed inconsistent.
* In the unlikely event the code is called outside of the expected
cases, the end result would be limited to the package-monitor
having to re-download the hash-id databases, which shouldn't
cause issues as that is the behaviour at client registration.
[Other Info]
* Other cases than server restores have been noticed to generate the
bug but they are far less common.
[Original description]
Landscape with live clients cannot handle a DB restore to a point in
the past.
The scenario is Landscape running as usual, with live clients,
restoring to a DB backup taken in the past. After the service ir
brought up again with this data, clients will start resyncing and
becoming wedged with all sorts of tracebacks on the message server.
I left such a scenario running overnight, hoping that eventually the
resyncs would settle down and everything recover, but that didn't
happen. The resyncs continued, in the packages scope.
An interesting one in particular was this:
Aug 22 21:46:26 message-server-2 ERR Error handling message
'operation-result' for computer 104: {'status': 6, 'timestamp': 1471901963,
'result-text': u'Mon Aug 22 21:39:23 UTC 2016\n', 'api': '3.3', 'operation-id':
533, 'type': 'operation-result'}#012Traceback (most recent call last):#012
File "/opt/canonical/landscape/canonical/landscape/message/apis.py", line 358,
in _process_messages#012self.handle(message["type"], message)#012 File
"/opt/canonical/landscape/canonical/message/api.py", line 66, in handle#012
return handler(type, body)#012 File
"/opt/canonical/landscape/canonical/message/handler.py", line 30, in
__call__#012return function(self.message_api, type, body)#012 File
"/opt/canonical/landscape/canonical/lib/arguments.py", line 79, in
replacement#012return original(*new_args, **new_kwargs)#012 File
"/opt/canonical/landscape/canonical/landscape/message/handlers/activity.py",
line 32, in handle_activity_result#012activity.succeed(code=result_code,
text=result_text)#012AttributeError: 'NoneType' object has no attribute
'succeed'
That was about an activity that had been delivered already, but did
not exist in the restored DB.
To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/1616116/+subscriptions
___
Mailing list:
[Group.of.nepali.translators] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
This bug was fixed in the package landscape-client - 18.01-0ubuntu3.2 --- landscape-client (18.01-0ubuntu3.2) bionic; urgency=medium * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix hypervisor. (LP: #1788219) * Fixes for release-upgrade: - debian/patches/release-upgrade-success.patch: Enable landscape-client to survive trusty upgrade. (LP: #1670291) - debian/patches/post-upgrade-reboot.patch: Force reboot operation in case systemd fails. (LP: #1670291) * debian/patches/unicode-tags-script.patch: Permit environments containing unicode chars for script execution. (LP: #1765518) * debian/patches/1616116-resync-loop.patch: Clear hash id database on package resync. (LP: #1616116) -- Simon Poirier Tue, 27 Nov 2018 09:24:22 -0500 ** Changed in: landscape-client (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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in systemd source package in Trusty: New Status in landscape-client source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.5 --- landscape-client (16.03-0ubuntu2.16.04.5) xenial; urgency=medium * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix hypervisor (LP: #1788219) * Fixes for release-upgrade (LP: #1699179). - debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu- release-upgrader is running before apt-update. (LP: #1699179) - debian/patches/release-upgrade-success.patch: Enable landscape-client to survive trusty upgrade. (LP: #1670291) - debian/patches/post-upgrade-reboot.patch: Force reboot operation in case systemd fails. (LP: #1670291) * debian/patches/1616116-resync-loop.patch: Clear hash id database on package resync. (LP: #1616116) -- Simon Poirier Tue, 27 Nov 2018 09:24:22 -0500 ** Changed in: landscape-client (Ubuntu Trusty) 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in systemd source package in Trusty: New Status in landscape-client source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1699179] Re: PackageReporter kicks in during do-release-upgrade
This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.5 --- landscape-client (16.03-0ubuntu2.16.04.5) xenial; urgency=medium * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix hypervisor (LP: #1788219) * Fixes for release-upgrade (LP: #1699179). - debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu- release-upgrader is running before apt-update. (LP: #1699179) - debian/patches/release-upgrade-success.patch: Enable landscape-client to survive trusty upgrade. (LP: #1670291) - debian/patches/post-upgrade-reboot.patch: Force reboot operation in case systemd fails. (LP: #1670291) * debian/patches/1616116-resync-loop.patch: Clear hash id database on package resync. (LP: #1616116) -- Simon Poirier Tue, 27 Nov 2018 09:24:22 -0500 ** Changed in: landscape-client (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/1699179 Title: PackageReporter kicks in during do-release-upgrade Status in Landscape Client: Fix Released Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Artful: Won't Fix Status in landscape-client source package in Bionic: Fix Released Bug description: [Impact] * This issue affects users of the release-upgrade feature of landscape. * Landscape package monitor would previously race during an upgrade and possibly grab apt locks, thus making the upgrade fail. * The fix adds checks during package operations to make sure a release upgrade is not in progresss. [Test Case] * in /etc/landscape/client.conf , set "apt_update_interval=1800" and "log_level=debug" and restart the client. * Launch a release upgrade from landscape-server. Look for messages in the package-monitor logs stating "conditions not met" [Regression Potential] * Unlikely, as this has already been released to newer ubuntu releases and is fairly well tested. * Any issue with related changes would likely only affect the client getting new package info, but won't affect other functionality. [Original description] Affected release: Ubuntu 14.04.5 Version of package: 14.12-0ubuntu5.14.04 Steps to reproduce: 1. Run do-release-upgrade to upgrade to 16.04.2. 2. Trigger the package-reporter to kick in while do-release-upgrade is working but not having the package database locked. 3. Package database is locked by package-reporter, do-release-upgrade fails to access it and exits. Expected result: Landscape detects that there's an release upgrade in progress and will wait for it to finish. Actual result: PackageReporter locks the apt database, do-release-upgrade cannot access it, exits with an error and may leave the system in an unusable state. * Link to Dariusz's PR on GitHub: https://github.com/CanonicalLtd/landscape-client/pull/14 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1699179/+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 1699179] Re: PackageReporter kicks in during do-release-upgrade
This bug was fixed in the package landscape-client - 14.12-0ubuntu6.14.04.4 --- landscape-client (14.12-0ubuntu6.14.04.4) trusty; urgency=medium * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix hypervisor. (LP: #1788219) * Fixes for release-upgrade (LP: #1699179). - debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu- release-upgrader is running before apt-update. (LP: #1699179) - debian/patches/release-upgrade-success.patch: Enable landscape-client to survive trusty upgrade. (LP: #1670291) - debian/patches/post-upgrade-reboot.patch: Force reboot operation in case systemd fails. (LP: #1670291) * debian/patches/1616116-resync-loop.patch: Clear hash id database on package resync. (LP: #1616116) -- Simon Poirier Tue, 27 Nov 2018 09:24:22 -0500 ** Changed in: landscape-client (Ubuntu Trusty) 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/1699179 Title: PackageReporter kicks in during do-release-upgrade Status in Landscape Client: Fix Released Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Artful: Won't Fix Status in landscape-client source package in Bionic: Fix Released Bug description: [Impact] * This issue affects users of the release-upgrade feature of landscape. * Landscape package monitor would previously race during an upgrade and possibly grab apt locks, thus making the upgrade fail. * The fix adds checks during package operations to make sure a release upgrade is not in progresss. [Test Case] * in /etc/landscape/client.conf , set "apt_update_interval=1800" and "log_level=debug" and restart the client. * Launch a release upgrade from landscape-server. Look for messages in the package-monitor logs stating "conditions not met" [Regression Potential] * Unlikely, as this has already been released to newer ubuntu releases and is fairly well tested. * Any issue with related changes would likely only affect the client getting new package info, but won't affect other functionality. [Original description] Affected release: Ubuntu 14.04.5 Version of package: 14.12-0ubuntu5.14.04 Steps to reproduce: 1. Run do-release-upgrade to upgrade to 16.04.2. 2. Trigger the package-reporter to kick in while do-release-upgrade is working but not having the package database locked. 3. Package database is locked by package-reporter, do-release-upgrade fails to access it and exits. Expected result: Landscape detects that there's an release upgrade in progress and will wait for it to finish. Actual result: PackageReporter locks the apt database, do-release-upgrade cannot access it, exits with an error and may leave the system in an unusable state. * Link to Dariusz's PR on GitHub: https://github.com/CanonicalLtd/landscape-client/pull/14 To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1699179/+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 1788219] Re: vm_type detection for nutanix cloud instances
This bug was fixed in the package landscape-client - 16.03-0ubuntu2.16.04.5 --- landscape-client (16.03-0ubuntu2.16.04.5) xenial; urgency=medium * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix hypervisor (LP: #1788219) * Fixes for release-upgrade (LP: #1699179). - debian/patches/1699179-release-upgrade-check.diff: Check if ubuntu- release-upgrader is running before apt-update. (LP: #1699179) - debian/patches/release-upgrade-success.patch: Enable landscape-client to survive trusty upgrade. (LP: #1670291) - debian/patches/post-upgrade-reboot.patch: Force reboot operation in case systemd fails. (LP: #1670291) * debian/patches/1616116-resync-loop.patch: Clear hash id database on package resync. (LP: #1616116) -- Simon Poirier Tue, 27 Nov 2018 09:24:22 -0500 ** Changed in: landscape-client (Ubuntu Trusty) 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/1788219 Title: vm_type detection for nutanix cloud instances Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in landscape-client source package in Cosmic: Fix Released Bug description: [Impact] * The dmi id for Nutanix cloud instances was added to the detection list for it to be properly detected as KVM. [Test Case] * create a vm (uvt-kvm create --no-start vm_name release=xenial) * virsh edit vm_name (and create or update sysinfo manufacturer to be "nutanix", like https://pastebin.ubuntu.com/p/C5mkc2B7rx/) * install landscape-client/common and call landscape-config * see the computer is detected as kvm [Regression Potential] * The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors. [Other Info] * Patches are already in the upstreams trunk. * Changes have been tested by some affected users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+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 1788219] Re: vm_type detection for nutanix cloud instances
This bug was fixed in the package landscape-client - 18.01-0ubuntu3.2 --- landscape-client (18.01-0ubuntu3.2) bionic; urgency=medium * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix hypervisor. (LP: #1788219) * Fixes for release-upgrade: - debian/patches/release-upgrade-success.patch: Enable landscape-client to survive trusty upgrade. (LP: #1670291) - debian/patches/post-upgrade-reboot.patch: Force reboot operation in case systemd fails. (LP: #1670291) * debian/patches/unicode-tags-script.patch: Permit environments containing unicode chars for script execution. (LP: #1765518) * debian/patches/1616116-resync-loop.patch: Clear hash id database on package resync. (LP: #1616116) -- Simon Poirier Tue, 27 Nov 2018 09:24:22 -0500 ** Changed in: landscape-client (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: landscape-client (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/1788219 Title: vm_type detection for nutanix cloud instances Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in landscape-client source package in Cosmic: Fix Released Bug description: [Impact] * The dmi id for Nutanix cloud instances was added to the detection list for it to be properly detected as KVM. [Test Case] * create a vm (uvt-kvm create --no-start vm_name release=xenial) * virsh edit vm_name (and create or update sysinfo manufacturer to be "nutanix", like https://pastebin.ubuntu.com/p/C5mkc2B7rx/) * install landscape-client/common and call landscape-config * see the computer is detected as kvm [Regression Potential] * The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors. [Other Info] * Patches are already in the upstreams trunk. * Changes have been tested by some affected users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+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 1788219] Re: vm_type detection for nutanix cloud instances
This bug was fixed in the package landscape-client - 18.01-0ubuntu4.1 --- landscape-client (18.01-0ubuntu4.1) cosmic; urgency=medium * debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix hypervisor. (LP: #1788219) * Fixes for release-upgrade: - debian/patches/release-upgrade-success.patch: Enable landscape-client to survive trusty upgrade. (LP: #1670291) - debian/patches/post-upgrade-reboot.patch: Force reboot operation in case systemd fails. (LP: #1670291) * debian/patches/unicode-tags-script.patch: Permit environments containing unicode chars for script execution. (LP: #1765518) * debian/patches/1616116-resync-loop.patch: Clear hash id database on package resync. (LP: #1616116) -- Simon Poirier Tue, 27 Nov 2018 09:24:22 -0500 ** Changed in: landscape-client (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/1788219 Title: vm_type detection for nutanix cloud instances Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in landscape-client source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in landscape-client source package in Cosmic: Fix Released Bug description: [Impact] * The dmi id for Nutanix cloud instances was added to the detection list for it to be properly detected as KVM. [Test Case] * create a vm (uvt-kvm create --no-start vm_name release=xenial) * virsh edit vm_name (and create or update sysinfo manufacturer to be "nutanix", like https://pastebin.ubuntu.com/p/C5mkc2B7rx/) * install landscape-client/common and call landscape-config * see the computer is detected as kvm [Regression Potential] * The hypervisor detection change is both trivial and similar to previous changes and is specific enough not to conflict with other hypervisors. [Other Info] * Patches are already in the upstreams trunk. * Changes have been tested by some affected users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1788219/+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 1814911] Re: charm deployment fails, when using self-signed certificate, which has IP address only (SAN)
Recommends are install when packages are upgraded: # apt install python-urllib3 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libfreetype6 os-prober Use 'apt-get autoremove' to remove them. The following extra packages will be installed: python-ipaddress python-pyasn1 Suggested packages: doc-base python-ntlm Recommended packages: python-ndg-httpsclient The following NEW packages will be installed: python-ipaddress python-pyasn1 The following packages will be upgraded: python-urllib3 1 upgraded, 2 newly installed, 0 to remove and 9 not upgraded. Need to get 131 kB of archives. After this operation, 596 kB of additional disk space will be used. Do you want to continue? [Y/n] So the right fix here is to update python-urllib3 to have a Recommends on python-ipaddress. ** Also affects: python-urllib3 (Ubuntu) Importance: Undecided Status: New ** Also affects: python-urllib3 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: python-urllib3 (Ubuntu) Status: New => Invalid ** Changed in: charm-helpers Status: New => Invalid ** Changed in: cloud-archive/mitaka Status: New => Triaged ** Changed in: python-urllib3 (Ubuntu Xenial) Status: New => Triaged ** Changed in: cloud-archive/mitaka Importance: Undecided => High ** Changed in: python-urllib3 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: python-urllib3 (Ubuntu Xenial) Assignee: (unassigned) => James Page (james-page) -- 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/1814911 Title: charm deployment fails, when using self-signed certificate, which has IP address only (SAN) Status in Charm Helpers: Invalid Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: Triaged Status in python-urllib3 package in Ubuntu: Invalid Status in python-urllib3 source package in Xenial: Triaged Bug description: E.g. radosgw charm fails, when self-signed SSL certificate has IP address only (not hostname based). 2019-02-06 13:05:46 DEBUG identity-service-relation-changed Traceback (most recent call last): 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/identity-service-relation-changed", line 400, in 2019-02-06 13:05:46 DEBUG identity-service-relation-changed hooks.execute(sys.argv) 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/charmhelpers/core/hookenv.py", line 800, in execute 2019-02-06 13:05:46 DEBUG identity-service-relation-changed self._hooks[hook_name]() 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/charmhelpers/contrib/openstack/utils.py", line 1891, in wrapped_f 2019-02-06 13:05:46 DEBUG identity-service-relation-changed restart_functions) 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/charmhelpers/core/host.py", line 730, in restart_on_change_helper 2019-02-06 13:05:46 DEBUG identity-service-relation-changed r = lambda_f() 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/charmhelpers/contrib/openstack/utils.py", line 1890, in 2019-02-06 13:05:46 DEBUG identity-service-relation-changed (lambda: f(*args, **kwargs)), restart_map, stopstart, 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/identity-service-relation-changed", line 245, in identity_changed 2019-02-06 13:05:46 DEBUG identity-service-relation-changed configure_https() 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/identity-service-relation-changed", line 389, in configure_https 2019-02-06 13:05:46 DEBUG identity-service-relation-changed setup_keystone_certs(CONFIGS) 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/utils.py", line 356, in _inner2_defer_if_unavailable 2019-02-06 13:05:46 DEBUG identity-service-relation-changed return f(*args, **kwargs) 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File "/var/lib/juju/agents/unit-radosgw-int-0/charm/hooks/utils.py", line 496, in setup_keystone_certs 2019-02-06 13:05:46 DEBUG identity-service-relation-changed get_ks_ca_cert(ksclient, auth_endpoint, certs_path) 2019-02-06 13:05:46 DEBUG identity-service-relation-changed File
[Group.of.nepali.translators] [Bug 1555569] Re: Use 'title' field for snap apps
snapcraft portion was solved as part of LP: #1804256 ** Changed in: snapcraft 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/169 Title: Use 'title' field for snap apps Status in Snapcraft: Fix Released Status in Software Center Agent: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Released Status in gnome-software source package in Yakkety: Won't Fix Status in gnome-software source package in Zesty: Fix Released Status in gnome-software source package in Artful: Fix Released Bug description: [Impact] Snaps show using the snap 'name', which has a limited character set and is not translatable (e.g. 'moon-buggy'). The store contained a 'title' which is more appropriate (e.g. 'Moon Buggy') which was not exposed via snapd. Now snapd supports this field we should use it in GNOME Software. [Test Case] 1. Start GNOME Software 2. Search for 'moon' Expected result: A snap called 'Moon Buggy' is shown. Observed result: A snap called 'moon-buggy' is shown. [Regression Potential] The fix is to use the new field if it is present. To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/169/+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 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not
The fix is incomplete in Xenail the same way as it is incomplete in Bionic.
Tested version: 1.1ubuntu1.18.04.7~16.04.1
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-failed verification-failed-xenial
** Changed in: unattended-upgrades (Ubuntu Bionic)
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/1781176
Title:
Blacklisted packages are included in the "upgradable origin", while
they should not
Status in unattended-upgrades:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Bionic:
Confirmed
Bug description:
[Impact]
* Reports from u-u incorrectly list packages from non-upgradable
origins as "Packages with upgradable origin but kept back"
* Listing the packages incorrectly is a result of
is_pkgname_in_blacklist() having a side effect and removing the side
effect is part of fixing LP: #1396787 which fix is also being SRU-d.
* The fix is removing the side effect of is_pkgname_in_blacklist()
[Test Case]
* There is a build-time test in test/test_blacklisted_wrong_origin.py
* To reproduce the original problem set up a system where all security
updates are installed but ebtables (from bionic-updates) is not updated:
$ sudo unattended-upgrade --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
apt apt-utils ebtables initramfs-tools initramfs-tools-bin
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io
networkd-dispatcher nplan
python-apt-common python3 python3-apt python3-minimal
python3-update-manager snapd squashfs-tools
unattended-upgrades update-manager-core update-notifier-common
27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 24.1 MB of archives.
After this operation, 1454 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
* blacklist ebtables, set up emails from u-u, then run u-u again:
$ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' >
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
$ sudo echo 'Unattended-Upgrade::Mail "root";' >
/etc/apt/apt.conf.d/51unattended-upgrades-mail
$ sudo unattended-upgrade --verbose
Initial blacklisted packages: ebtables
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
Packages that will be upgraded:
* Observe ebtables listed as being kept back and having upgradable origin
with buggy u-u:
$ sudo cat /var/mail/mail
...
Packages with upgradable origin but kept back:
ebtables=20
...
* Upgrade u-u to a fixed version and run it, observing ebtables to be
not listed as having upgradable origin
[Regression Potential]
* Regressions may make packages incorrectly missing from u-u's
report, but the autopkgtests also cover that to some extent.
[Other Info]
* Original report: https://github.com/mvo5/unattended-
upgrades/issues/116
To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+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 1573594] Re: Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling
** Changed in: libmemcached (Ubuntu Trusty) Status: Fix Committed => 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/1573594 Title: Missing null termination in PROTOCOL_BINARY_CMD_SASL_LIST_MECHS response handling Status in libmemcached package in Ubuntu: Fix Released Status in libmemcached source package in Trusty: Invalid Status in libmemcached source package in Xenial: Fix Released Status in libmemcached source package in Bionic: Fix Released Status in libmemcached source package in Cosmic: Fix Released Status in libmemcached source package in Disco: Fix Released Status in libmemcached package in Debian: New Bug description: [Impact] When connecting to a server using SASL, memcached_sasl_authenticate_connection() reads the list of supported mechanisms [1] from the server via the command PROTOCOL_BINARY_CMD_SASL_LIST_MECHS. The server's response is a string containing supported authentication mechanisms, which gets stored into the (uninitialized) destination buffer without null termination [2]. The buffer then gets passed to sasl_client_start [3] which treats it as a null-terminated string [4], reading uninitialised bytes in the buffer. As the buffer lives on the stack, an attacker that can put strings on the stack before the connection gets made, might be able to tamper with the authentication. [1] libmemcached/sasl.cc:174 [2] libmemcached/response.cc:619 [1] libmemcached/sasl.cc:231 [3] http://linux.die.net/man/3/sasl_client_start [Test Case] This bug is difficult to reproduce since it depends on the contents of the stack. However, here is a test case using the fix on Bionic that shows that this fix does not cause any problems. For testing you need 1) A memcached server. You can setup one by following the instructions in [1], or (what I did) create one in the cloud [2]. 2) A client test program to connect to the memcached server. One can be found in [3]. This simple test connects to a memcache server and test basic get/set operations. Copy paste the C code into a file (sals_test.c) and compile with : gcc -o sasl_test -O2 sasl_test.c -lmemcached -pthread 3) On a machine with the updated version of libmemcached in which the fix is applied : jo@bionic-vm:~$ dpkg -l | grep libmemcached ii libhashkit-dev:amd64 1.0.18-4.2ubuntu0.18.04.1 amd64libmemcached hashing functions and algorithms (development files) ii libhashkit2:amd64 1.0.18-4.2ubuntu0.18.04.1 amd64libmemcached hashing functions and algorithms ii libmemcached-dbg:amd641.0.18-4.2ubuntu0.18.04.1 amd64Debug Symbols for libmemcached ii libmemcached-dev:amd641.0.18-4.2ubuntu0.18.04.1 amd64C and C++ client library to the memcached server (development files) ii libmemcached-tools1.0.18-4.2ubuntu0.18.04.1 amd64Commandline tools for talking to memcached via libmemcached ii libmemcached11:amd64 1.0.18-4.2ubuntu0.18.04.1 amd64C and C++ client library to the memcached server ii libmemcachedutil2:amd64 1.0.18-4.2ubuntu0.18.04.1 amd64library implementing connection pooling for libmemcached Run the sals_test binary : #./sasl_test [username] [password] [server] In my case using the credentials and the server created in step 1 : jo@bionic-vm:~$ ./sasl_test 88BAB0 1A99094B77C8935ED9F1461C767DB1F9 mc2.dev.eu.ec2.memcachier.com Get/Set success! [1] https://blog.couchbase.com/sasl-memcached-now-available/ [2] https://www.memcachier.com/ [3] https://blog.memcachier.com/2014/11/05/ubuntu-libmemcached-and-sasl-support/ [Regression Potential] This fix initialises the buffer to 0. Any potential regression may include failure of the authentication when using SASL. * When running autopkgtest for xenial/armhf it fails on gearmand : http://autopkgtest.ubuntu.com/packages/g/gearmand/xenial/armhf . However this is a long standing issue with gearmand and it is not related with the current SRU. [Other Info] This bug affects trusty and later. * rmadison: libmemcached | 1.0.8-1ubuntu2 | trusty | source libmemcached | 1.0.18-4.1 | xenial | source libmemcached | 1.0.18-4.2 | bionic | source libmemcached | 1.0.18-4.2 | cosmic | source libmemcached | 1.0.18-4.2 | disco | source * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919696 * Upstream seems pretty quiet since 2014 Unfortunately, because the project seems more or less dead ... it seems like we won't be able submit anything
[Group.of.nepali.translators] [Bug 1814655] Re: linux-raspi2: 4.4.0-1104.112 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa-dnu Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 phase: Packaging phase-changed: Thursday, 07. February 2019 08:04 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1814655 Title: linux-raspi2: 4.4.0-1104.112 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1814647 phase: Packaging phase-changed: Thursday, 07. February 2019 08:04 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1814655/+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
