Closed ajaydevtron closed 6 months ago
We are getting below error in inception pod when we upgrade Devtron to latest version.
Starting workers {"reconcilerGroup": "installer.devtron.ai", "reconcilerKind": "Installer", "controller": "installer", "worker count": 1} url changed updating 2024-02-01T07:40:52.132Z ERROR controllers.Installer error while requesting {"error": "Get \"http://metadata.google.internal/computeMetadata/v1/instance/tags\": dial tcp: lookup metadata.google.internal on 10.100.0.10:53: no such host", "requestError": "json: unsupported type: func() (io.ReadCloser, error)", "error": "Get \"http://metadata.google.internal/computeMetadata/v1/instance/tags\": dial tcp: lookup metadata.google.internal on 10.100.0.10:53: no such host"} github.com/go-logr/zapr.(*zapLogger).Error /go/pkg/mod/github.com/go-logr/zapr@v0.3.0/zapr.go:132 github.com/devtron-labs/inception/pkg/providerIdentifier/providers.(*IdentifyGoogle).IdentifyViaMetadataServer /workspace/pkg/providerIdentifier/providers/google.go:37 panic: send on closed channel goroutine 247 [running]: github.com/devtron-labs/inception/pkg/providerIdentifier/providers.(*IdentifyGoogle).IdentifyViaMetadataServer(0xc000ccfa70, 0xc00018cb40) /workspace/pkg/providerIdentifier/providers/google.go:38 +0x3b8 created by github.com/devtron-labs/inception/pkg/providerIdentifier.(*ProviderIdentifierServiceImpl).IdentifyProvider /workspace/pkg/providerIdentifier/ProviderIdentifierService.go:61 +0x479
Inception pod shouldn’t through this error.
Currently inception through above error.
1.25
Chrome
No response
AB#9525
https://github.com/devtron-labs/inception/pull/20 This has been fixed in this PR and the latest version v0.6.29 contains this fix.
📜 Description
We are getting below error in inception pod when we upgrade Devtron to latest version.
👟 Reproduction steps
👍 Expected behavior
Inception pod shouldn’t through this error.
👎 Actual Behavior
Currently inception through above error.
☸ Kubernetes version
1.25
Cloud provider
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#9525