Bug 33351 – 60_umc/04_policies: policy result test with fixed/empty attributes

Bug 33351 - 60_umc/04_policies: policy result test with fixed/empty attributes


Summary:	60_umc/04_policies: policy result test with fixed/empty attributes

Status:	CLOSED WONTFIX

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

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Dmitry Galkin
QA Contact:	Philipp Hahn

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-11-13 14:01 CET by Florian Best
Modified:	2023-03-25 06:40 CET (History)
CC List:	1 user (show)

See Also:	33354
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
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 Florian Best

2013-11-13 14:01:37 CET

The test case 60_umc/04_policies should also test policies which have 'fixed attribute', 'empty attribute' and maybe also 'required/excluded object class' set.

Comment 1 Dmitry Galkin

2014-07-08 17:16:19 CEST

The cases with 'empty' and 'fixed' attributes are not going to be implemented, since behavior with UCR policies ('policies/registry') used in this test is different. An attempt showed that they are not really inherited/applied (probably due to a special hexadecimal values representation?)

Comment 2 Philipp Hahn

2014-07-09 08:23:08 CEST

OK(In reply to Dmitry Galkin from comment #1)
> The cases with 'empty' and 'fixed' attributes are not going to be
> implemented, since behavior with UCR policies ('policies/registry') used in
> this test is different. An attempt showed that they are not really
> inherited/applied (probably due to a special hexadecimal values
> representation?)

OK: empty and fixed don't work for UCR policies indeed; no need to test.

OK: required/excluded object class still works; please add a test for that through Bug #35314, as that is the same mechanism for all policies; but there seems to be a UMC Bug #33354 comment 2