[CLI] Installation of operators in a new namespace fails
Description
Tested with Everest v0.9.1 version on gke cluster.
Install mysql operator initially in n1 namespace
Create a mysql database of 1 node.
Install mongodb operator in n2 namespace, it fails
Logs attached for everest service and operator.
Environment
None
Attachments
2
Activity
Show:
Manish Chawla June 5, 2024 at 5:20 AM
Tested with Everest v0.11.0-rc1 version and did not observe the issue.
Mayank Shah April 26, 2024 at 7:53 AM
What do you mean by installing recursively?
Manish Chawla April 23, 2024 at 1:52 PM
Hi , There were some fixes done in the past for this issue, but it seems that this issue was not fixed completely. To reproduce this issue, you will have to install operators in different namespaces recursively. It is mostly related to the Everest operator restart timing.
Mayank Shah April 23, 2024 at 1:12 PM
Hi
I was not able to reproduce this. Can you please retry and let me know if this was just a flake?
Tested with Everest v0.9.1 version on gke cluster.
Install mysql operator initially in n1 namespace
Create a mysql database of 1 node.
Install mongodb operator in n2 namespace, it fails
Logs attached for everest service and operator.