Hi Rob

The last line in the upgrade log is:
"2019-01-09T09:28:45Z INFO The ipa-server-upgrade command was successful"
That indicates success to me!
----- Original message -----
From: Rob Crittenden <rcritten@redhat.com>
To: FreeIPA users list <freeipa-users@lists.fedorahosted.org>
Cc: Christopher Lamb <christopher.lamb@ch.ibm.com>
Subject: Re: [Freeipa-users] ipa-server Upgrade to 4.6.4 warning: %posttrans(bind-32:9.9.4-72.el7.x86_64)
Date: Wed, Jan 9, 2019 4:07 PM
Christopher Lamb via FreeIPA-users wrote:
> Hi
> I have just upgraded our ipa-server from 4.2 to 4.6.4 via yum update on
> OEL 7.2.
> At the very last step of the yum update I got the following warning:
> OSError: No such file or directory
> ValueError: SELinux policy is not managed or store cannot be accessed.
> warning: %posttrans(bind-32:9.9.4-72.el7.x86_64) scriptlet failed, exit
> status 1
> Non-fatal POSTTRANS scriptlet failure in rpm package
> 32:bind-9.9.4-72.el7.x86_64
> The update process hung at this point. Pressing CTRL C,  produced:
> warning: %posttrans(ipa-server-4.6.4-10.0.1.el7.x86_64) scriptlet
> failed, signal 2
> Non-fatal POSTTRANS scriptlet failure in rpm package
> ipa-server-4.6.4-10.0.1.el7.x86_64
> Can I ignore this warning? My initial tests indicate that the upgrade
> was a success:
> * I can log into IPA clients.
> * I can log into JIRA (authentication via IPA LDAP integration)
> * SSL RC4 no longer supported on port 443 (this was the main reason for
> the upgrade)
> * Samba initially failed (smb running on the same server as ipa-server),
> but after upgrading Samba from 4.4.4 to 4.8.3 now works.

You should check /var/log/ipaupgrade.log. IPA performs post-package
upgrades during the rpm transaction so it can take a while.

You can safely re-run ipa-server-upgrade to be sure things are up-to-date.