[Touch-packages] [Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
The issue was fixed in python-apt =2.0.0 ** Changed in: python-apt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1827857 Title: Stuck on applying package profile for servers running 18.04 Status in landscape-client package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: Fix Released Bug description: When I apply a package profile to a server, the activity is stuck on 'in progress'. It only happens for servers running on 18.04 LTS. It works for servers running on 14.04 LTS. I can verify that this is not a connection issue by: * Manually installing the packages contained in the package profile * Installing the package profile directly using apt-get. The landscape server is hosted on-premise using version 18.01. The 18.04 server is running: * The latest version of landscape-client, 18.01-0ubuntu3.3. * Ubuntu Server 18.04.02 LTS using 4.15.x kernel. * Python version: 3.6.7 Maybe relevant log files: package-changer.log 2019-05-06 11:59:55,977 WARNING [MainThread] Package data not yet synchronized with server (...) package-reporter.log 2019-05-06 12:00:07,581 ERROR[MainThread] None UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 29: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
** Changed in: landscape-client (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1827857 Title: Stuck on applying package profile for servers running 18.04 Status in landscape-client package in Ubuntu: Fix Committed Status in python-apt package in Ubuntu: New Bug description: When I apply a package profile to a server, the activity is stuck on 'in progress'. It only happens for servers running on 18.04 LTS. It works for servers running on 14.04 LTS. I can verify that this is not a connection issue by: * Manually installing the packages contained in the package profile * Installing the package profile directly using apt-get. The landscape server is hosted on-premise using version 18.01. The 18.04 server is running: * The latest version of landscape-client, 18.01-0ubuntu3.3. * Ubuntu Server 18.04.02 LTS using 4.15.x kernel. * Python version: 3.6.7 Maybe relevant log files: package-changer.log 2019-05-06 11:59:55,977 WARNING [MainThread] Package data not yet synchronized with server (...) package-reporter.log 2019-05-06 12:00:07,581 ERROR[MainThread] None UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 29: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
landscape-client workaround: https://github.com/CanonicalLtd/landscape- client/pull/80 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1827857 Title: Stuck on applying package profile for servers running 18.04 Status in landscape-client package in Ubuntu: In Progress Status in python-apt package in Ubuntu: New Bug description: When I apply a package profile to a server, the activity is stuck on 'in progress'. It only happens for servers running on 18.04 LTS. It works for servers running on 14.04 LTS. I can verify that this is not a connection issue by: * Manually installing the packages contained in the package profile * Installing the package profile directly using apt-get. The landscape server is hosted on-premise using version 18.01. The 18.04 server is running: * The latest version of landscape-client, 18.01-0ubuntu3.3. * Ubuntu Server 18.04.02 LTS using 4.15.x kernel. * Python version: 3.6.7 Maybe relevant log files: package-changer.log 2019-05-06 11:59:55,977 WARNING [MainThread] Package data not yet synchronized with server (...) package-reporter.log 2019-05-06 12:00:07,581 ERROR[MainThread] None UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 29: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827857] Re: Stuck on applying package profile for servers running 18.04
I've been able to reproduce this bug consistently. It appears
python3-apt is at cause. If a non-utf8 locale is configured, apt will
returned descriptions in the preferred lang/encoding and python3 fails
to interpret them as utf8. Python2.7 did ascii conversion, returning
"lossy" unicode conversion but not crashing.
$ grep en_US /etc/locale.gen
en_US ISO-8859-1
# en_US.ISO-8859-15 ISO-8859-15
# en_US.UTF-8 UTF-8
$ LANG=en_US python3
Python 3.7.3 (default, Apr 3 2019, 05:39:12)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apt
>>> apt.Cache().get("gosa").versions[0].description
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/apt/package.py", line 627, in description
dsc = records.long_desc if records is not None else None
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 236:
invalid start byte
** Also affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1827857
Title:
Stuck on applying package profile for servers running 18.04
Status in landscape-client package in Ubuntu:
In Progress
Status in python-apt package in Ubuntu:
New
Bug description:
When I apply a package profile to a server, the activity is stuck on
'in progress'. It only happens for servers running on 18.04 LTS. It
works for servers running on 14.04 LTS.
I can verify that this is not a connection issue by:
* Manually installing the packages contained in the package profile
* Installing the package profile directly using apt-get.
The landscape server is hosted on-premise using version 18.01.
The 18.04 server is running:
* The latest version of landscape-client, 18.01-0ubuntu3.3.
* Ubuntu Server 18.04.02 LTS using 4.15.x kernel.
* Python version: 3.6.7
Maybe relevant log files:
package-changer.log
2019-05-06 11:59:55,977 WARNING [MainThread] Package data not yet
synchronized with server (...)
package-reporter.log
2019-05-06 12:00:07,581 ERROR[MainThread] None
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 29:
invalid start byte
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I tested successfully landscape-client and landscape-common packages
from {trusty,xenial,bionic,cosmic}-proposed. As in the test case, masked
systemd-logind.
After triggering reboots from landscape on all of those. All machines both
force-rebooted as would be expected, and surfaced the error to the web
interface
https://screenshots.firefox.com/bCPz5KxKkx4yG5hl/landscape.canonical.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
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 Committed
Status in systemd source package in Trusty:
New
Status in landscape-client source package in Xenial:
Fix Committed
Status in systemd source package in Xenial:
Fix Released
Status in landscape-client source package in Bionic:
Fix Committed
Status in systemd source package in Bionic:
Fix Committed
Status in landscape-client source package in Cosmic:
Fix Committed
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/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done-bionic verification-done-cosmic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. 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 Committed Status in systemd source package in Trusty: New Status in landscape-client source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: Fix Committed 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies
That workaround wouldn't work in Landscape for many configurations; we
can't assume pocket names as many use custom mirrors or repository
snapshots in which the pocket may not match.
It seems to me there is no simple way to resolve this automatically in
Landscape, but as that upgrade situation is both infrequent, noisy, and
is easy to resolve manually, the real workaround for landscape is to
install those versions manually when that case happens.
Other than that, managing sources lists to limit them to -security after
deployment is the only other simple way to ensure that situation does
not happen with landscape.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1788486
Title:
apt behaviour with strict dependencies
Status in apt package in Ubuntu:
Won't Fix
Status in apt source package in Xenial:
Won't Fix
Status in apt source package in Bionic:
Won't Fix
Bug description:
[Impact]
We notice that situation while investigating a security update using
Landscape, but it also applies to 'apt' outside the Landscape context.
'apt' should be smarter to detect/install packages with strict
dependencies such as systemd[1] when a version is specified for
upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).
It should automatically install the dependencies (if any) from that
same version as well instead of failing trying to install the highest
version available (if any) while installing the specified version for
the one mentionned :
$ apt-get install systemd=229-4ubuntu-21.1
"systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to
be installed"
=
To face that problem :
- Package with lower version should be found in -security ( Ex:
systemd/229-4ubuntu21.1 )
- Package with higher version should be found in -updates ( Ex:
systemd/229-4ubuntu21.4 )
- Package should have strict dependencies ( Ex: libsystemd0 (=
${binary:Version}) )
- The upgrade should only specify version for the package, without it's
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without
libsystemd0 depends)
Using systemd is a good reproducer, I'm sure finding other package
with the same situation is easy.
It has been easily reproduced with systemd on Xenial and Bionic so
far.
[1] debian/control
Depends: ${shlibs:Depends},
${misc:Depends},
libsystemd0 (= ${binary:Version}),
...
[Workaround]
If package + dependencies are specified, the upgrade work just fine :
Ex: $ apt-get install systemd=229-4ubuntu-21.1
libsystemd0=229-4ubuntu-21.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1788486/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
