Bug 54441 – Heimdal starts before network target reached

Bug 54441 - Heimdal starts before network target reached


Summary:	Heimdal starts before network target reached

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Kerberos
Version:	UCS 4.4
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:	2022-02-10 11:57 CET by Dirk Schnick
Modified:	2022-02-10 11:57 CET (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?:	3: A User would likely not purchase the product
User Pain:	0.171
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2022020921000444
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 Schnick

2022-02-10 11:57:30 CET

In a customer environment the heimdal kdc was only listening on localhost after a restart. This was reproduceable. We have seen in the boor.svg that heimdal starts before network is set up. The systemd config of heimdal does not contain
Wants=network-online.target

I think we should add this as starting kdc without full network online makes not really sense.