Bug 52851 – UMC Updater: Log should scroll automatically

Bug 52851 - UMC Updater: Log should scroll automatically


Summary:	UMC Updater: Log should scroll automatically

Status:	RESOLVED DUPLICATE of bug 48981

Product:	UCS
Classification:	Unclassified
Component:	UMC - Software update
Version:	UCS 4.4
Hardware:	Other Windows NT

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-02-25 14:04 CET by Michael Grandjean
Modified:	2021-02-25 14:51 CET (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	5: Will affect all installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.114
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
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 Michael Grandjean

2021-02-25 14:04:30 CET

root@ucs-hacon-m1:~# univention-app info
UCS: 4.4-7 errata898
Installed: admindiary-backend=1.0 admindiary-frontend=1.0 dhcp-server=12.0 openid-connect-provider=2.2-konnect-0.33.11 samba4=4.10 self-service=4.0 self-service-backend=4.0
Upgradable:

Scenario: I want to update my UCS system via the UMC module. After starting the update, the log file is shown (/var/log/univention/updater.log). 

Expected behaviour: the log file scrolls automatically ("tail -f" behaviour)

Observed behaviour: the log file does not scroll automatically

Comment 1 Florian Best

2021-02-25 14:09:59 CET

This has been the behavior in the past.

Comment 2 Erik Damrose

2021-02-25 14:51:51 CET

It broken since UCS 4.4-0

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