Bug 54945 – UMC do not report error if share path is not whitelisted

Bug 54945 - UMC do not report error if share path is not whitelisted


Summary:	UMC do not report error if share path is not whitelisted

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	UMC - Shares
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2022-07-06 10:43 CEST by Dirk Schnick
Modified:	2022-07-06 10:58 CEST (History)
CC List:	1 user (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?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2022070421000417
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-07-06 10:43:35 CEST

If a share is created in default blacklisted path /var/ in UMC you get not notice that the share can not be created. Also everything looks fine on the system, but the share is not created. The only point to find is listener.log.

This behavior (ucr config capabilities) is also not mentioned in the documentation.

Have seen that in 4.4-9 but I'm sure the behavior exists also in UCS5