Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-9455: Fail to upgrade centrify-openssh from Suite2016.1 to Suite2017.2 via native command

Authentication Service ,  

20 December,17 at 10:26 PM

Problem: Failed to upgrade centrify-openssh from Suite 2016.1 to Suite 2017.2 via native command.

This issue also exists on HPUX 11.31 IA normal(LatPatch), Solaris 11.3 SPARC and AIX 7.1 PAM(TL4-SP4) when upgrade centrify-openssh from Suite2016.1 to Suite2017.2 via native command.
This issue doesn't exist via ./install.sh with same platform.
This issue also exists when upgrade centrify-openssh from Suite2016.1 to Suite2017.1 on the same platform via native command.
This issue doesn't exist when upgrade centrify-openssh from Suite2016.1 to Suite2017 on the same platform via native command.
The issue also exists on Solaris 11.3 SPARC and AIX 7.1 PAM(TL4-SP4) but not exist on HPUX 11.31 IA normal(LatPatch) when upgrade centrify-openssh from Suite2016.1 to Suite2017.2 via native command.

Cause:  Openssh has library dependency for kerberos which got upgraded in suite 2017. The libkrb5.so.3 in CDC version 5.3.1-398 does not have function krb5_get_err, so suite 2017+ openssh dependency should be for >= CDC 5.4.0, so it cannot upgrade cdc-openssh without upgrading the entire set of CDC packages. 

Resolution: The issue is fixed in Suite 2017.2.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleCentrify 19.6 Release Notes articleCentrify 18.3 Release Notes