#50919 Backend delete fails using dsconf
Closed: wontfix 4 years ago by mreynolds. Opened 4 years ago by vashirov.

Issue Description

dsconf -v localhost backend delete userRoot
DEBUG: 'Namespace' object has no attribute 'be_name'
Traceback (most recent call last):
  File "/usr/sbin/dsconf", line 134, in <module>
    result = args.func(inst, None, log, args)
  File "/usr/lib/python3.7/site-packages/lib389/cli_conf/backend.py", line 222, in backend_delete
    dn = _search_backend_dn(inst, args.be_name)
AttributeError: 'Namespace' object has no attribute 'be_name'
ERROR: Error: 'Namespace' object has no attribute 'be_name'

Package Version and Platform

389-ds-base-1.4.2.8-3.fc31.x86_64
389-ds-base-1.4.3.3-3.fc33.x86_64


Metadata Update from @vashirov:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

4 years ago

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

4 years ago

Commit 5fb0471 relates to this ticket

Commit 5fb0471 relates to this ticket

dc339c4..1d03ec3 389-ds-base-1.4.2 -> 389-ds-base-1.4.2

265d4df..419b56a 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue priority set to: critical
- Issue set to the milestone: 1.4.1
- Issue status updated to: Closed (was: Open)

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3972

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata