-
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
kube-builder: ClusterParams() returned result of unexpected type (%!s(<nil>))
on send-manifest
(on tx deployment update)
#152
Comments
kube-builder: ClusterParams() returned result of unexpected type (%!s(<nil>))
on send-manifest
kube-builder: ClusterParams() returned result of unexpected type (%!s(<nil>))
on send-manifest
(on tx deployment update)
still happens with provider 0.5.4, on akash network 0.32.2; have only observed this to happen on the Hurricane provider. It feels like this issue triggers when provider scans through the leases |
still happens with provider 0.6.2, on akash network 0.36.0 example with provider logs 152-hurricane.log
|
Spotted the same issue on Valdi provider for dseqs 17676873 and 17687779. Complete provider logs saved under
|
Todo: Test provider v0.6.5-rc6Provider v0.6.5-rc6 has some patches which try to fix this issue.
|
The first week has been pretty smooth with |
@troian let's release
|
Side note: I've opened a discussion to what might be a potential contributor (not the root cause) to this issue https://github.com/orgs/akash-network/discussions/760 |
It looks like Update 1
|
I am still seeing this error (
err="kube-builder: ClusterParams() returned result of unexpected type (%!s(<nil>))"
) on Hurricane provider with k8sv1.27.5
(delivered with kubesprayv2.23.0
) when sending-manifest to the provider (using the CLI) and that's not limited to theimage
update in SDL, but alsoenv
update.It is not always happening, but rather sporadically.
Todo
Provider logs:
The text was updated successfully, but these errors were encountered: