Bug 43521 – App Center should copy all container scripts into the container immediately

Bug 43521 - App Center should copy all container scripts into the container immediately


Summary:	App Center should copy all container scripts into the container immediately

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:	43522
	Show dependency tree / graph

Reported:	2017-02-09 22:30 CET by Dirk Wiesenthal
Modified:	2019-01-03 07:19 CET (History)
CC List:	0 users

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?:	2: Will only affect a few 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.046
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 Dirk Wiesenthal

2017-02-09 22:30:25 CET

If an App ships its own setup script, it is copied into the container just before execution. This may be too late especially for scripts like update_app_version or update_packages.

These scripts are called by setup. But only the custom setup script is copied in this case, the custom update_app_version script is not. There is no way to execute this very script during setup.

Comment 1 Stefan Gohmann

2019-01-03 07:19:34 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 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.