Skip to content

Conversation

@boonware
Copy link
Contributor

@boonware boonware commented Dec 8, 2025

Issue

MASAIB-1626

Description

  • To determine if the upgrade path is valid the code currently performs the check aiservice_channel in aiservice_upgrade_path, however, aiservice_upgrade_path is a dictionary so this check is insufficient; we need to check if (a) the currently installed AI Service channel is a valid key in the dictionary, and (b) if the values for this key include the channel version we want to upgrade to. The PR adds a new filter function to perform this check.
  • Another filter function is added to get the default target channel from the dictionary when a user does not supply one. The first entry in a list of target versions is taken as the default.
  • Includes unit tests for the new filter functions. Even though the pipeline does not currently run these tests they are useful locally for a developer to run.

Test Results

AI Service upgrade has been successfully tested with these changes included in custom branch #2021


⚠️ Notes for Reviewers

  • Ensure you have understood the PR guidelines in the Playbook before proceeding with a review.
  • Ensure all sections in the PR template are appropriately completed.

karol-czarnecki
karol-czarnecki previously approved these changes Dec 8, 2025
Copy link
Contributor

@karol-czarnecki karol-czarnecki left a comment

Choose a reason for hiding this comment

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

lgtm

@boonware boonware marked this pull request as ready for review December 9, 2025 09:13
@boonware boonware requested a review from a team as a code owner December 9, 2025 09:13
karol-czarnecki
karol-czarnecki previously approved these changes Dec 9, 2025
Copy link
Contributor

@karol-czarnecki karol-czarnecki left a comment

Choose a reason for hiding this comment

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

lgtm

# does not supply a target upgrade version.
aiservice_upgrade_path:
9.1.x: 9.2.x-feature
9.1.x: [9.2.x-feature]
Copy link
Member

Choose a reason for hiding this comment

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

I thought there was always a one to one mapping for the upgrade path i.e. you can't have more than one "to" channel to upgrade too. For the 9.2.x-feature, that is the only channel until 9.2.x comes out, at which point 9.2.x-feature would not be a valid option.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Table is updated to remove the list and allow only one upgrade target version.

@@ -0,0 +1,70 @@
# -----------------------------------------------------------
Copy link
Contributor

Choose a reason for hiding this comment

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

Errrrrrm, I hope this is just a mistake of putting the wrong license file in place, rather than copying product code into this repo?

ansible-devops is open source code, licensed under the EPL, we can not published licensed materials in this repository

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@durera durera changed the title [patch] fix check for upgrade compatibility [patch] Fix check for AIService upgrade compatibility Dec 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants