-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Receiving "Deployment is not ready" error while the deployment is ready actually #264
Comments
And here is the output of the all resources, related to the process, while I see the "Deployment is not ready" error:
|
This looks like a bug, I'll have a look. You can get more info by |
Thanks! I already have |
I had a look and noticed that this error comes from Helm's wait logic, not from our code. So I would give a try to pass helm ls -a
helm status <name-of-the-release> Also, note that for |
Tested, even without
Here is the output of helm:
|
Seems this problem is related to the But I tested on the destination cluster (just test the copy back), and with While the pv-migrate waits for readiness, I see the Service in the active state, here are the details:
And I can connect to this node port on the source cluster from the destination cluster (using the externtal IP of any node) via telnet:
So, the network connection is not a problem. So, could you please describe what exactly it tries to wait? And maybe make the more verbose debug logging to cath it? |
Also, specifying the source node IP address explicitly using |
And will be good to add to the debug logs the output of the Helm chart deployment status, at least |
Describe the bug
When I start the pv-migrate, it creates the deployment, but in the debug log I see errors like:
But at the same time, via kubectl I see that the deployment is ready:
The log level is debug, and no additional messages were displayed.
So, any ideas on what can cause this problem?
How can I enable more verbose logging to understand what's happening and why it is not detecting the ready status?
Console output
The text was updated successfully, but these errors were encountered: