RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1188679 [details]
messages file

Description of problem: ipa-replica-manage del <$ADHost> fails to delete replication agreement.

Version-Release number of selected component (if applicable):
ipa-server-dns-4.4.0-5.el7.noarch
ipa-server-common-4.4.0-5.el7.noarch
ipa-server-trust-ad-4.4.0-5.el7.x86_64
ipa-server-4.4.0-5.el7.x86_64
389-ds-base-1.3.5.10-5.el7.x86_64

How reproducible: Always


Steps to Reproduce:
1. Establish winsync agreement with windows AD
2. Now try to delete the agreement with the below command.

ipa-replica-manage del <$ADHostname>

Actual results:
1. [root@vm92 ipa-winsync]# ipa-replica-manage del apache.pne.qe
apache.pne.qe: server not found
Where apache.pne.qe is the test windows AD

2. Attaching the /var/log/messages file output.


Expected results: 
The replication agreement should be deleted when the command is issued, instead it gives the message server not found.

Additional info:
1. IPA-Server and windows AD are in the same timezone and have time in sync.
2. The firewall is not running on IPA/Windows AD
3. The dig command for SRV record for windows domain is resolvable.

Created attachment 1188686 [details]
Attaching dirsrv error logs.

I believe the right command for removing winsync replication is:

  ipa-replica-manage disconnect windows.ad.example.com


` ipa-replica-manage del` is for removing IPA masters

As is written in man page:

"""
       Create a winsync replication agreement:

               # ipa-replica-manage connect --winsync --passsync=MySecret --cacert=/root/WIN-CA.cer --binddn "cn=administrator,cn=users,dc=ad,dc=example,dc=com" --bindpw MySecret -v windows.ad.example.com

       Remove a winsync replication agreement:
               # ipa-replica-manage disconnect windows.ad.example.com

"""

I'm removing regression and test blocker keywords because they are not - see comment 4.

Per triage on Aug 16, we might want to detect this situation and advise to use the proper command. This is a subject for future FreeIPA release -> postponing to later release.

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/6227

this is not a issue, see comments 5 and 6

As this is not an issue (see comments 4 and 5) and we want to promote AD trusts instead of investing in winsync, closing as won't fix.