Issue with legacy encryptor when restoring old CloudStack DB on new management setup #12413
midhunpjos
started this conversation in
General
Replies: 1 comment 1 reply
-
|
@midhunpjos since you are using v1 encryptor and able to start and login I don't think there is an issue with encryption. The API responses are empty for all APIs or specific APIs. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are facing an issue related to the legacy encryptor while setting up a new CloudStack management server using an old database backup, and would like to check if anyone has encountered a similar scenario.
We were using an older CloudStack installation(4.18.1) that relied on the legacy encryptor.
Unfortunately, the original cloud DB user password was not recorded.
We faced a database crash, we restored the CloudStack database from a backup.
After restoration:
A new cloud DB user was created with a new password.
A fresh CloudStack management server was installed.
New encryption keys were generated during the installation using cloudstack-setup-databases and encryptor version as v1
The database connection is successful, and CloudStack services start normally. As per logs ACS is able to connect to hypervisors and system VM's
Both dbkey and mgmtkey were set to the default values that were used in the old installation.
Issue:
User authentication is successful (login does not fail).
However, after login:
The API responses return empty values.
The UI does not populate expected data.
We tested using CloudMonkey:
API key synchronization is successful.
API calls execute without error, but responses are still empty.
What could be the possible reason for this?
Beta Was this translation helpful? Give feedback.
All reactions