-
Notifications
You must be signed in to change notification settings - Fork 56
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
bug: Misleading error message when no successors available #1022
Comments
joelanford
added
kind/bug
Categorizes issue or PR as related to a bug.
v1.0
Issues related to the initial stable release of OLMv1
labels
Jul 9, 2024
26 tasks
/assign |
/assign |
@itroyano and @dhoover103, I'm refactoring this area of code in #1033, so you may want to hold off or branch off of that PR. |
everettraven
added
v1.x
Issues related to OLMv1 features that come after 1.0
and removed
v1.0
Issues related to the initial stable release of OLMv1
labels
Jul 23, 2024
4 tasks
@joelanford mentioned that he has already fixed it, so assigning it to him to cross check. |
I cross checked. I don't think I did fix this actually. My mistake! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a scenario setup with 6.0.1 installed, where I updated the spec.version to 6.0.0 with upgrade policy enforcement enabled.
I got the following error message:
This makes it sound like:
I expected something along the lines of (where the list of best available successors would be sugar on top):
The text was updated successfully, but these errors were encountered: