Bug 45808 – More error codes for failed App installations / upgrades / uninstallations

Bug 45808 - More error codes for failed App installations / upgrades / uninstallations


Summary:	More error codes for failed App installations / upgrades / uninstallations

Status:	CLOSED FIXED

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

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.2-3-errata
Assigned To:	Dirk Wiesenthal
QA Contact:	Felix Botner

URL:
Keywords:

Depends on:	43061
Blocks:
	Show dependency tree / graph

Reported:	2017-12-01 12:13 CET by Dirk Wiesenthal
Modified:	2017-12-14 12:55 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:	0.011
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-12-01 12:13:49 CET

Now we need more details about the error codes.

+++ This bug was initially created as a clone of Bug #43061 +++

After an App installation etc, a status code is sent. Currently, 200 means success, 500 means traceback, 401 means a "clean" raise Abort().

But what exactly caused the App Center to abort the action is not sent. We should improve that.

Comment 1 Dirk Wiesenthal

2017-12-05 14:16:52 CET

I have had a look at the error codes and which occur more frequently.

These error codes should get more details:
InstallSetupFailed (416)
DockerCouldNotStartContainer (417)
InstallFailed (420)
RegisterSchemaFailed (425)

Note that
  DockerCouldNotStartContainer
and
  InstallFailed

are not implemented yet. We should first work with 416 and 425 and see how much these details help.

Additionally, every other exception sends its str() representation. E.g.,
500 - "TypeError: int() argument must be a string or a number, not 'NoneType'"

Comment 2 Florian Best

2017-12-05 14:22:56 CET

(In reply to Dirk Wiesenthal from comment #1)
> Additionally, every other exception sends its str() representation. E.g.,
> 500 - "TypeError: int() argument must be a string or a number, not
> 'NoneType'"
Without a full traceback this information is not really useful.

Comment 3 Dirk Wiesenthal

2017-12-05 14:38:00 CET

(In reply to Florian Best from comment #2)
> (In reply to Dirk Wiesenthal from comment #1)
> > Additionally, every other exception sends its str() representation. E.g.,
> > 500 - "TypeError: int() argument must be a string or a number, not
> > 'NoneType'"
> Without a full traceback this information is not really useful.

Maybe not always. But some may be:
"IOError: [Errno 2] No such file or directory: u'/var/lib/univention-appcenter/apps/nextcloud/data'"
"CalledProcessError: Command '[...]' returned non-zero exit status 1"

Also, we may see whether 20 of our 500 error codes all have the same str() representation or not.

Many error codes cannot come from that many places inside "install".

Comment 4 Felix Botner

2017-12-12 09:38:54 CET

OK - univention-appcenter status
OK - YAML

Comment 5 Arvid Requate

2017-12-14 12:55:58 CET

<http://errata.software-univention.de/ucs/4.2/250.html>