-
Notifications
You must be signed in to change notification settings - Fork 80
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] Unable to run opensearch-benchmark in test mode #245
Comments
Thanks for bringing this to our attention Kunal. I've also been experiencing this issue recently in the integration tests and am currently in the process of identifying a fix. Looks like the issue arises for users who are starting from scratch and is not detected for users who have workloads already preloaded and unzipped. |
Curious to see if this issue only occurs when we provision an opensearch cluster via OSB. I've been using an external host and found that it works with that. This is good to note since we can further be sure to test changes with external and internal hosts. |
i'm currently hitting this issue when running OSB against a remote endpoint:
Note that I get the same stacktrace and error on running |
Thanks for the heads up @kartg. I've been able to get it to work with an external host. Will dive further into this.
|
@kartg @kotwanikunal Could we have more context on your setups:
|
Yes, I have setup a cluster locally.
Tried pulling the latest and running again, still the same issue. |
@kotwanikunal Could you try the following:
|
I'm running OSB on macOS 12.6.3 on an Intel-powered Macbook. My target cluster is on OpenSearch 1.3
|
@IanHoang the error seems to originate from executing this git command: opensearch-benchmark/osbenchmark/utils/git.py Line 124 in a1f4550
and then trying to parse its output: opensearch-benchmark/osbenchmark/utils/git.py Line 137 in a1f4550
Here's the output of that git command against the directory where the workloads repo is cloned:
I'm guessing that the "origin" entry in this list is causing the parsing to fail (since it has no EDIT: Can confirm that I can repro this error signature with a simple Python script:
Seems related to the new |
It looks like fixing this will need either:
In the meantime, here's a rather ugly workaround:
and the change the following line:
to something like:
(or any string other than |
|
While trying to reproduce this scenario by cloning the workloads repository and checking the refs:
There are no entries without a |
@gkamat interesting, maybe it's a change in the
|
I have the same output as @kartg
|
I'm using the version that gets installed by
Which platform are you using? |
M1 Macbook Pro on Ventura 13.2.1 |
That is a rather new version of |
Nah, FTP just sorts |
Just rebuilt |
@IanHoang, changing the
|
@kartg Thanks for diving into this! Just caught up on the thread. TL;DR:Reproduced the issue in a clean Ubuntu environment and can confirm that the issue lies in I'll open a PR to address this fix. I'm in the same boat as Govind and am using an earlier version of
Reproduced issue in Ubuntu:Confirmed that issue resides in
Logs shows same error:
Applying the recommended fix by @gkamatAdded recommended fix by @gkamat to
|
…nsearch-project#245) Signed-off-by: Ian Hoang <hoangia@amazon.com>
… (#246) Signed-off-by: Ian Hoang <hoangia@amazon.com> Co-authored-by: Ian Hoang <hoangia@amazon.com>
Closing issue as this has been resolved in PR #246 |
Describe the bug
To Reproduce
Expected behavior
Logs
More Context (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: