Starting with version 8.14, when Aria Operations and Aria Operations for logs are managed through SDDC Manager 4.5.x, the password expiry status appears as blank or "? --".
search cancel

Starting with version 8.14, when Aria Operations and Aria Operations for logs are managed through SDDC Manager 4.5.x, the password expiry status appears as blank or "? --".

book

Article ID: 394407

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

  • Log file /var/log/vmware/vcf/operationsmanager.log will show similar entries to: 

YYYY-MM-DDTHH:MM:SS DEBUG [vcf_om,a9db33e702486c66,f412] [c.v.evo.sddc.common.util.SshUtil,om-exec-11] The command [ passwd -S root ] executed on <VRLI-FQDN>. Status: 0, Timed out: false
Output: root P 2024-10-11 0 365 7 -1
Error: 
YYYY-MM-DDTHH:MM:SS ERROR [vcf_om,a9db33e702486c66,f412] [c.v.v.p.s.PasswordValidationService,om-exec-11] Password expiry retrieval is failed for entity: VRLI, credential type: SSH, address: <VRLI-FQDN>
com.vmware.vcf.passwordmanager.exception.PasswordManagerException: Text '2024-10-11' could not be parsed at index 2
        at com.vmware.vcf.passwordmanager.update.changers.SshPasswordChanger.getPasswordExpiry(SshPasswordChanger.java:180)
        at com.vmware.vcf.passwordmanager.service.PasswordValidationService.testPasswordExpiry(PasswordValidationService.java:733)
        at com.vmware.vcf.passwordmanager.service.PasswordValidationService.validatePasswordForEntity(PasswordValidationService.java:489)
        at com.vmware.vcf.passwordmanager.service.PasswordValidationService$$FastClassBySpringCGLIB$$882078a.invoke(<generated>)

Environment

VMware Cloud Foundation 4.5.X

Cause

  • SDDC Manager could not retrieve password expiry details for Aria Operations and Aria Operations for Logs due to incorrect date format.
  • Starting with version 8.14, both Aria Operations and Aria Operations for Logs have upgraded their underlying operating system from Photon OS 3 to Photon OS 4.
  • Default OS date format for Photon 3 was "MMM DD, YYYY". In Photon 4 it was changed to "YYYY-MM-DD".

Resolution

This has been addressed in VMware Cloud Foundation 5.1, which includes a fix for the parsing logic.