Bug 53939 – installation of replica, with deferred join, only works without upgrade

Bug 53939 - installation of replica, with deferred join, only works without upgrade


Summary:	installation of replica, with deferred join, only works without upgrade

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UCS Installer
Version:	UCS 5.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-10-18 14:13 CEST by Tobias Wenzel
Modified:	2022-05-13 09:27 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.069
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 Tobias Wenzel

2021-10-18 14:13:49 CEST

Scenario: 

New installation of a multiserver environments. When you want to install a replica, you are have multiple checkboxes. The first is to not join after a successful installation (-> I unchecked this). Another one sets if the server should be updated after the installation. I ran into problems when I did not uncheck this checkbox. I.e. joining was not possible. Unchecking the checkbox activating the test appcenter solved this issue for me.

For me, this is an unexpected behaviour and should be fixed.

Comment 1 Jürn Brodersen

2021-10-18 14:31:53 CEST

The specific problem here was that the ldap server was not yet fully configured due to the deferred join and could not start.

This resulted in a broken upgrade because the ldap server postinst failed due to a failed slapd restart.
Afterwards apt could not be used without solving the broken package configuration.

Comment 2 Jürn Brodersen

2022-01-07 12:30:10 CET

(In reply to Jürn Brodersen from comment #1)

> Afterwards apt could not be used without solving the broken package
> configuration.

Quick correction: apt can still be used but returns a non zero return code, which broke "something" (a join script?) else.

Comment 3 Dirk Ahrnke

2022-05-13 09:27:23 CEST

duplicate to bug 54465?