Bug 38953 – Univention Apps and App Reporting

Bug 38953 - Univention Apps and App Reporting


Summary:	Univention Apps and App Reporting

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:	38951 40062
Blocks:	40063
	Show dependency tree / graph

Reported:	2015-07-17 22:29 CEST by Stefan Gohmann
Modified:	2019-01-03 07:16 CET (History)
CC List:	5 users (show)

See Also:
What kind of report is it?:	Feature Request
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
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 Stefan Gohmann

2015-07-17 22:29:04 CEST

The metering component (app reporting) should be added to the Univention Apps by default: jenkins/app-appliance.cfg

The metering should only be activated when a CSP license has been installed: Bug #38951.

Comment 1 Stefan Gohmann

2015-08-12 12:12:23 CEST

(In reply to Stefan Gohmann from comment #0)
> The metering component (app reporting) should be added to the Univention
> Apps by default: jenkins/app-appliance.cfg

The metering component should be installed on every UCS system but it should only be activated if a CSP license is installed.

Comment 2 Stefan Gohmann

2019-01-03 07:16:10 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.