389-ds-base

#49522 access log reports erronously an Operation canceled
Closed: wontfix by spichugi. Opened by tbordaz.

Closed: wontfix
Reopen Issue

Issue Description

With the attached test case, the connection ends with error status although all operations were successful.

[05/Jan/2018:11:44:44.373700955 +0100] conn=1 op=15 MOD dn="cn=group_1,ou=groups,dc=example,dc=com"
[05/Jan/2018:11:44:44.433739301 +0100] conn=1 op=15 RESULT err=0 tag=103 nentries=0 etime=0.0060274750
[05/Jan/2018:11:44:44.434301595 +0100] conn=1 op=16 SRCH base="cn=user_1,ou=people,dc=example,dc=com" scope=0 filter="(objectClass=*)" attrs="memberOf"                                                                                                                 
[05/Jan/2018:11:44:44.434505436 +0100] conn=1 op=16 RESULT err=0 tag=101 nentries=1 etime=0.0000359866
[05/Jan/2018:11:44:44.463001096 +0100] conn=1 op=-1 fd=64 closed error 125 (Operation canceled) - A1

Package Version and Platform

Reproduced on master

Steps to reproduce

  1. run the attached testcase
    note the test is related to memberof just because I was preparing a memberof test. However I am unsure current issue is related to memberof.
    Note that the test triggers 2 internal operations to set the 'memberof'. The first operation fails because of schema violation.

Actual results

Operation is said to be canceled

Expected results

Connection should close without stating an operation was canceled

Metadata Update from @tbordaz:
- 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

ticket49522_test.py

At the exact time of the connection closure, this message is logged

[05/Jan/2018:15:30:01.244192445 +0100] - INFO - ns_connection_post_io_or_closing - post closure job for conn 1 for fd=64 failed to be added to event queue as server is shutting down

Is this really a bug? If the server is marked to shutdown this is correct - we can't re-add to the event queue because all the workers are shutdown and we'll leak resources, so we have to reject the event queue add.

There should be no add to the queue, the message is logged if the server is shutdown and a connection is still established, no activity.

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

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

If not reproducible with 1.4.3 with the provided testcase => close this ticket

Metadata Update from @tbordaz:
- Issue priority set to: None (was: normal)
- Issue set to the milestone: 1.4.0 (was: 1.4.3)

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

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

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)
Metadata
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.