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]: Version mismatch in manifest files #5386

Open
gaiksaya opened this issue Mar 11, 2025 · 0 comments
Open

[Bug]: Version mismatch in manifest files #5386

gaiksaya opened this issue Mar 11, 2025 · 0 comments
Labels
bug Something isn't working untriaged Issues that have not yet been triaged

Comments

@gaiksaya
Copy link
Member

Describe the bug

The input manifest contains version (3.0.0) and a qualifier (alpha1) as two separate values.

However, the build manifest (the interim manifest) generated after building all the components as well as the bundle or distribution manifest, generated assembling the components contains a single version key with qualifier already attached 3.0.0-alpha1

This discrepancy lead to some notable side effects. All the post build and test workflows/ jenkins libraries use version as the key for parsing data from opensearch-metrics cluster. See sample queries. However, data is indexed using build or dist manifest (in this case version=3.0.0-alpha1).

In order to retrieve the data, the version is retrieved from input manifest which is considered as the source of the truth. Because of this mismatch, it is now trying to run queries with 3.0.0 and returning no data. Example: https://build.ci.opensearch.org/job/integ-test-notification/3496/console

To reproduce

See the input manifest and compare with dist and build manifest.

Expected behavior

The version across all the manifests should be same. Either pick 3.0.0 with qualifier as alpha1 OR pick version: 3.0.0-alpha1
Accordingly modify the code base to accommodate this changes.

Screenshots

If applicable, add screenshots to help explain your problem.

Host / Environment

No response

Additional context

No response

Relevant log output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Issues that have not yet been triaged
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant