-
Notifications
You must be signed in to change notification settings - Fork 51
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
cannot bootstrap simple-manager (version 3.2) on existing ubuntu 14.04 vm. #136
Comments
Usually, this happens when the provider context has already been posted. Where exactly are you trying to bootstrap? Is it a clean machine? |
I'm not sure. I mean it is a clean machine at first. |
I tried again with a clean VM. but the result is the same. Still |
Are you running on Openstack by any chance and using a volume as your storage? Maybe you already bootstrapped once and am now using that same volume that already contains elasticsearch indices? |
I have same problem, 409 Conflict error on setting provider context. I install cloudify 3.2.1 on Openstack Kilo with using volume. Following the installation manual from getcloudify.org: http://getcloudify.org/guide/3.2/getting-started-bootstrapping.html I tried to increase the task-retries to 30, no good. Particularly the provider context error: initially, it is 500 Internal server error, then became 504 Gateway Time-out, at last became 409 Conflict error. what is the problem here |
The bootstrap can successfully download the docker image. and start a new container.
But after that. one of a
curl --fail -XPOST localhost:8101/provider/context?update=False
command failed. The error logs says409 CONFLICT
partial logs.
The text was updated successfully, but these errors were encountered: