Skip to content
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

failed to convert Descheduler minor version to float on start #1419

Open
der-eismann opened this issue May 29, 2024 · 5 comments
Open

failed to convert Descheduler minor version to float on start #1419

der-eismann opened this issue May 29, 2024 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@der-eismann
Copy link

der-eismann commented May 29, 2024

What version of descheduler are you using?

descheduler version: 0.30.0

Does this issue reproduce with the latest release?

yes

Which descheduler CLI options are you using?

--kubeconfig container/config-staging --policy-config-file container/policy.yaml

Please provide a copy of your descheduler policy config file

apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
nodeSelector: node.kubernetes.io/role=worker
evictLocalStoragePods: true
evictSystemCriticalPods: false
ignorePvcPods: false
strategies:
  "RemovePodsViolatingTopologySpreadConstraint":
    enabled: true
    params:
      includeSoftConstraints: true # soft = 'ScheduleAnyway' constraint
      nodeFit: true
      thresholdPriority: 200100 # only evict pods with 'default' pod priority

What k8s version are you using (kubectl version)?

kubectl version Output
$ kubectl version
Client Version: v1.30.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.0-eks-036c24b

What did you do?

Start the descheduler

What did you expect to see?

No warning

What did you see instead?

This on every start:

W0529 16:12:11.137539  715219 descheduler.go:248] failed to convert Descheduler minor version to float

I don't know why the GitVersion is used to parse here - it has a format of v20240519-v0.30.0. According to the docs of utilversion.ParseGeneric:

ParseGeneric parses a "generic" version string. The version string must consist of two or more dot-separated numeric fields (the first of which can't have leading zeroes), followed by arbitrary uninterpreted data (which need not be separated from the final numeric field by punctuation). For convenience, leading and trailing whitespace is ignored, and the version can be preceded by the letter "v". See also ParseSemantic.

The version it's trying to parse however is this (obtained from descheduler version - also see the double v):

v20240519-v0.30.0

My suggestion would be to either replace VERSION?=v$(shell date +%Y%m%d)-$(shell git describe --tags) in the Makefile with VERSION?=$(shell git describe --tags)-$(shell date +%Y%m%d) (but no idea what other implications that would have) or alternatively just parse versionInfo.Minor in the descheduler.go. But the way it is right now is just broken.

@der-eismann der-eismann added the kind/bug Categorizes issue or PR as related to a bug. label May 29, 2024
@a7i
Copy link
Contributor

a7i commented Jun 6, 2024

I may have tagged the release incorrectly. cc: @damemi

@damemi
Copy link
Contributor

damemi commented Jun 6, 2024

I don't see a git tag for v20240519-v0.30.0 in github, @a7i can you remember the order of the steps you did? In relation to https://github.com/kubernetes-sigs/descheduler/blob/master/docs/release-guide.md#release-process

That said we might be able to fix it by just tagging a new version. I don't know if we can delete the old k8s registry images but we might be able to

@a7i
Copy link
Contributor

a7i commented Jun 6, 2024

Yes, I followed those steps.

Looks like Descheduler version parsing broke in this commit dca2e58

I can submit a fix soon

@damemi
Copy link
Contributor

damemi commented Jun 6, 2024

@a7i no worries, I wasn't implying that you didn't follow those steps. I just meant that we could trace back through that flowchart to try to figure out what could have happened :) looks like you've tracked it down though

@der-eismann
Copy link
Author

Mega, thanks for the quick fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants