Bug 38396 – "Performing software tests on involved systems" is running twice

Bug 38396 - "Performing software tests on involved systems" is running twice


Summary:	"Performing software tests on involved systems" is running twice

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-04-30 09:34 CEST by Stefan Gohmann
Modified:	2019-01-03 07:23 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?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.034
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-04-30 09:34:58 CEST

It looks like "Performing software tests on involved systems" is running twice. First for the check and the program listing (that's OK) and than before starting the installation (that seems needless).

Comment 1 Florian Best

2015-05-19 16:03:30 CEST

Well, "needless". If there are changes between receiving the list of changes and clicking the "install" button the check is required again. Between these steps the sources.list is modified, commited and apt-get update runs twice.
→ We can change the progressbar message.
But how is it possible to remove that *seemingly necessary* step?

Comment 2 Stefan Gohmann

2016-01-27 07:14:55 CET

I still think it is needless at least if the check is done 1 minute ago. Anyway, Dirk did some general performance upgrades in the App Center. So I guess we can lower the priority.

Comment 3 Dirk Wiesenthal

2016-10-28 13:07:43 CEST

The first "Software tests" add the repository, calculate package changes and remove the repository. This is done to not leave it there in case the users decides to cancel the process.

The second test adds the repository, but does not remove it again. Instead the repository is used to actually install the App.

To optimize this, one would have to work on the first run. This seems a bit dangerous and error prone.

Comment 4 Stefan Gohmann

2019-01-03 07:23:21 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.