This bug was fixed in the package systemd - 237-3ubuntu10.31
---
systemd (237-3ubuntu10.31) bionic; urgency=medium
[ Dimitri John Ledkov ]
* Add conflicts with upstart and systemd-shim. (LP: #1773859)
* d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units:
verified with 237-3ubuntu10.31:
root@bb-lp1670291:~# dpkg -l systemd
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
@kat-amsterdam
The fixes we are introducing are for upgrades to 18.04, which by default
is not possible from 14.04.
Upgrade from 14.04 to 16.04 (trusty to xenial) has already been fixed a
while back in landscape client, thus if one uses uptodate client,
upgrades should succeed and reboot without
I saved one 14.04.5 machine for this purpose.
Will I be able to enabled -proposed for 14.04.5 even though it's now out of
support?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Hello Damiön, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
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
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:
-
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:
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:
-
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
** 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
Hello Damiön, or anyone else affected,
Accepted landscape-client into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/14.12-0ubuntu6.14.04.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this
Hello Damiön, or anyone else affected,
Accepted landscape-client into cosmic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/landscape-
client/18.01-0ubuntu4.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Also affects: landscape-client (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: landscape-client (Ubuntu Trusty)
Status: New => In Progress
** Changed in: landscape-client
** Changed in: landscape-client (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: landscape-client (Ubuntu Xenial)
Assignee: (unassigned) => Simon Poirier (simpoir)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358165
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
** Changed in: landscape-client (Ubuntu Cosmic)
Status: Fix Committed => In Progress
** Changed in: landscape-client (Ubuntu Cosmic)
Assignee: Dave Jones (waveform) => Simon Poirier (simpoir)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Testing systemd 237-3ubuntu10.10, with masked and stopped systemd-
logind, `sudo shutdown +1` command proceeds to shutdown in a VM.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358164
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
** Changed in: landscape-client (Ubuntu Bionic)
Status: New => In Progress
** Changed in: landscape-client (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: landscape-client (Ubuntu Bionic)
Assignee: (unassigned) => Simon Poirier (simpoir)
--
You received this bug
This bug was fixed in the package landscape-client - 18.01-0ubuntu6
---
landscape-client (18.01-0ubuntu6) disco; urgency=medium
* debian/patches/nutanix-kvm.patch: Update vm_info.py to include Nutanix
hypervisor.
* Fixes for release-upgrade (LP: #1699179).
-
Hello Damiön, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.8 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358799
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162
** Merge proposal linked:
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163
--
You received this bug
So physically at the machine it was only possible to log into the
command prompt. There is no graphical interface available.
To top it off
Network manager was stopped! Not very good for network-manager to be
stopped right after an upgrade.
sudo service network-manager restart
started the
Ok so this is still FUBAR but then on a higher level.
The upgrade failed miserably see the attached file.
I was able to ssh into the machine after the upgrade.
ran dpkg --reconfigure -a as suggested see below
then I tried to reboot. which was a big mistake.
when I try to reconnect to the
One quick little rant.
Landscape is supposed to be Enterprise Grade software. I should be able
to upgrade the releases of an entire farm of machines. This has been
broken since the first time I tried this feature with Landscape.
--
You received this bug notification because you are a member of
I'm going to upgrade a system from 14.04.5 to 16.04.x tomorrow at
10:00AM CEST so I'll let you know the results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade
This bug was fixed in the package systemd - 229-4ubuntu21.5
---
systemd (229-4ubuntu21.5) xenial; urgency=medium
[ Dimitri John Ledkov ]
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* hwdb: update micmute on Dell laptops. (LP:
root@subtle-cobra:~# dpkg-query -W systemd
systemd 229-4ubuntu21.4
root@subtle-cobra:~# systemctl mask systemd-logind
Created symlink from /etc/systemd/system/systemd-logind.service to /dev/null.
root@subtle-cobra:~# systemctl stop systemd-logind
root@subtle-cobra:~# shutdown +1
Failed to set wall
Hello Damiön, or anyone else affected,
Accepted systemd into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to
I have still have two machines that need upgrading from 14.04 -> 16.04 ->
18.04. I want to replace them and test the upgrade in the lab.
The upgrade from 16.04->18.04 also fails. I'll report it in a new ticket.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This bug was fixed in the package systemd - 239-7ubuntu8
---
systemd (239-7ubuntu8) cosmic; urgency=medium
[ Dimitri John Ledkov ]
* Cherrypick many bugfixes from master.
* systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
[ Julian
** Also affects: landscape-client (Ubuntu Cosmic)
Importance: High
Assignee: Dave Jones (waveform)
Status: Fix Committed
** Also affects: systemd (Ubuntu Cosmic)
Importance: High
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
--
You received this bug
** Description changed:
- Used Landscape (Paid Canonical Subscription) to upgrade one of my
- machines.
+ 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
** Also affects: landscape-client (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: systemd (Ubuntu Xenial)
Yeah, this is all still broken upstream. If dbus call to schedule
shutdown, fails, immediate shutdown is not actually in fact attempted.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-17.06 => ubuntu-18.09
--
You
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L8548
I wonder if fake systemd-services logind shim is on the dbus, accepts
ScheduleShutdown and then does nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Reading modern systemctl code, if the scheduling fails, the intention is
to immediately shutdown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2
Heh, I believe there are historical options re -H -h. As a wild guess, i
looked at the sysvinit implementation in Debian (we have removed the
package in Ubuntu) it has this:
-h Halt or power off after shutdown.
-H Modifier to the -h flag. Halt action is to halt or drop into boot
Note to self, I wonder if:
https://github.com/systemd/systemd/commit/c68867da320de296917820e5a76e902a8a86be5a
https://github.com/systemd/systemd/commit/7f96539d45028650f2ba9452095473a9c455d84b
are related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> /sbin/shutdown, post upgrade not working, imho is a severe bug
I suspect no-one's bothered to report it because as soon as the machine
is (somehow) rebooted, the issue goes away (and reproduction then
involves the pain of going through a trusty install + xenial upgrade
cycle). Still, I'm not
/sbin/shutdown, post upgrade not working, imho is a severe bug. I'll
investigate that. I suspect that because we cannot restart dbus things
don't show up there, but /sbin/shutdown should be smart enough to do
something. I guess the scheduling of timeout is failing, but
/sbin/shutdown now works?
@xnox Scheduling with /sbin/shutdown normally does work ... however,
what we're dealing with here is the anomalous situation of an instance
which starts off as trusty and is upgraded to xenial. During the upgrade
process, the /sbin/shutdown implementation is changed from the upstart
one to the
In general, scheduling with shutdown command should work. E.g. tested in
lxd container that `$ sudo shutdown +4` works correctly.
I wonder if landscape is affected by:
"""
If the time argument is used, 5 minutes before the system goes down the
/run/nologin file is created to ensure that further
** Changed in: landscape-client (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable
I've now pushed a PR which should alleviate the reboot issue
*partially*. The complexity in fixing this arises from the differing
behaviours of implementations of the shutdown, poweroff, and reboot
commands; upstart's poweroff & reboot commands for example, immediately
return (briefly) permitting
Seems like there's two issues here which I'll address in separate PRs to
the landscape-client:
First is the issue that the landscape-client fails to report the
completion (or failure) of the release upgrade process. This turns out
to be due to a delayed import in the version of twisted
For landscape, we will try systemctl reboot, and systemctl -f reboot,
this warning in the manpage:
Warning: specifying --force twice with any of these operations might result
in data loss.
seems like something we don't want to do with managed machines.
--
You received this bug
Could we please use
$ systemctl reboot
$ systemctl -f reboot
$ systemctl -ff reboot
instead of poweroff.
My machines are spread all around the country I live in. I don't want to have
to drive hundreds of kilometers to go around to turn on all my machines by hand
after the upgrade.
Thanks!
@xnox: not as of yet, no. it's still in our backlog.
** Changed in: landscape-client (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: landscape-client (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ping, has above been implemented in landscape? to attempt poweroff, then
-f poweroff, then -ff poweroff?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to
Hello, I've looked more into this.
Upstream does admit that shutdown/reboot commands via systemd may fail.
And the recommendation there is to progressively use bigger hammers.
See: https://github.com/systemd/systemd/issues/3282
So i believe you should be trying to:
$ systemctl poweroff
$
Remove zesty task; added xenial task.
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-17.04 => ubuntu-17.06
** Changed in: systemd (Ubuntu Zesty)
Milestone: ubuntu-17.04 => zesty-updates
** Also affects: landscape-client (Ubuntu Xenial)
Importance: Undecided
Status: New
**
** Changed in: landscape-client (Ubuntu Zesty)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to
** Also affects: landscape-client (Ubuntu Zesty)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Zesty)
Importance: High
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
--
You received this bug notification because you are a member of
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
** Tags added: dist-upgrade xenial
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: landscape-client (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Here's the bug report (from ubuntu-bug /sbin/shutdown):
== ApportVersion =
2.20.1-0ubuntu2.5
== Architecture =
amd64
== Date =
Wed Mar 15 21:35:37 2017
== Dependencies
This does not require landscape-client. It can be reproduced via:
* Install machine with 14.04.5 and fully upgrade it.
* Execute 'do-release-upgrade' to upgrade to 16.04.
* When the upgrade is finished, exit the release upgrade tool (do not allow
the tool to reset the system).
* Manually
** Package changed: ubuntu-release-upgrader (Ubuntu) => landscape-client
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to
Was able to reboot by sshing into the machine and rebooting with error
message but it still went through with the reboot.
Landscape is now stuck on In Progress
In progress Upgrade from trusty to xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs,
66 matches
Mail list logo
