Bug 34516 – Tool for list and remove conflicted and deleted objects

Bug 34516 - Tool for list and remove conflicted and deleted objects


Summary:	Tool for list and remove conflicted and deleted objects

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 3.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:	33616 33977
Blocks:
	Show dependency tree / graph

Reported:	2014-04-09 16:01 CEST by Tim Petersen
Modified:	2017-04-20 20:29 CEST (History)
CC List:	4 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):
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 Tim Petersen

2014-04-09 16:01:26 CEST

+++ This bug was initially created as a clone of Bug #33616 +++

A Samba tool would be helpful to list and delete all deleted and conflicted objects (*\0CNF:* and *\0DEL:*).

With this tool it should be possible to run an interactive or non-interactive mode. All objects selected for deletion should be written to /var/univention-backup/samba4.





It seems that it won't work with the "--yes" flag:
"samba-tool dbcheck --fix --yes"
does not fix the objects.

If used interactively while confirming each removal it works, but you seem to need more than one (or two) runs.

Comment 1 Arvid Requate

2017-04-20 20:29:06 CEST

This issue has been filed against UCS 3.2.

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

If this is still an issue in newer UCS versions, please use "Clone this bug".
In this case please provide detailed information on how this issue is affecting
you.