#49880 In lib389 - MonitorLDBM class does not work properly when we turn off nsslapd-ndn-cache-enabled
Closed: wontfix 3 years ago by spichugi. Opened 5 years ago by amsharma.

Issue Description

With the help of src/lib389/lib389/monitor.py
I was trying to assert ::
log.info("Check the backend monitor output for Normalized DN cache statistics while nsslapd-ndn-cache-enabled is on")
topo.standalone.config.set('nsslapd-ndn-cache-enabled', 'on')
monitor_backend = MonitorBackend(topo.standalone)
assert monitor_backend.present('normalizeddncachehits')

so it should be able to check normalizeddncachehits is present in monitor_backend when nsslapd-ndn-cache-enabled is on, but it does not work and gives error :smoking:
E TypeError: search_ext() argument 1 must be str, not None

Full logs - http://pastebin.test.redhat.com/626448


Also there is a weird check for the version in src/lib389/lib389/monitor.py in init for MonitorLDBM class. so even if we have the right version, but we turn off nsslapd-ndn-cache-enabled, the code will fail

Metadata Update from @amsharma:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

5 years ago

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.0

5 years ago

I think the issue is we allow disabling of ndn cache. We should remove this parameter instead.

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.3 (was: 1.4.0)

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/2939

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
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata