Bug 48818 – unexpected behaviour when setting a user-quota policy

Bug 48818 - unexpected behaviour when setting a user-quota policy


Summary:	unexpected behaviour when setting a user-quota policy

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Quota
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:	2019-02-28 15:21 CET by Jannik Ahlers
Modified:	2019-03-04 11:52 CET (History)
CC List:	2 users (show)

See Also:	36442
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?:	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.086
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 Jannik Ahlers

2019-02-28 15:21:38 CET

Setting hard and soft limits for quota policies via umc has some problems:
- The default unit is B(yte), while in the UMC quota module it is MB. this is inconsistent.
- inserting values without a unit SHOULD default to B, but this doesn't work as
    a) the if statement only passes if the value is 0-10
    b) the value then gets divided by 1024, which for int < 10 returns 0 anyways
  (see base/univention-quota/files/univention-user-quota lines 57-70)
- There is no check if the hard limit is larger than the soft limit