Bug 48126 – proxy/http option not set in system setup, results in failing join

Bug 48126 - proxy/http option not set in system setup, results in failing join


Summary:	proxy/http option not set in system setup, results in failing join

Status:	RESOLVED FIXED

Product:	UCS
Classification:	Unclassified
Component:	System setup
Version:	UCS 4.3
Hardware:	Other Linux

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

URL:	https://git.knut.univention.de/univen...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-11-09 12:10 CET by fherrman
Modified:	2023-12-12 11:43 CET (History)
CC List:	5 users (show)

See Also:	51682
What kind of report is it?:	Bug Report
What type of bug is this?:	6: Setup Problem: Issue for the setup process
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.171
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:

Flags:	hahn: Patch_Available+

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 fherrman 2018-11-09 12:10:53 CET

When installing UCS 4.3 in an environment where a http-proxy is needed, the proxy option is not set when being adding via the web system setup interface. 

As an result an error message is shown, no package sources can be retrieved, a later join fails. Even if proxy/http and proxy/https variables are being set manually and apt-get update is called sucessfully the join fails.

This works without issues when installing UCS 4.2 in the same environment.

Comment 1 Arvid Requate

2018-12-11 15:43:37 CET

This probably affects appliances, because their network config is done via the  UMC setup module.

Comment 2 fherrman 2018-12-11 21:01:20 CET

Definitely affects both appliances and fresh installs, I ran into the same problem with both

Comment 3 Arvid Requate

2018-12-11 21:08:58 CET

When installing from DVD/ISO the network configuration page is provided by the Debian installer, not by the UMC System Setup module.

Comment 4 Philipp Hahn

2019-03-11 11:17:06 CET

This happens with Univention System Setup with our KVM templates: My analysis shows the univention.management.console.modules.setup.checks.repository.get_reachable_repository_servers() is invoked from the *running* UMC server, which has a clean environment from systemd, which does *not* include *http_proxy* and *https_proxy*. So the setting just done in USS is not applied.

git:phahn/48126-uss-proxy

Comment 5 Philipp Hahn

2020-07-17 08:57:51 CEST

At least in USS this was worked-around by Bug #50613 git:db66e7b242061fdb3cbf7588d7d36daf9b453e41 and git:d61451cd025df218e8d263213f23269d842312ba, but later on USS forks many more sub-processes which all inherit the environment, where the proxy settings are missing.

Comment 6 Ingo Steuwer

2021-05-14 16:38:17 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.

Comment 7 Philipp Hahn

2023-12-04 14:51:44 CET

https://git.knut.univention.de/univention/ucs/-/merge_requests/763

Comment 8 Philipp Hahn

2023-12-12 11:43:31 CET

[5.0-6] 944f713049 fix(USS): proxy checking
 base/univention-system-setup/debian/changelog                   |  1 +
 .../umc/python/setup/checks/repositories.py                     | 54 +++++++++++++++++++++--------
 2 files changed, 40 insertions(+), 15 deletions(-)

Package: univention-system-setup
Version: 13.0.10-1
Branch: ucs_5.0-0
Scope: ucs5.0-6