Skip to content
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

Porter unable to install bundle and giving rpc errors #2473

Closed
nitishdsharma opened this issue Nov 29, 2022 · 4 comments
Closed

Porter unable to install bundle and giving rpc errors #2473

nitishdsharma opened this issue Nov 29, 2022 · 4 comments

Comments

@nitishdsharma
Copy link

Creating a new porter bundle and trying to install it locally but its rendering rpc errors on porter install command.

Error messages

rpc error: code = DeadlineExceeded desc = server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: localhost:27018, Type: Unknown }, ] } could not retrieve the installation record: could not read storage schema document: rpc error: code = DeadlineExceeded desc = server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: localhost:27018, Type: Unknown }, ] } could not retrieve the installation record: could not read storage schema document: rpc error: code = DeadlineExceeded desc = server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [{ Addr: localhost:27018, Type: Unknown }, ] }

@VinozzZ
Copy link
Contributor

VinozzZ commented Nov 29, 2022

Hi there, thanks for reporting your issue. Do you mind to share which version of porter you are using and the porter command you ran that produced this error?

@carolynvs
Copy link
Member

By default, if you do not configure differently in ~/.porter/config.yaml, Porter will use the mongodb-docker storage plugin, which runs a mongo container on porter 27018 named porter-mongodb-docker-plugin.

$ docker ps
...
b56beddb3f0e   95a66c5d5e6c   "docker-entrypoint.s…"   6 weeks ago   Up 6 weeks   0.0.0.0:27018->27017/tcp  porter-mongodb-docker-plugin

Can you check your porter configuration file (located in ~/.porter, named config.toml or config.yaml or config.json) and verify that you do not have a storage plugin set? Then run docker ps to see if docker is running, and if you have that container started?

One cause of that error is that porter was unable to start the mongo container and then it fails to connect.

@nitishdsharma
Copy link
Author

nitishdsharma commented Dec 15, 2022

@VinozzZ Thanks for replying.
The porter version is porter v1.0.1 (91676a6)
Command which triggered this issue: porter install cloudcasa --param cluster_id=

@kichristensen
Copy link
Contributor

@nitishdsharma Sorry for lack for reply, because the issue is so old and the version of Porter is old, I will close it. If you are still having problems please create a new issue.

@kichristensen kichristensen closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants