iserver-test: Fix genpath script due to recent EC API change

[ericywl]

Closes #20119.

The EC API that we use to get available stack versions was recently changed to remove previously release SNAPSHOTs. This caused our integration server test to fail due to enforcing the upgrade path to be full SNAPSHOTs (for legacy reason, there's no real explanation for it) e.g. 9.2.0-SNAPSHOT -> 9.3.0-SNAPSHOT.

Since SNAPSHOTs are now only available for future releases, we will only use SNAPSHOTs as the tested version, and the previous versions in the upgrade path will use released ones instead. In our previous example, we want to test 9.3.0-SNAPSHOT, so the upgrade path will instead be 9.2.0 -> 9.3.0-SNAPSHOT since 9.2.0 is a released version.

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[mergify]

This pull request does not have a backport label. Could you fix it @ericywl? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.17 is the label to automatically backport to the 7.17 branch.
• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[carsonip]

so the upgrade path will instead be 9.2.0 -> 9.3.0-SNAPSHOT

q: is this a valid upgrade path though? I am trying to upgrade from 9.2.x to 9.3.0-SNAPSHOT manually and no luck so far

[ericywl]

q: is this a valid upgrade path though? I am trying to upgrade from 9.2.x to 9.3.0-SNAPSHOT manually and no luck so far

That's weird, it should be since we get the valid upgrade paths from the EC API itself. I will test it out myself and check with the ECH(?) team.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 673a7b1

History

• 💚 Build #8567 succeeded 784f6be
• 💚 Build #8559 succeeded f9c5b29

cc @ericywl

[ericywl]

I tried the iserver-test and there seems to be an error with Kibana?

found deployment plan errors: deployment [5b46d9a42c48739e3bc5e4d0524720fe] - [integrations_server][ec88aeb196764af7bba49ba3085d1f97]: caught error: "Plan change failed: Cluster not reachable: [kibana]... Please validate the cluster is in a healthy state and retry."

I will try to follow up on this next working day. On the other hand, the smoke test is also broken due to the API change: #20137.