Your steps are correct.  We run  a production with multi-master replication with redundant sites.  Using Ansible to perform updates (with too many servers to hit one at a time.) We do disable from load-balancer by site instead of just the one host.
  1. remove server1 from the load balancer config to halt client requests
  2. ***We do not stop the server, the update can occur while it is still running
  3. run "yum ***update 389-ds-base 389-ds-base-libs" on server1
  4. run "setup-ds-admin.pl -u" on server1
  5. ***Not needed since we never stopped restart dirsrv and dirsrv-admin on server1
  6. verify replication is still working
  7. add server1 back to load balancer config
  8. repeat steps 1-7 on server2


Paul M. Whitney, RHCSA, CISSP
Email: paul.whitney@chesapeake-it.com
CONFIDENTIALITY NOTICE 
The information contained in this facsimile or electronic message is confidential information intended for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this facsimile message to the intended recipient, you are hereby notified that any dissemination, or copying of this communication is strictly prohibited. If this message contains non-public personal information about any consumer or customer of the sender or intended recipient, you are further prohibited under penalty of law from using or disclosing the information to any third party by provisions of the federal Gramm-Leach-Bliley Act. If you have received this facsimile or electronic message in error, please immediately notify us by telephone and return or destroy the original message to assure that it is not read, copied, or distributed by others.



From: Patrick Landry <patrick.landry@louisiana.edu>
Sent: Monday, April 29, 2019 3:23 PM
To: General discussion list for the 389 Directory server project.
Subject: [389-users] Re: Proper upgrade procedure using Redhat repo and yum
 
Hmmm, no advice here? I would have presumed someone here is running
with packages from the RHEL repository. I'll open a ticket with Redhat but
it would be reassuring to hear from someone who has real-world experience.



From: "Patrick Landry" <patrick.landry@louisiana.edu>
To: 389-users@lists.fedoraproject.org
Sent: Thursday, April 18, 2019 4:47:25 PM
Subject: [389-users] Proper upgrade procedure using Redhat repo and yum

I have two servers running with multi master replication. The servers are
running RHEL 7.4 with 389-ds installed via yum using the rhel-7-server-rpms
repository. The hosts are behind a load balancer and all client access is through
the load balancer.

I would like to upgrade to the latest release available in rhel-7-server-rpms. I
have the following packages installed related to 389ds:

389-admin-1.1.46-1.el7.x86_64
389-admin-console-1.1.12-1.el7.noarch
389-admin-console-doc-1.1.12-1.el7.noarch
389-adminutil-1.1.21-2.el7.x86_64
389-console-1.1.18-1.el7.noarch
389-ds-1.2.2-6.el7.noarch
389-ds-base-1.3.7.5-21.el7_5.x86_64
389-ds-base-libs-1.3.7.5-21.el7_5.x86_64
389-ds-console-1.2.16-1.el7.noarch
389-ds-console-doc-1.2.16-1.el7.noarch
389-dsgw-1.1.11-5.el7.x86_64

Only two of those packages appear to have updates available; 389-ds-base and 389-ds-base-libs.

Is this the correct procedure?
  1. remove server1 from the load balancer config to halt client requests
  2. stop the dirsrv and dirsrv-admin services on server1
  3. run "yum upgrade 389-ds-base 389-ds-base-libs" on server1
  4. run "setup-ds-admin.pl -u" on server1
  5. restart dirsrv and dirsrv-admin on server1
  6. verify replication is still working
  7. add server1 back to load balancer config
  8. repeat steps 1-7 on server2
I presume that replication will continue to work after upgrading server1 but before
upgrading server2. I believe that at step 4, I don't *also* have to run "setup-ds.pl".
Is that correct?

Thanks.

--

Patrick Landry
Director, UCSS
University of Louisiana at Lafayette
patrick.landry@louisiana.edu




_______________________________________________
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org



--

Patrick Landry
Director, UCSS
University of Louisiana at Lafayette
patrick.landry@louisiana.edu