You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the backport of various build changes to 2.18 in d737c7b, we see errors in 2.18 builds searching for yugabyte-db/managed/node-agent/version_metadata.json. We need to investigate and potentially roll back the backported changes to resolve.
Warning: Please confirm that this issue does not contain any sensitive information
I confirm this issue does not contain any sensitive information.
The text was updated successfully, but these errors were encountered:
Summary:
Updates to gen_version_info.py backported to 2.18 via D25956 change the paths related to version_metadata.json. This appears to be causing build
issues where yugabyte-db/managed/node-agent/version_metadata.json is expected but missing.
The backported changes indicate: sys.path should be set differently in gen_version_info.py after it was moved from build-support to python/yugabyte in
9d99f77.
However, 9d99f77 has not been backported to 2.18 as of yet.
Reverting the backported change.
Jira: DB-6816
Test Plan: Jenkins: rebase: 2.18, compile only, urgent
Reviewers: mbautin, smishra
Differential Revision: https://phorge.dev.yugabyte.com/D26059
Jira Link: DB-6816
Description
Following the backport of various build changes to 2.18 in d737c7b, we see errors in 2.18 builds searching for yugabyte-db/managed/node-agent/version_metadata.json. We need to investigate and potentially roll back the backported changes to resolve.
Warning: Please confirm that this issue does not contain any sensitive information
The text was updated successfully, but these errors were encountered: