Exalogic Exapasswd Rolls back Compute Node OS Credentials In EMOC Causing Sync Issues When Compute Node OS Credentials Is Changed Using Exapasswd Followed by Compute Node ILOM Credentials
(Doc ID 2289060.1)
Last updated on JUNE 17, 2021
Applies to:Oracle Exalogic Elastic Cloud Software - Version 22.214.171.124.161018 to 126.96.36.199.170718
Oracle Virtual Server x86-64
Exapasswd 1.0.2 (build 11496) included in ELLC 14.2.8 (Oct 2016 PSU), 14.2.9 (January 2017 PSU), 14.2.10 (July 2017 PSU)
In Exalogic Virtual racks running October 2016 PSU 188.8.131.52.161018 or above, issue of Exapasswd rolling back Compute Node OS Credentials in EMOC is observed. In this case Exapasswd version used is 1.0.2 (build 11496).
This issue is seen only when changing the Compute Node OS credentials followed by Compute Node ILOM credentials using Exapasswd commands (below).
Compute Node OS credentials being rolled back from EMOC is verified by checking the credentials for Compute Node OS Asset from EMOC BUI console. To check credentials for Compute node from EMOC console we have to go to Assets, right click on every compute nodes and select 'Update Management Credentials'.
At the time of the issue we see following when checking the credentials for Compute Node OS asset in EMOC BUI console. As we can see, there is no new set of credentials for Compute Node OS even though the password is changed using Exapasswd. Since Exapasswd 1.0.2 (build 11496), when we run Exapasswd to change password for any components of Exalogic, it will create a new set of credentials with name format as "default credential name-timestamp". As seen in below screenshot there is no new set of credentials for Compute Node OS in EMOC.
Compute Node OS password changes followed by Compute Node ILOM password changes using Exapasswd.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document