Bug 34533 – Improve ordering of LDAP schema inclusion

Bug 34533 - Improve ordering of LDAP schema inclusion


Summary:	Improve ordering of LDAP schema inclusion

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	LDAP
Version:	UCS 4.2
Hardware:	All Linux

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

URL:
Keywords:

Depends on:	34406
Blocks:
	Show dependency tree / graph

Reported:	2014-04-11 09:03 CEST by Philipp Hahn
Modified:	2020-07-03 20:51 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Development Internal
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):	Cleanup
Max CVSS v3 score:

Flags:	hahn: Patch_Available+

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 Philipp Hahn

2014-04-11 09:03:13 CEST

+++ This bug was initially created as a clone of Bug #34406 +++
This is for the remaining cleanup-part of attachment 5839 [details]:
<del>1. Use sorted(listdir(...)) to at least get a stable order</del>
2. Allow schema files to start with two digits, which allows ordering. This prefix is ignored when checking for already included schema files.
3. Anchor schema RegExp and escape special characters
4. Convert "useless use of cat" into Python stdin=open(...)
5. Just read lines form stdout instead of first reading whole file.
6. Just parse templates once (instead of for each schema file)
<del>7. Remove duplicate import os.path</del>

Comment 1 Stefan Gohmann

2017-06-16 20:38:53 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 2 Ingo Steuwer

2020-07-03 20:51:33 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.