-
Notifications
You must be signed in to change notification settings - Fork 4
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
provider 0.3.2-rc2
panics because one of two SDL deployments services lacks global: true
#112
Comments
New logs with provider SDL tested => https://transfer.sh/mKzHRYPPNj/deploy.yaml.1
Entire provider log https://transfer.sh/tpLhHlvWRn/logs.log |
no panic with the provider
as you can see I've also made sure the wordpress service can see the db (the one w/o the global:true):
|
Provider-services
0.3.2-rc2
experiences a panic due to an SDL issue with two deployments , where one of them does not expose a global service (has noglobal: true
).provider
version
provider-services v0.3.2-rc2
sandbox v0.23.2-rc3
SDL
I've tested this SDL, have also removed the
33060
port since it should not be there generally:https://github.com/akash-network/awesome-akash/blob/c3a8fedb5685078e7313be51732e178b6b3ca3f8/wordpress/deploy.yaml#L35-L37
Here is a working SDL where I've added
global: true
to thedb
service, and removed33060
port which should not be there: https://gist.githubusercontent.com/andy108369/733cd5c4a191211885808469d7b4ec35/raw/420c5ecc2c2dc1bcb3cbcb5a3fee9d1d0eca37d1/wordpress-working-sdl.yamlLogs
All provider logs:
https://transfer.sh/QTY7vMopwi/provider.logs
The text was updated successfully, but these errors were encountered: