Univention Bugzilla – Full Text Bug Listing |
Summary: | Reduce ldap load from ldap-group-to-file.py | ||
---|---|---|---|
Product: | UCS@school | Reporter: | Jürn Brodersen <brodersen> |
Component: | General | Assignee: | Jürn Brodersen <brodersen> |
Status: | CLOSED FIXED | QA Contact: | Ole Schwiegert <schwiegert> |
Severity: | normal | ||
Priority: | P5 | CC: | schwardt, schwiegert |
Version: | UCS@school 4.4 | ||
Target Milestone: | UCS@school 4.4 v5-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
What kind of report is it?: | Feature Request | 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: | |||
Bug Depends on: | 50904 | ||
Bug Blocks: |
Description
Jürn Brodersen
2020-03-09 10:45:23 CET
UCRV unset: OK Branch test looks good: OK I would merge the change to the postinst into the master. I dont know what to do yet about test as we cannot merge it into the master like that. I'm not sure about tests. 01_base/52proofuniquemember and 01_base/52proofuniquemember_empty_attribute do repair groups with members that don't exist. These test don't have the apptest tag so they aren't executed in our tests, though. Adding a group in the scenario like I did in the branch test, feels quite a bit hacky. Any other ideas? Or is the branch test scenario sufficient? Ok merged and build Package installs: OK Advisory: OK Changes take effect: OK UCS@school 4.4 v5 has been released. https://docs.software-univention.de/changelog-ucsschool-4.4v5-de.html If this error occurs again, please clone this bug. |