-
Notifications
You must be signed in to change notification settings - Fork 700
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
incorrect unreleased version warning #2737
Comments
looks like a bug. |
the validation problem happens when e.g. 1.24.0 is not released yet but the 1.25.0-alpha tag is already there on the master branch. we might just want to remove the warning to not confuse users and just return nil. |
the commit I'm using should be past of v1.24.0 which has already been released, it is a v1.25.0 prerelease. v1.25.0-alpha is for v1.25.0, not v1.24.0, it shouldn't be printing the minimum control plane version, we could take the current version and drop the prerelease portion for that log mesessge, or drop that part of the log entirely. |
I might have misunderstood the intent, but if not kubernetes/kubernetes#111615 is an attempt at logging what I think the intent was (drops the pre-release part to form a release version). I've put a |
commented on the PR. |
/assign thanks! |
@BenTheElder: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Is this a BUG REPORT or FEATURE REQUEST?
Choose one: BUG REPORT
Versions
kubeadm version (use
kubeadm version
):Environment:
kubectl version
): v1.25.0-alpha.3.348+d046a58de435a0uname -a
):What happened?
The previous "possibly unreleased" version is printed instead of the current one (off-by-one error)
kubernetes-sigs/kind#2846 (comment)
What you expected to happen?
This line:
Should read:
How to reproduce it (as minimally and precisely as possible)?
Run a kubeadm cluster with a pre-release Kubernetes version, I'm using d046a58de435a0
Anything else we need to know?
The text was updated successfully, but these errors were encountered: