Bug 38810 – univention-repository-update fails with "Configuration error: host is unresolvable" for errata component

Bug 38810 - univention-repository-update fails with "Configuration error: host is unresolvable" for errata component


Summary:	univention-repository-update fails with "Configuration error: host is unresol...

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Update - Repository administration
Version:	UCS 3.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-07-01 16:40 CEST by Daniel Orrego
Modified:	2019-01-03 07:07 CET (History)
CC List:	0 users

See Also:	42450
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:	Yes
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 Daniel Orrego

2015-07-01 16:40:27 CEST

We have a member server as UCS repository mirror (repository/mirror: yes)

If a new patch release comes, a system upgrade (univention-upgrade) will create the corresponding UCR variables for the errata component. Say:
 repository/online/component/3.2-<lastminor>-errata: enabled
 repository/online/component/3.2-<lastminor>-errata/description: Errata updates for UCS 3.2-<lastminor>
 repository/online/component/3.2-<lastminor>-errata/version: 3.2

But that is not enough for univention-repository-update.
It will fail with this backtrace in the /etc/apt/mirror.list file:

# An error occurred during the repository check. The error message:
#   Traceback (most recent call last):
#     File "<stdin>", line 13, in <module>
#     File "/usr/lib/pymodules/python2.6/univention/updater/mirror.py", line 49, in __init__
#       UniventionUpdater.__init__(self, check_access)
#     File "/usr/lib/pymodules/python2.6/univention/updater/tools.py", line 556, in __init__
#       self.ucr_reinit()
#     File "/usr/lib/pymodules/python2.6/univention/updater/tools.py", line 611, in ucr_reinit
#       assert self.server.access('/univention-repository/')
#     File "/usr/lib/pymodules/python2.6/univention/updater/tools.py", line 481, in access
#       raise ConfigurationError(uri, reason)
#   ConfigurationError: Configuration error: host is unresolvable
#

# After fixing this issue, you should rewrite this file with the following command:
#   univention-config-registry commit /etc/apt/mirror.list
#

*Workaround*
Explicitly set the server UCRV for the errata component, each time there is a new patch release:
~# ucr set repository/online/component/3.2-<lastminor>-errata/server="updates.software-univention.de"

After that univention-repository-update will work as expected.

Comment 1 Stefan Gohmann

2017-06-16 20:39:21 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 2 Florian Best

2017-06-28 14:52:50 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 3 Stefan Gohmann

2019-01-03 07:07:55 CET

This issue has been filled against UCS 3.2. The maintenance with bug and security fixes for UCS 3.2 has ended on 30st of November 2016.

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