Bug 47432 – (Some) app installations run forever if DNS resolution does not work

Bug 47432 - (Some) app installations run forever if DNS resolution does not work


Summary:	(Some) app installations run forever if DNS resolution does not work

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-01 13:45 CEST by Valentin Heidelberger
Modified:	2021-05-14 16:34 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
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.114
Enterprise Customer affected?:
School Customer affected?:	Yes
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 Valentin Heidelberger

2018-08-01 13:45:02 CEST

To reproduce:

- Make sure external DNS resolution does not work on Master server
- Try to install Nextcloud on Member server in the same domain via Master's UMC

Loading bar stays there for at least 45 min, appcenter.log states that DNS resolution does not work on Member

Comment 1 Valentin Heidelberger

2018-08-01 13:47:05 CEST

Classified this as "major usability" because efforts go towards a single centralized UMC being used in the domain.

Comment 2 Ingo Steuwer

2021-05-14 15:42:34 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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