Bug 48900 – Update broken 5000 users in 1000 groups product test script and generate new reference data

Bug 48900 - Update broken 5000 users in 1000 groups product test script and generate new reference data


Summary:	Update broken 5000 users in 1000 groups product test script and generate new ...

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	General
Version:	unspecified
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-03-07 15:31 CET by Arvid Requate
Modified:	2019-03-07 15:33 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
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
create_5000_users_in_1000_groups.sh (7.84 KB, application/x-shellscript) 2019-03-07 15:31 CET, Arvid Requate	Details
View All 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 Arvid Requate

2019-03-07 15:31:51 CET

Created attachment 9899 [details]
create_5000_users_in_1000_groups.sh

The product tests (LDAP, Samba) reference a script that creates 5000 users in 1000 groups, 50 members each. But the script is a bot broken:

* It only adds 32 members in each group
* It only puts each user in one additional group
* It puts non-existent user account DNs into groups

The last point is especially nasty, because some ucs-test scripts fail in that case. The attached script should be better, but before replacing the script we need to generate new comparison data with it with UCS 4.4, as a basis for the next round of product tests. We should als accurately document under which conditions the reference data is collected (e.g. VM on lattjo, hdd image on the high-performance storage, 2 cpus, 2 GB RAM, VM cache=writethrough -- or something suitable).