Bug 2236521

Summary: dbmon fails with 'Error: list index out of range'
Product: Red Hat Enterprise Linux 9 Reporter: bsmejkal
Component: 389-ds-baseAssignee: LDAP Maintainers <idm-ds-dev-bugs>
Status: CLOSED MIGRATED QA Contact: LDAP QA Team <idm-ds-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: idm-ds-dev-bugs
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-19 14:57:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description bsmejkal 2023-08-31 15:10:34 UTC
Description of problem:
Running dsconf monitor dbmon fails with Error: list index out of range

Version-Release number of selected component (if applicable):
389-ds-base-2.2.4-3.el9.x86_64
389-ds-base-2.2.4-5.el9_2.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Run 'dsconf instance monitor dbmon' or dirsrvtests/tests/suites/clu/dbmon_test.py
2. 
3.

Actual results:
  File "/usr/local/lib/python3.9/site-packages/lib389/cli_conf/monitor.py", line 135, in db_monitor
    pagesize = int(ldbm_mon['nsslapd-db-mp-pagesize'][0])
IndexError: list index out of range
ERROR: Error: list index out of range


Expected results:


Additional info:

Comment 1 RHEL Program Management 2023-09-19 14:56:11 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-19 14:57:46 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.