Proper upgrade procedure using Redhat repo and yum

[Patrick Landry]

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(a)louisiana.edu

[Patrick Landry]

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. 

----- Original Message -----

>  From: "Patrick Landry"
> <patrick.landry(a)louisiana.edu&gt;
>  To: 389-users(a)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(a)louisiana.edu 
>  _______________________________________________
>  389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)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/[e-mail]... 
-- 

	

Patrick Landry 
Director, UCSS 
University of Louisiana at Lafayette 
patrick.landry(a)louisiana.edu

[Theadora Strother]

We have a single master and 3 replicas. Updates are more or less "remove
from the load balancer one at a time / yum -y upgrade / reboot / re-add to
load balancer" when being cautious, and "yum -y upgrade / stagger reboot"
when not being cautious. The ldap server is resilient enough that changes
will be tracked and distributed.

On Mon, Apr 29, 2019 at 3:33 PM Patrick Landry <patrick.landry(a)louisiana.edu&gt;
wrote:

>  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(a)louisiana.edu&gt;
>  *To: *389-users(a)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(a)louisiana.edu <pml(a)louisiana.edu&gt;
>
>
>
>  _______________________________________________
>  389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)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/[e-mail]...
>
>
>
>
>  --
>
>
>  *Patrick Landry*Director, UCSS
>  University of Louisiana at Lafayette
>  patrick.landry(a)louisiana.edu <pml(a)louisiana.edu&gt;
>
>
>  _______________________________________________
>  389-users mailing list -- 389-users(a)lists.fedoraproject.org
>  To unsubscribe send an email to 389-users-leave(a)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/[e-mail]...
>  

-- 
Theadora Strother
Systems Administrator Senior
Information Technology Services
University of Michigan-Dearborn
19000 Hubbard Drive, 238 FCN
Dearborn, MI 48126

[Paul Whitney]

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: [e-mail]<mailto:[e-mail]>
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(a)louisiana.edu&gt;
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(a)louisiana.edu&gt;
To: 389-users(a)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.

--

[cid:f92db249-adad-434c-95dd-dd80d4b9b6f9]


Patrick Landry
Director, UCSS
University of Louisiana at Lafayette
[e-mail]<mailto:[e-mail]>




_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)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/[e-mail]...



--

[cid:8474e3e6-d2db-4113-9444-3890866ea187]


Patrick Landry
Director, UCSS
University of Louisiana at Lafayette
[e-mail]<mailto:[e-mail]>

[Patrick Landry]

Thanks for the comments. I will be proceeding with my update shortly. 

-- 

	

Patrick Landry 
Director, UCSS 
University of Louisiana at Lafayette 
patrick.landry(a)louisiana.edu

[Patrick Landry]

The updates of my servers were successful. The only note I had to add was 
that running "setup-ds-admin.pl -u" required the re-entry of the information 
about how to contact the Config Directory Server. 

Thanks again. 

-- 

	

Patrick Landry 
Director, UCSS 
University of Louisiana at Lafayette 
patrick.landry(a)louisiana.edu