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

bug: Misleading error message when no successors available #1022

Open
joelanford opened this issue Jul 9, 2024 · 5 comments
Open

bug: Misleading error message when no successors available #1022

joelanford opened this issue Jul 9, 2024 · 5 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. v1.x Issues related to OLMv1 features that come after 1.0

Comments

@joelanford
Copy link
Member

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:

    message: 'error upgrading from currently installed version "6.0.1": no package
      "cockroachdb" matching version "6.0.0" found'

This makes it sound like:

  • there just isn't a 6.0.0 version in the catalog
  • if there was a 6.0.0 version (there is), the upgrade would proceed (it doesn't, because 6.0.0 is not a successor)

I expected something along the lines of (where the list of best available successors would be sugar on top):

    message: 'error upgrading from currently installed version "6.0.1": desired package "cockroachdb" with version range "6.0.0" does not match any successor of "6.0.1", which include "6.0.3" (highest-available z-update) and "6.4.0" (highest available y-update)
@joelanford 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
@joelanford joelanford added this to OLM v1 Jul 9, 2024
@itroyano
Copy link
Contributor

/assign

@itroyano itroyano removed their assignment Jul 16, 2024
@dhoover103
Copy link

/assign

@joelanford
Copy link
Member Author

@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 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
@LalatenduMohanty
Copy link
Member

@joelanford mentioned that he has already fixed it, so assigning it to him to cross check.

@joelanford
Copy link
Member Author

I cross checked. I don't think I did fix this actually. My mistake!

@joelanford joelanford removed their assignment Sep 17, 2024
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. v1.x Issues related to OLMv1 features that come after 1.0
Projects
Status: No status
Development

No branches or pull requests

5 participants