Bug 46026 – The path '/self-service' was not found.

Bug 46026 - The path '/self-service' was not found.


Summary:	The path '/self-service' was not found.

Status:	NEEDMOREINFO

Product:	UCS
Classification:	Unclassified
Component:	Self Service
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Duplicates:	45845 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-01-12 18:11 CET by Johannes Keiser
Modified:	2021-01-15 10:29 CET (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	3: Will affect average number of 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.103
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018010821000616, 2020043021000878, 2017111621000558, 2020061521000018, 2020072321000626, 2020062321000673, 2020061521000054
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 Johannes Keiser

2018-01-12 18:11:24 CET

Version: 4.2-1 errata197 (Lesum)

Webfrontend-Fehler: Die angegebene Anfrage ist nicht bekannt.
The path '/self-service' was not found.


Role: domaincontroller_slave

Comment 1 Daniel Tröder

2018-01-15 09:05:51 CET

Maybe the backend (self-service/backend-server) was not installed on the DC master?

Comment 2 Christian Castens

2020-06-12 12:15:15 CEST

Reported again:
Version: 4.4-0 errata0 (Blumenthal)

Webfrontend error: The specified request is unknown.
The path '/self-service' was not found.


Role: domaincontroller_master

Comment 3 Philipp Hahn

2021-01-15 10:28:36 CET

*** Bug 45845 has been marked as a duplicate of this bug. ***