-
Notifications
You must be signed in to change notification settings - Fork 104
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
[1.3.0][Distribution][BUG] Error building alerting components #312
Comments
I was able to reproduce this with The call with the arguments all filled out is the following:
Strangely enough, when you remove the Given that the default on main for the version (in
And we then do:
It should still be ending up with the same version internally ( |
@qreshi I just tried removing alerting from If the issue of alerting cannot be fixed soon, could we for now remove alerting from |
@tianleh Yeah you can remove it for now if it's blocking anything. Although, doesn't Alerting publish the Notification subproject locally before moving on to Index Management? I tried removing Alerting from the manifest locally and when I re-ran |
Also, I'm not really a gradle expert but looking up the gradle code, I saw this was where that error message was being generated from. We actually have a reference to the repos in a couple places. I tried removing all references to repositories.gradle in the Alerting project and then the error became:
Perhaps someone with Gradle expertise can identify if this is a configuration problem. |
I will wait for this issue to be resolved given the complicated situation. |
Based on my observation, the CI command |
Transfer the issue to alerting repo as this is directly pointing to their script errors. |
@peterzhuamazon Running that Alerting script with
@tianleh was also saying how this was working a few days ago. Is this possibly an issue introduced from OpenSearch. If it's a misconfiguration from our side that's incompatible with some OpenSearch change we can fix it but it would help if we knew what it was. Can anyone from the OpenSearch side lend a hand? |
Here are multiple command configurations and whether they succeed or pass in case it helps: Passes
Fails
The main trend seems to be whether we're using |
@qreshi are you able to identify what exactly is the issue related to non-snapshot dependencies? I just build alerting on my devdesktop and it runs to success.
|
Seems like this is something changes in the core as @qreshi mentioned, my build is based on local .m2, thus pass. It is technically blocking itself at this point. |
Share my story on this issue: Hope this will provide more insights. Thanks. |
@peterzhuamazon No, I'm not really sure what the discrepancy is. Would removing Alerting from the manifest to unblock the build and then reintroducing it fix the problem? |
Sure, please PR. |
@peterzhuamazon I tried to re-run
It can be reproduced with |
Actually, taking a closer look, it looks like I'm just missing |
I tried to run locally again since Peter confirmed that the build ran. The assembly command with
And now, strangely enough, even with the snapshot dependency, it's failing:
I just checked with @peterzhuamazon Can you check what the recent changes were to the OpenSearch snapshot repo? At this point even Alerting development is blocked. |
cc @CEHENKLE this seems like a major blocker at this point. Need some core engineers to help debug this. |
Also, recently I notice the run does not show error during builds and the upload complete, but the pipeline still show as failure. Will need to dig more into it to confirm what is happening. Thanks. |
Rabi is going to take a look. |
It looks like this commit caused this issue I tried building locally without this commit and the issue disappears. Next step - need to look into the changes as part of the commit and find a fix if possible or revert this commit |
@qreshi @zelinh @peterzhuamazon reverted the change in core that's probably causing the issue. Can you try building with @Rishikesh1159 will investigate the change to figure out a fix as he originally authored the PR and has more knowledge on it. |
@adnapibar I tried to build locally again and it looks like the snapshot version is working again. So it must have been that commit. |
I have figured out the issue specifically caused the failure is on security plugin in arm64 build. |
1.3.0 build success for a whole night, close this now. |
Thanks @qreshi @adnapibar @CEHENKLE |
Currently our distribution-build-opensearch is broken.
Here is the context of error.
To reproduce
Run
./build.sh manifests/1.3.0/opensearch-1.3.0.yml --component alerting --snapshot
.The text was updated successfully, but these errors were encountered: