search

kubecost / features-bugs

A public repository for filing of Kubecost feature requests and bugs. Please read the issue guidelines before filing an issue here.
0 stars 0 forks source link

Fix PV costs on Alibaba Cloud #74

Closed ivankube closed 3 weeks ago

ivankube commented 1 year ago

Describe the bug
Kubecost is not recognizing PV cost on Alibaba

To Reproduce
Steps to reproduce the behavior:

  1. Deploy Kubecost on Alibaba
  2. Check UI and logs

Expected behavior
Kubecost displays PV costs

Screenshots
1fva81lgde9039-image 1fva81lgded2f3-image

Collect logs (please complete the following information):


│ cost-model 2023-04-12T07:56:07.020186163Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::700 │ 
│ cost-model 2023-04-12T07:56:07.020214978Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::330 │ 
│ cost-model 2023-04-12T07:56:07.020234555Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::1101 │ 
│ cost-model 2023-04-12T07:56:07.020256297Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::300 │ 
│ cost-model 2023-04-12T07:56:07.020275144Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::363 │ 
│ cost-model 2023-04-12T07:56:07.020293299Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::500 │ 
│ cost-model 2023-04-12T07:56:07.020310814Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_ssd::21 │ 
│ cost-model 2023-04-12T07:56:07.020327747Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::500 │ 
│ cost-model 2023-04-12T07:56:07.020344373Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::300 │ 
│ cost-model 2023-04-12T07:56:07.020364222Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::350 │ 
│ cost-model 2023-04-12T07:56:07.020382842Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::380 │ 
│ cost-model 2023-04-12T07:56:07.020402836Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::385 │ 
│ cost-model 2023-04-12T07:56:07.02042316Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::341 │ 
│ cost-model 2023-04-12T07:56:07.02044051Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::1045 │ 
│ cost-model 2023-04-12T07:56:07.020457867Z ERR Persistent Volume pricing not found for PV with feature: ap-southeast-1::data::cloud_efficiency::500```

**Please share the support case, if any**  
https://kubecost.zendesk.com/agent/tickets/3787
AjayTripathy commented 1 year ago

cc @teevans and @avrodrigues5 for triage.

teevans commented 1 year ago

@allyleonce - Can you get this on the burndown board plz?

avrodrigues5 commented 1 year ago

@ivankube ,

I see the user hasnt notified you on the four things asked on slack thread

I put a fix as part of PR https://github.com/opencost/opencost/pull/1881 which could potential address the PV errors that come up in the logs.

TLDR: If user had given key and secret as custom pricing it would make the key and secret empty string. I verified it and fix it. Let me know if this address users concern!

ivankube commented 1 year ago

Thanks! I'm checking with the user.

chipzoller commented 6 months ago

Transferred to the appropriate repo.

Is this issue resolved? It pertains to Alibaba, a current initiative we have, so need status. cc @AjayTripathy or @avrodrigues5

avrodrigues5 commented 6 months ago

Just to be safe, keep this issue open and see how kubecost with aggregator is installed on Alibaba cloud. If PV costs are shown accurately as part of this current initiative. This was pre aggregator times.

I tested this in us-east region in dec 22 and if i remember correctly working on this issue, if user would have submitted a default pricing it would have resulted in those error logs incorrectly which was corrected in PR. I no longer have access to that slack thread to confirm if user got back to @ivankube if issue was resolved.

ivankube commented 6 months ago

I checked and they didn't confirm if the issue was resolved.

chipzoller commented 3 weeks ago

Hello, in an effort to consolidate our bug and feature request tracking, we are deprecating using GitHub to track tickets. If this issue is still outstanding and you have not done so already, please raise a request at https://support.kubecost.com/.