Due to how PRB1530694 temporarily deactivated the "Encrypt ssh private key" Business Rule, the fix for PRB1665263 is skipped in Washington DC upgrades - Known Error

Due to how PRB1530694 temporarily deactivated the "Encrypt ssh private key" Business Rule, the fix for PRB1665263 is skipped in Washington DC upgrades Description The fix for PRB1530694 in San Diego (Create a migration job for re-encrypt the existing data in ssh_private_key after fixing [another problem]) involved a script action "SSH Private Key Migration", which temporarily deactivated the business rule "Encrypt ssh private key" on the discovery_credentials table. As part of the fix, a security.job.status event was is fired, and a script action was run to migrate the data. Before we could re-encrypt old ssh_private data, we needed to deactivate "Encrypt ssh private key" Business Rule to let insert the new data without that interfering. Then the script action activated it again, but just as a normal update, so it appears to be a customisation by 'system'.

When this business rule was changed again out-of-box in Washington DC, as the fix for PRB1665263 (SSH Private Key credential's private key field shows random string after saving the empty field), it gets skipped in the upgrade and the fix is not applied.

Steps to Reproduce

This would probably apply to any instance provisioned before the San Diego (or maybe Tokyo) release.

A Washington DC upgrade will show that the sys_script_78351e1b0a0a0bbe0028ec8853be3731 is Skipped during the upgrade. Manually reverting that to out-of-box would be reqquired to get the latest Washington version of the business rule, that has the fix for PRB1665263.

Workaround This problem has been fixed in Xanadu. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to.