In the past it appeared that they tried to enable encryption at rest on the only universe on this YW and that failed. That seems to have left YW metadata in a bad state.
universe_details_json had a keyvalue pair "encryptionAtRestConfig":null and there was data in the two kms tables as if encyption at rest was enabled for this universe.
We probably need to do two things when the Enable encryption at rest task fails.
Do not update the universe details json with the above key value pair
roll back the kms table entry (do we need to rollback only the entry in the kms history table?)
This was on 2.0.5.7
In the past it appeared that they tried to enable encryption at rest on the only universe on this YW and that failed. That seems to have left YW metadata in a bad state. universe_details_json had a keyvalue pair "encryptionAtRestConfig":null and there was data in the two kms tables as if encyption at rest was enabled for this universe.
We probably need to do two things when the Enable encryption at rest task fails.