Bug 44894 - univention-upgrade causes umc to be autoremoved on base-systems
univention-upgrade causes umc to be autoremoved on base-systems
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.2
All Linux
: P5 normal (vote)
: UCS 4.2-1-errata
Assigned To: Florian Best
Jürn Brodersen
:
Depends on:
Blocks: 45279
  Show dependency treegraph
 
Reported: 2017-06-29 13:07 CEST by Stefan Ahrens
Modified: 2017-08-30 16:29 CEST (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 7: Crash: Bug causes crash or data loss
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.400
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Ahrens univentionstaff 2017-06-29 13:07:11 CEST
When updating a 4.2-Base-System, apt flags umc-packages to be autoremoved. Since univention-upgrade forces autoremove, these packages and config-files are removed, leaving a system wit broken services, like apache2.

This bug is replroducable on UCS-4.2 Base-Systems.
Comment 1 Stefan Gohmann univentionstaff 2017-07-21 08:00:35 CEST
If I remember correctly, UMC is not installed by default, right?

I think it is a problem in our UMC package because it should be possible to remove it.
Comment 2 Florian Best univentionstaff 2017-08-22 18:50:55 CEST
univention-web (1.0.42-38):
r82424 | Bug #44894: allow UMC to be removed on a basesystem

univention-apache.yaml:
r82425 | YAML Bug #44894

univention-apache (9.0.5-12):
r82424 | Bug #44894: allow UMC to be removed on a basesystem
r82423 | Bug #44894: allow UMC to be removed on a basesystem

univention-management-console (9.0.80-64):
r82424 | Bug #44894: allow UMC to be removed on a basesystem
r82422 | Bug #44894: allow UMC to be removed on a basesystem

univention-web.yaml:
r82425 | YAML Bug #44894

univention-management-console.yaml:
r82425 | YAML Bug #44894
Comment 3 Jürn Brodersen univentionstaff 2017-08-28 11:56:41 CEST
Removing univention-management-console flags some packages to be autoremoved on which some customers might depend on:

docker.io
php5
runit (for custom init scripts)
sudo
pam/heimdal packages <- I don't think these are important on an unjoined system.
Some python libs like python-dateutil <- This might break some customer scripts but at least it should not delete any configs.

Adding univention-apache, univention-sudo and univention-docker to univention-basesystem might be a solution. But univention-apache depends on univention-directory-listener which I think should not be on a basesystem?
Comment 4 Florian Best univentionstaff 2017-08-29 12:03:18 CEST
(In reply to Jürn Brodersen from comment #3)
I split this into Bug #44894. This fixes the package state. Apache and such can be started again after the upgrade. The other packages can be installed manually if needed.
Comment 5 Jürn Brodersen univentionstaff 2017-08-29 12:08:58 CEST
(In reply to Florian Best from comment #4)
> (In reply to Jürn Brodersen from comment #3)
> I split this into Bug #44894. This fixes the package state. Apache and such
> can be started again after the upgrade. The other packages can be installed
> manually if needed.

Ok
What I tested:
Upgraded a base system from ucs 4.2-0 to ucs 4.2-1 -> Apache still works -> OK

YAML -> OK