Fedora Info

Sunday, January 4, 2026

[Test-Announce]2026-01-05 @ 16:00 UTC - Fedora Quality Meeting

# Fedora Quality Assurance Meeting
# Date: 2026-01-05
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location:
https://matrix.to/#/#meeting:fedoraproject.org?web-instance[element.io]=chat.fedoraproject.org

Greetings testers! It's meeting time again.

Here is a handy link which should show you the meeting time
in your local time:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Fedora+quality+meeting&iso=20260105T16&p1=1440&ah=1

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 44 status
3. Forgejo migration status
4. Test Day / community event status
5. Open floor
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net

--
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Friday, January 2, 2026

[389-users] Re: how to apply increased search limits to a group of accounts?

Thank you very much for following up and the contribution.

nsTimeLimit is indeed the user-level parameter to configure.

there is a mention in this guide:

https://docs.redhat.com/en/documentation/red_hat_directory_server/13/html/management_configuration_and_operations/searching-entries-and-tuning-searches#setting-user-and-global-resource-limits-by-using-the-command-line

but this use case is different and interesting.

We could add an Upstream HowTo/doc page about it, or even document this into one of the RHDS guides.

Happy New Year!

On Wed, Dec 31, 2025 at 10:00 PM Bob Green via 389-users <389-users@lists.fedoraproject.org> wrote:

On Wed, Dec 31, 2025 at 12:27 PM Bob Green <wood.green.robert@gmail.com> wrote:
>
> On Wed, Dec 24, 2025 at 10:39 AM Mark Reynolds <mareynol@redhat.com> wrote:
> >
> > Hey Bob,
> >
> > What you want is probably pointer COS:
> >
> > https://docs.redhat.com/en/documentation/red_hat_directory_server/11/html-single/administration_guide/index#About_CoS-How_a_Pointer_CoS_Works
> >
> > The issue with this is it works for all entries under a subtree. There
> > is no filtering. So you can apply it to all users under
> > ou=people,dc=example,dc=com by creating the COS definition entry
> > directly under that branch.
> >
> > Not sure if this will work for you, but it's all we got at the moment.
>
> Thank you. I managed to get this to work once I realized that the
> nsSizeLimit and nsLookThroughLimit cosAttribute entries had to include
> operational in the cosPointerDefinition:
>
> cosAttribute: nsSizeLimit operational
> cosAttribute: nsLookThroughLimit operational
>
> I am now running into "Time limit exceeded (3)" when running a query
> that takes over 30 seconds. I was hoping adding nstimelimit: -1 to
> the COS template would overcome this limitation, but I have yet to get
> it to work. I've tried adjusting a variety of cn=config limit and
> time(out) attributes but to no avail. Can anyone please point me to
> whatever attribute needs adjusting?

After rebuilding my instance I no longer see the time limit exceeded
warning. I believe the attribute to overcome the limit is indeed
nstimelimit, and can only account for it not working previously
possibly due to a configuration change I failed to keep track of. I
apologize to the list for the spam, and wish all a happy new year.

Bob
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[fedora-arm] Re: Thunderbird on Fedora aarch64 doesn't start anymore

On Sat, 2025-12-20 at 15:05 +0000, Peter Robinson via arm wrote:
> Have you filed a bug, or even provided karma, on the thunderbird
> update that broke it?
>
> Ultimately it needs to be reported to the maintainer, they're the ones
> that can fix it.

There's some discussion at the end of
https://bugzilla.redhat.com/show_bug.cgi?id=2423824 . Several people
are seeing it.

It may be related to
https://bugzilla.redhat.com/show_bug.cgi?id=2420679 , I guess, which
openQA caught.

Possibly Thunderbird also needs
https://src.fedoraproject.org/rpms/firefox/c/ed74b03b2d1fa2e20a2236b3b760a88f2d5c7548?branch=rawhide
. which looks like it was the fix for the Firefox aarch64 crash. jhorak
found it for Firefox, and he is also the Thunderbird maintainer, but at
a quick look, it seems like he hasn't applied it to Thunderbird yet?
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@fosstodon.org
https://www.happyassassin.net

--
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Wednesday, December 31, 2025

[389-users] [ANN] LDAP Assistant MCP v0.2.0 - AI-Powered 389 DS Diagnostics

Hello 389 Directory Server community,

I'm excited to share an experimental project: LDAP Assistant MCP - an AI-powered assistant for diagnosing 389 Directory Server instances.

What is it?

LDAP Assistant MCP is a Model Context Protocol (MCP) server that enables AI models like Claude to interact with your 389 DS instances. Instead of manually running dsconf/dsctl commands and parsing output, you can ask:

- "What's wrong across all my servers?"
- "Check replication status and tell me if there's any lag"
- "Are there any unindexed searches causing performance issues?"

The assistant runs the appropriate tools and provides actionable recommendations with severity levels.

Key Features (v0.2.0)

- Health & Diagnostics: first_look() for multi-server health overview, run_healthcheck() equivalent to dsctl healthcheck
- Replication: status checks, topology mapping, lag analysis (CSN comparison), conflict detection
- Performance: cache statistics, connection analysis, operation metrics, thread utilization
- Index Analysis: list indexes, analyze against best practices, find unindexed searches from access logs
- Configuration: server config retrieval, multi-server comparison, plugin listing
- User & Group Management: list, search, filter users by status, check groups

Use Cases

Support Engineers: Rapid root cause analysis, multi-server health scans, replication troubleshooting
LDAP Administrators: Performance tuning, index optimization, configuration audits

Getting Started

Prerequisites:
- Python 3.13+
- uv package manager
- MCP client (Claude Desktop, Claude Code, Cursor, or any MCP-compatible client)

Quick Setup:

1. Clone and install:
git clone https://github.com/droideck/ldap-assistant-mcp.git
cd ldap-assistant-mcp
uv venv
source .venv/bin/activate
uv pip install -r requirements.txt

2. Create servers.json with your server(s). You can configure local servers (with is_local: true and serverid for full diagnostics including disk/logs/etc) or remote servers (LDAP-only).

3. Install to your MCP client:
fastmcp install claude-desktop fastmcp.json
or
fastmcp install claude-code fastmcp.json

4. Edit MCP client config to set LDAP_SERVERS_CONFIG path to your servers.json

5. Restart and start asking questions!

Important Notes

- Experimental - Early-stage project, APIs may change
- Read-only - No write operations yet
- Privacy mode - Set LDAP_MCP_EXPOSE_SENSITIVE_DATA=false to anonymize output
- Plain text passwords - Use restrictive file permissions on config files

Feedback

I'd love to hear your thoughts:
- What diagnostics would be most useful?
- What operations would you want AI assistance with?

GitHub: https://github.com/droideck/ldap-assistant-mcp
Issues: https://github.com/droideck/ldap-assistant-mcp/issues

References:
- Model Context Protocol: https://modelcontextprotocol.io/introduction
- FastMCP: https://gofastmcp.com

- lib389: https://pypi.org/project/lib389/

Kind regards,

Simon

[389-users] Re: how to apply increased search limits to a group of accounts?

On Wed, Dec 31, 2025 at 12:27 PM Bob Green <wood.green.robert@gmail.com> wrote:
>
> On Wed, Dec 24, 2025 at 10:39 AM Mark Reynolds <mareynol@redhat.com> wrote:
> >
> > Hey Bob,
> >
> > What you want is probably pointer COS:
> >
> > https://docs.redhat.com/en/documentation/red_hat_directory_server/11/html-single/administration_guide/index#About_CoS-How_a_Pointer_CoS_Works
> >
> > The issue with this is it works for all entries under a subtree. There
> > is no filtering. So you can apply it to all users under
> > ou=people,dc=example,dc=com by creating the COS definition entry
> > directly under that branch.
> >
> > Not sure if this will work for you, but it's all we got at the moment.
>
> Thank you. I managed to get this to work once I realized that the
> nsSizeLimit and nsLookThroughLimit cosAttribute entries had to include
> operational in the cosPointerDefinition:
>
> cosAttribute: nsSizeLimit operational
> cosAttribute: nsLookThroughLimit operational
>
> I am now running into "Time limit exceeded (3)" when running a query
> that takes over 30 seconds. I was hoping adding nstimelimit: -1 to
> the COS template would overcome this limitation, but I have yet to get
> it to work. I've tried adjusting a variety of cn=config limit and
> time(out) attributes but to no avail. Can anyone please point me to
> whatever attribute needs adjusting?

After rebuilding my instance I no longer see the time limit exceeded
warning. I believe the attribute to overcome the limit is indeed
nstimelimit, and can only account for it not working previously
possibly due to a configuration change I failed to keep track of. I
apologize to the list for the spam, and wish all a happy new year.

Bob
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[389-users] Re: how to apply increased search limits to a group of accounts?

On Wed, Dec 24, 2025 at 10:39 AM Mark Reynolds <mareynol@redhat.com> wrote:
>
> Hey Bob,
>
> What you want is probably pointer COS:
>
> https://docs.redhat.com/en/documentation/red_hat_directory_server/11/html-single/administration_guide/index#About_CoS-How_a_Pointer_CoS_Works
>
> The issue with this is it works for all entries under a subtree. There
> is no filtering. So you can apply it to all users under
> ou=people,dc=example,dc=com by creating the COS definition entry
> directly under that branch.
>
> Not sure if this will work for you, but it's all we got at the moment.

Thank you. I managed to get this to work once I realized that the
nsSizeLimit and nsLookThroughLimit cosAttribute entries had to include
operational in the cosPointerDefinition:

cosAttribute: nsSizeLimit operational
cosAttribute: nsLookThroughLimit operational

I am now running into "Time limit exceeded (3)" when running a query
that takes over 30 seconds. I was hoping adding nstimelimit: -1 to
the COS template would overcome this limitation, but I have yet to get
it to work. I've tried adjusting a variety of cn=config limit and
time(out) attributes but to no avail. Can anyone please point me to
whatever attribute needs adjusting? BTW, my queries are GSSAPI over
TLS which is arguably unnecessary since GSSAPI will encrypt the comms.
I mention this in case something like nssslsessiontimeout is
responsible for the timeout.

Thanks,
Bob
--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce]Fedora-IoT 44 RC 20251231.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event
for Fedora-IoT 44 RC 20251231.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/44iot

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_44_RC_20251231.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_44_RC_20251231.0_General

Thank you for testing!
--
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
--
_______________________________________________
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue