[389-users] Proper upgrading procedure and the use of setup-ds-admin.pl -u

[Anthony Joseph Messina]

I am currently running the following:
389-admin-1.1.8-3.fc11.x86_64
389-admin-console-1.1.4-1.fc11.noarch
389-admin-console-doc-1.1.4-1.fc11.noarch
389-adminutil-1.1.8-3.fc11.x86_64
389-console-1.1.3-3.fc11.noarch
389-ds-1.1.3-4.fc11.noarch
389-ds-base-1.2.1-1.fc11.x86_64
389-ds-base-debuginfo-1.2.1-1.fc11.x86_64
389-ds-console-1.2.0-4.fc11.noarch
389-ds-console-doc-1.2.0-4.fc11.noarch
389-dsgw-1.1.4-1.fc11.x86_64

Those are the packages that were the initial group that supported the renaming 
of Fedora DS to 389 DS.  I plan to upgrade with "yum upgrade" today as some 
bugs have been fixed.

What is the proper upgrading procedure for 389 DS?

Can I simply do a "yum update" and expect everything to work or do I always 
need to merge rpmnew files and run setup-ds-admin.pl after each "yum update"?

I ask for two reasons:

1) I was hit by https://bugzilla.redhat.com/show_bug.cgi?id=518418 and have 
since recreated my servers with the above packages

2) I noticed that while using SSL, the setup-ds-admin.pl requires me to delete 
the CA cert that was previously installed and re-import it (crazy).

I'd like to make sure don't have these servers crap out again.

Thanks a lot.

-A
-- 
Anthony - http://messinet.com - http://messinet.com/~amessina/gallery
8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://listman.redhat.com/archives/fedora-directory-users/attachments/20090828/3ef4291a/attachment.sig>