The nightly test test_integration/test_simple_replication.py::TestSimpleReplication::test_replica_removal is failing in [testing_master_389ds] Nightly PR #3432 with an error:
test_integration/test_simple_replication.py::TestSimpleReplication::test_replica_removal
def test_replica_removal(self): """Test replica removal""" result = self.master.run_command(['ipa-replica-manage', 'list']) assert self.replicas[0].hostname in result.stdout_text # has to be run with --force, there is no --unattended self.master.run_command(['ipa-replica-manage', 'del', self.replicas[0].hostname, '--force']) result = self.master.run_command( ['ipa-replica-manage', 'list', '-v', self.master.hostname]) > assert self.replicas[0].hostname not in result.stdout_text E AssertionError: assert 'replica0.ipa.test' not in 'replica0.ip...0:00+00:00\n' E 'replica0.ipa.test' is contained here: E replica0.ipa.test: replica E last update status: Error (0) Replica acquired successfully: Incremental update started E last update ended: 1970-01-01 00:00:00+00:00 test_integration/test_simple_replication.py:146: AssertionError
This error is consistent after re-run. Full report, Artifacts
Initial log investigation does not show any replication agreements being removed. I do see various IPA replication related entries being deleted/updated, but not the replication agreements themselves.
"ipa-replica-manage list" appears to trigger this search, and a replication agreement is found
[26/Feb/2024:07:32:11.698424686 +0000] conn=50 op=3 SRCH base="cn=mapping tree,cn=config" scope=2 filter="(|(&(objectClass=nsds5ReplicationAgreement)(nsDS5ReplicaRoot=dc=ipa,dc=test))(objectClass=nsDSWindowsReplicationAgreement))" attrs=ALL [26/Feb/2024:07:32:11.704446985 +0000] conn=50 op=3 RESULT err=0 tag=101 nentries=1 wtime=0.000416191 optime=0.006022402 etime=0.006436444
I see no failures in the DS logs, so it would appear that for some reason "ipa-replica-manage del" is not doing everything it's supposed to do. I would like to see the /etc/dirsrv/slapd-INSTANCE/dse.ldif from this test, but the CI test does not collect the DS config files when an error occurs.
Login to comment on this ticket.