Skip to content

Conversation

@cadenmarchese
Copy link
Collaborator

@cadenmarchese cadenmarchese commented Nov 19, 2025

Which issue this PR addresses:

Fixes #itn-2025-00300

What this PR does / why we need it:

  • Version validation populates the version if not specified by the user, so we need to run it before we do static validation so that static validation can determine if the SKU is valid or not.

  • Better error handling when:

  1. no default ocp version is set in frond end cache
  2. no default ocp version can be retrieved from the sync (every 10 seconds) in version update change feed
  3. better error explanation to the user/cu to suggest them using --verison param when there is no default ocp version available

Test plan for issue:

  • Unit tests
  • test in local RP, OR test in canary

* static validation depends on cluster version
* if unset, static validation can't complete
* and results in a SKU invalid error.
@cadenmarchese cadenmarchese added bug Something isn't working work-in-progress labels Nov 19, 2025
@Tof1973 Tof1973 force-pushed the populate-version-before-static-validation branch 5 times, most recently from 7397493 to b811eea Compare November 25, 2025 11:22
@Tof1973 Tof1973 force-pushed the populate-version-before-static-validation branch 4 times, most recently from c330374 to bc4cd90 Compare November 25, 2025 14:47
@Tof1973
Copy link
Collaborator

Tof1973 commented Nov 25, 2025

In E2E test, when FE starts and cluster creation is done immediately, we reach the validateInsallVersion before OCP versions are initialized. This was not an issue before as validation was done after ValidateNewCluster which takes few seconds, but now we need to do it before and so we need to make sure OCP versions are already initialized.

@Tof1973 Tof1973 force-pushed the populate-version-before-static-validation branch from 255cc9c to 66fd098 Compare November 25, 2025 16:20
@Tof1973
Copy link
Collaborator

Tof1973 commented Nov 25, 2025

The current fix has been tested in local dev and E2E and it is working and fixing the issue in local dev.
We now need also to validate the test in Canary, but that is not easy due to CCAO.

Copy link
Member

@mociarain mociarain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Left a question that's not blocking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working ready-for-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants