Skip to content

Bug: Kubelink Requests getting Failed for gRPC method GetAppDetails  #5008

@tayalrishabh96

Description

@tayalrishabh96

📜 Description

Kubelink requests fail with below error :
{"level":"error","ts":1713965180.331496,"caller":"appList/AppListingRestHandler.go:1074","msg":"error in fetching app detail","err":"rpc error: code = Unknown desc = release not exists for this app"
This happens even when application is not deployed
Ideally request should not go to kubelink in the first place.

Affected areas

CD

Additional affected areas

None

Prod/Non-prod environments?

Prod

Is User unblocked?

Yes

How was the user un-blocked?

None

Impact on Enterprise

Unnecessarily requests are going to Kubelink and failing

👟 Steps to replicate the Issue

  1. create an application with deployment app type as helm.
  2. create CI, CD but do not deploy
  3. go to app details page and parallelly check orchestrator logs.

👍 Expected behavior

Requests should not go to kubelink searching for release as application is not even deployed yet.

👎 Actual Behavior

Kubelink throws an error that release not exists

☸ Kubernetes version

NA

Cloud provider

NA

🌍 Browser

Chrome

✅ Proposed Solution

NA

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

AB#9576

Metadata

Metadata

Labels

bugSomething isn't workingpager-dutyBugs / Issues found while on pager duty

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions