ValueError: invalid literal for int() with base 10 about kube-opex-analytics HOT 11 CLOSED

That's what I was suspecting, though it's not documented in Kubernetes docs:)

Will fix that while considering milli, micro and nano too :)

from kube-opex-analytics.

Yep - looks better, thanks!

from kube-opex-analytics.

hi @agrushin,
Thank you to raise this issue, we're working to fix that.
A hotfix should be provided very shortly.

from kube-opex-analytics.

Dear @agrushin,
I just made a hot release, can you retry and let me know if that fixes the issue please?
Please set your image version to latest or 0.4.1-rc1

from kube-opex-analytics.

Thanks for a fast response.

Unfortunately, the same exception:

Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
    self._target(*self._args, **self._kwargs)
  File "backend.py", line 677, in create_metrics_puller
    k8s_usage.extract_nodes(pull_k8s('/api/v1/nodes'))
  File "backend.py", line 341, in extract_nodes
    node.memAllocatable = self.decode_memory_capacity(item['status']['allocatable']['memory'])
  File "backend.py", line 276, in decode_memory_capacity
    return int(cap_value)
ValueError: invalid literal for int() with base 10: '14162554060800m'

I believe this is because of .endswith() is case sensitive; json result have m in lower case, but function expected the upper.

from kube-opex-analytics.

I see, the problem is that the documentation does not state about the case sensitivity...

from kube-opex-analytics.

Can you try again please ?
The units are not considered non sensitive to case. Use version latest or 0.4.1-rc2

from kube-opex-analytics.

by the way, do you think that in your metrics m is for milli or mega? It's intriguing...

from kube-opex-analytics.

Heh, that's interesting, it is now about case; Looks like m here stands for a milli.

Checked on c5.4xlarge AWS ec2 instance with 32gb ram onboard. /api/v1/nodes endpoint returns

{
  "capacity": "31901716Ki",
  "allocatable": "30485060812800m"
}

from kube-opex-analytics.

sorry the issue was closed accidentally, can you try again with latest or 0.4.1-rc3 please?

from kube-opex-analytics.

cool.
If you like the tool, don't miss to give a star :) Thanks in advance.

from kube-opex-analytics.