buildmgr authentication lost

[Pierrot_2]

Our 3rd core was working just fine then we started getting this:

.opsware.client.Twist, line: 0, hostname: twist, timestamp: 1585166882726 ]

com.opsware.fido.AuthenticationException: ID: HPSA-1114
Code: com.opsware.fido.FidoMessageSpec.AUTHENTICATION_FAILURE
Details: Authentication failed for user buildmgr. Details <class=UserImpl><method=authenticate><message='login incorrect for user: buildmgr'>

What cause that?

Pierrre

[Pierrot_2]

ran this and it says valid:

/var/log/opsware/occ](413) # /opt/opsware/support/bin/verify_user_sigs -n buildmgr
VALID: 'buildmgr'(20100) - ACTIVE

[bengland]

Best guess The password in here does not match the password for the buildmgr user.
/var/opt/opsware/crypto/buildmgr/twist.passwd

The content will be encrypt but you can replace it will the correct cleartext password and restart the buildmgr and if its correct it will re-encrypt and connect.

You may not simply copy the encrypted file from another core as each has its own salt for encryption.

The password used when you built your core can be found like this:
grep -A1 twist.buildmgr.passwd /var/opt/opsware/install_opsware/resp/resp_globals

Unless of course you have used the passwdChanger to change them all.

[Pierrot_2]

I'll change my passwords to be all the same...

but I get these fails :

Validate %truth.detuserpwd in file twist/detuserpwd [OK]
Validate %truth.detuserpwd in file da/detuser.passwd [FAIL]
REASON: WARNING: Component not present

Validate %truth.detuserpwd in file hub/twist.pwd [OK]
Validate %truth.detuserpwd in file apxproxy/twist.pwd [OK]
Validate %truth.twistPwd in file da/twist.passwd [FAIL]
REASON: WARNING: Component not present

Validate %truth.vaultPwd in file vault/vault.pwd [OK]
Validate %twist.buildmgr.passwd in file buildmgr/twist.passwd [FAIL]
REASON: WARNING: Component not present

Validate %twist.buildmgr.passwd in file occ/twist.passwd [OK]
Validate %truth.spinPwd used in /etc/opt/opsware/spin/spin.args [OK]
Validate %truth.twistPwd in file .../standalone-full.xml [OK]
Validate %truth.twistPwd for Oracle user twist [OK]
Validate %truth.vaultPwd for Oracle user vault [OK]
Validate %truth.spinPwd for Oracle user spin [OK]
Validate %truth.truthPwd for Oracle user truth [OK]
Validate %truth.gcPwd for Oracle user gcadmin [OK]
Validate %truth.aaaPwd for Oracle user aaa [OK]
Validate %truth.aaaPwd for Oracle user aaa_user [OK]
Validate %truth.lcrepPwd for Oracle user lcrep [OK]
Validate %truth.pubViewsPwd for Oracle user opsware_public_views [OK]
Validate %truth.oaPwd for Oracle user opsware_admin [FAIL]
REASON: Password OK - warnings only
WARNING: User SPIN allows 10 failed logins before account lockout
WARNING: User TWIST allows 10 failed logins before account lockout
WARNING: User VAULT allows 10 failed logins before account lockout

Validate %truth.detuserpwd in DA Oracle table [FAIL]
REASON: No row found in da_global_configuration

Validate %truth.detuserpwd for SA user detuser [OK]
Validate %twist.buildmgr.passwd for SA user buildmgr [OK]

[bengland]

Validate %twist.buildmgr.passwd in file buildmgr/twist.passwd [FAIL]
REASON: WARNING: Component not present

I forgot to ask what version of SA are you on.  The buildmgr component has been deprecated and removed in SA release 2018.08.  It has no buildmgr.   This component was used to provide OS Sequence support and has since been replaced entirely with the new OS Build Plan approach.

[Pierrot_2]

[root@prd-vusaapp05 /opt/opsware/support/bin](5495) # ./version
2018.08

[bengland]

A fresh install will not install buildmgr.
I checked a SA 10.20 core that was upgraded in place to 2018.08 and the buildmgr component has been removed.  Its not present in this file /opt/opsware/oi_util/startup/components.config

I suggest you open a support ticket indicating from SA version you came from and where are now, along with the buildmgr issue.  This is an post-upgrade problem.

[Pierrot_2]

Cool, I'll do that, but it's not an upgrade, it's a new build completly.

Also, do I run passwdChanger on the primary of each cores, once per mesh or or all slices?

Pierre

[bengland · Accepted solution]

Also, do I run passwdChanger on the primary of each cores, once per mesh or or all slices?

All three with different scripts.  The documentation will explain.
# less /opt/opsware/support/man/man1/passwdChanger.1