-
-
Notifications
You must be signed in to change notification settings - Fork 751
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
"NotUniqueError: Tried to save duplicate unique keys" on st2 register content #3933
Comments
Seeing it again on StackStorm first install. The worst thing is that the error doesn't result in I think it should fail on failure like this, so we stop the provision on that error instead of going further. @Kami do you think that's something at minimum we can fix? |
More of this:
|
I am also facing same issue
|
I fixed it by
Also st2chatops 2.10 is dependent on nodejs > nodejs-8.0, which doesn't get install with the single command installation process, so I installed it from |
I can confirm i'm seeing this too, as reported in #4626. Here's a gist of my install log: https://gist.github.com/nmaludy/875acebf3772d10384df5eccfc2605e9 I noticed that this only happened when installing on CentOS 7, i couldn't reproduce using Ubuntu 16.04. Here are my steps to reproduce: git clone https://github.com/StackStorm/st2vagrant
cd st2vagrant
BOX=centos/7 vagrant up |
I will try to have a look this week. From a quick glance - some of those errors (trigger type already exists) are not fatal. IIRC, we already made some changes in the past to log those errors under DEBUG instead of ERROR so it doesn't confuse the user, but it may need more work (and there might be another face hiding there which is fatal). |
I was able to reproduce this issue today. It's indeed related to a non-fatal race - we try to register internal trigger types on each service startup and during register content script run. Operation itself is idempotent so failure isn't fatal (it simply means internal trigger has already been registered by another service). Only problem is with logging - we log error as fatal, even though it's not. I will open a PR which fixes the logging and logs this error under |
Getting the following error on Ubuntu 16 latest
stable
st2 packages during thest2ctl --register-all
(first & clean run):Happens randomly, probably some race and I couldn't reproduce it consistently so far.
Hence, still good to leave it here until we or someone else finds more info.
The text was updated successfully, but these errors were encountered: