Univention Bugzilla – Full Text Bug Listing |
Summary: | invoke-rc.d: initscript univention-virtual-machine-manager-daemon, action "stop" failed | ||
---|---|---|---|
Product: | UCS | Reporter: | Jan Christoph Ebersbach <ebersbach> |
Component: | UMC - Virtual machines (UVMM) | Assignee: | Philipp Hahn <hahn> |
Status: | CLOSED FIXED | QA Contact: | Erik Damrose <damrose> |
Severity: | normal | ||
Priority: | P5 | CC: | best, damrose, gohmann, virtualization-maintainers, walkenhorst |
Version: | UCS 4.0 | ||
Target Milestone: | UCS 4.0-0-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
See Also: | https://forge.univention.org/bugzilla/show_bug.cgi?id=36672 | ||
What kind of report is it?: | --- | What type of bug is this?: | --- |
Who will be affected by this bug?: | --- | How will those affected feel about the bug?: | --- |
User Pain: | Enterprise Customer affected?: | ||
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: | |||
Attachments: | updater.log |
Description
Jan Christoph Ebersbach
2014-11-20 18:29:49 CET
The update was performed on a UCS Master. The pysupport triggers are probably not done at that point. We should move any reload of UMC into a dpkg-trigger which is executed after py_support. # univention-upgrade --ignoressh Traceback (most recent call last): File "/usr/sbin/univention-upgrade", line 43, in <module> from univention.updater import UniventionUpdater, UCS_Version, ConfigurationError ImportError: No module named updater Subsequently the upgrade can't be continued because univention-upgrade doesn't want to start anymore: # univention-upgrade --ignoressh Traceback (most recent call last): File "/usr/sbin/univention-upgrade", line 43, in <module> from univention.updater import UniventionUpdater, UCS_Version, ConfigurationError ImportError: No module named updater UCS 4 has been removed from sources.list as well - apt-get -f install wants to remove half of UCS. Can you please attach the full updater.log? Created attachment 6455 [details]
updater.log
Here it is.
That's the reason for the failed upgrade: Preparing to replace univention-virtual-machine-manager-daemon 3.0.17-9.493.201404030839 (using .../univention-virtual-machine-manager-daemon_4.0.20-1.561.201411121814_all.deb) ... Stopping UCS Virtual Machine Manager: uvmmdkill: finish: univention-virtual-machine-manager-daemon: (pid 4389) 332282s, want down invoke-rc.d: initscript univention-virtual-machine-manager-daemon, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg - trying script from the new package instead ... Stopping UCS Virtual Machine Manager: uvmmdkill: finish: univention-virtual-machine-manager-daemon: (pid 4407) 332290s invoke-rc.d: initscript univention-virtual-machine-manager-daemon, action "stop" failed. dpkg: error processing /var/cache/apt/archives/univention-virtual-machine-manager-daemon_4.0.20-1.561.201411121814_all.deb (--unpack): subprocess new pre-removal script returned error exit status 1 configured to not write apport reports (In reply to Jan Christoph Ebersbach from comment #0) > 3.0.17-9.493.201404030839 (using .../univention-virtual-machine-manager-daemon_4.0.20-1.561.201411121814_all.deb) ... > Stopping UCS Virtual Machine Manager: uvmmd > kill: finish: univention-virtual-machine-manager-daemon: (pid 4389) 332282s, want down This happens when UVMMd failes to start. Then runit starts ./finish to delay the restart exponentially from 5 to 60 seconds. During that time "sv force-stop" just returns 1, which aborts the init script due to the use of "set -e". To reproduce: ln -sf /bin/false /usr/sbin/univention-virtual-machine-manager-daemon kill -USR1 $(</etc/runit/univention-virtual-machine-manager-daemon/supervise/pid) while sv status univention-virtual-machine-manager-daemon; do sleep 1; done & univention-upgrade --ignoressh --ignoreterm --noninteractive </dev/null r57181 | Bug #36927 UVMM: Copyright 2015 r57182 | Bug #36927 UVMM: Fix upgrade problem r57185 | Bug #36927 UVMM: Fix init script Package: univention-virtual-machine-manager-node Version: 3.0.4-1.87.201501081418 Branch: ucs_4.0-0 Scope: errata4.0-0 2014-11-26-univention-virtual-machine-manager-daemon.yaml Handle failure to stop UVMMd during update more gracefully. Package: univention-virtual-machine-manager-daemon Version: 4.0.21-1.571.201501081422 Branch: ucs_4.0-0 Scope: errata4.0-0 OK: This works great, uvmm-d is more useable now. Updating to a new version does no longer block or fail. OK: YAML However: This will not solve the update problem from 3.2-*: When updating to UCS 4, the errata repositories will only be activated after the initial upgrade completes. The fix should be backported: Bug 37609 |