Bug 40034 - No UMC login possible after update to 4.1
Summary: No UMC login possible after update to 4.1
Status: RESOLVED DUPLICATE of bug 43520
Alias: None
Product: UCS
Classification: Unclassified
Component: Update - Release updates
Version: UCS 4.1
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 4.1-x
Assignee: UCS maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-19 11:50 CET by Florian Best
Modified: 2018-04-14 13:51 CEST (History)
0 users

See Also:
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):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2015-11-19 11:50:19 CET 
We received the feedback that no UMC login is possible anymore after Upgrading to UCS 4.1.
http://forum.univention.de/viewtopic.php?f=48&t=4557&p=17322#p17322

This is caused by not restarting the UMC-Webserver after the upgrade via UMC. There is a pop up to restart the server components which might be ignored.

Maybe we should just do a hardcoded 'univention-management-console-web-server restart' in postup.sh?!
Side effect could be that the login dialog pops up after the update if one wants to use other modules.
Comment 1 Florian Best univentionstaff 2015-11-20 10:58:37 CET 
Ok, the problem was a different one:
The template /etc/univention/templates/files/etc/apache2/sites-available/univention-management-console was manually overwritten.

Maybe we should block the update if:
univention-check-templates | grep /etc/univention/templates/files/etc/apache2/sites-available/univention-management-console
Comment 2 Florian Best univentionstaff 2017-02-15 11:08:12 CET 

*** This bug has been marked as a duplicate of bug 43520 ***