Bug 42013 - Changing quota in UMC Quota-Modul fails if quota is already exceeded
Summary: Changing quota in UMC Quota-Modul fails if quota is already exceeded
Status: CLOSED FIXED
Alias: None
Product: UCS
Classification: Unclassified
Component: UMC - Quota
Version: UCS 4.1
Hardware: Other Linux
: P5 normal
Target Milestone: UCS 4.1-4-errata
Assignee: Florian Best
QA Contact: Richard Ulmer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-16 16:07 CEST by Christina Scheinig
Modified: 2017-01-11 12:19 CET (History)
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?: 2: Will only affect a 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.091
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2016081021000406
Bug group (optional):
Customer ID:
Max CVSS v3 score:


Attachments
validation error caused by empty limit fields (38.26 KB, image/png)
2016-08-16 16:07 CEST, Christina Scheinig
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2016-08-16 16:07:02 CEST
Created attachment 7882 [details]
validation error caused by empty limit fields

In a customer environment the filesystem-quota exceeded for the Administrator. The customer gets the following error when he tried to expend the quota via umc-quota-modul.

"Eine Option für users_set hat den falschen Typ: 2 Fehler aufgetreten
fileLimitHard: 'Kann nicht in eine Zahl umgewandelt werden
fileLimitSoft: 'Kann nicht in eine Zahl umgewandelt werden"

This problem is caused by the reseted (default) value for "Files soft limit" and "Files hard limit" See added Screenshot

If you add/modify both values, the new quota can be changed.

-------------------------------------------------------------------------------
/var/log/univention/management-console-web-server.log

13.08.16 07:27:54.773  MAIN        ( PROCESS ) : CPCommand (192.168.0.212:51386) response status code: 422
13.08.16 07:27:54.773  MAIN        ( PROCESS ) : CPCommand (192.168.0.212:51386) response message: Eine Option für users_set hat den falschen Typ: 2 Fehler aufgetreten
13.08.16 07:27:54.773  MAIN        ( PROCESS ) : CPCommand (192.168.0.212:51386) response result: {'fileLimitHard': 'Kann nicht in eine Zahl umgewandelt werden', 'fileLimitSoft': 'Kann nicht in eine Zahl umgewandelt werden'}

--------------------------------------------------------------------------------
Trying to reset the quota for the Administrator completely by setting all values to zero, the entry cannot be saved. Instead the message: "Not all limits can be set to zero" appears.
Deleting the quota by "removing" the Administrator, all limits are reset to zero. This is quite illogical. The confirmation message "Please confirm to remove the following user: Administrator" is also confusing

This happened in Ticket#2016081021000406
Comment 1 Florian Best univentionstaff 2017-01-05 17:22:51 CET
It is now possible to reset the values to the default again.

univention-quota (10.0.2-1):
r75602 | Bug #42368: Bug #42013:

univention-quota.yaml:
r75604 | YAML Bug #42368 Bug #42013
Comment 2 Richard Ulmer univentionstaff 2017-01-09 13:19:49 CET
Fix         : Left out values get reset -> Verified
Merge to 4.2: Verified
YAML        : Verified
Comment 3 Janek Walkenhorst univentionstaff 2017-01-11 12:19:29 CET
<http://errata.software-univention.de/ucs/4.1/374.html>