Temporary Workaround:
Add an additional warning day earlier than the first configured warning day in the alert notification settings. This helps ensure that alerts are triggered at the expected time, you would use the following commands:
[:]:>configure controller properties
[:]: >controllerproperties> ssl_certificate_expiry_warning_days 45
[:]: >controllerproperties> save
After this configuration, the ssl_certificate_expiry_warning_days would include the new values. For example, the configuration in version 31.2 would appear as:
Field Value
ssl_certificate_expiry_warning_days[1] 45 days
ssl_certificate_expiry_warning_days[2] 30 days
ssl_certificate_expiry_warning_days[3] 7 days
ssl_certificate_expiry_warning_days[4] 1 days
Permanent Fix:
The issue will be permanently fixed on version 32.2.1