-
Notifications
You must be signed in to change notification settings - Fork 0
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
Generic Service Error #5
Comments
Error in
|
Can you check if the network is created? I think it should be created. It is just the ansible process not able to successfully deliver job status to evm. |
@psachin Nope. Network is not created in OpenStack Host. |
Oh I missed the line in error. The job launched failed,
This means that evm never handed over job to Ansible. There has to be something in |
Right. Job is not handed over to Ansible. That's why I don't see anything in |
I have checked awx log using Some issues regarding /var/lib/awx/projects folder: ansible/awx#857 & ansible/awx#1080 |
I encounter similar issue in my environment. I noticed Ansible role fails to enable in my environment. Raised my concern here ManageIQ/manageiq#15670 |
I can see that those paths( |
Also make sure you use create_instance branch of https://github.com/psachin/openstack-ansible-inside and NOT master |
docker logs -f awx_task throws this error many times,
There are lot similar issues filed on ansible/awx, https://github.com/ansible/awx/issues?utf8=%E2%9C%93&q=is%3Aissue+connection+reset+by+peer And developers are working on that in I guess, job launching is failed because awx has api component issue. I got directory @psachin Are you able to launch ansible playbook service in your environment(Gaprindishvili) with no error? |
rabbitmq Docker image is present.
Running containers
|
I'm aware of that. Just adding FYI into the thread. It was not intended anyone specific |
I had removed all Docker images and pulled again for latest code. Then restarted evm server. Still facing same problem. |
Today, we have tried to look into job details using |
The error
Generic Service Error: Server [EVM] Service [OpenStack | Create External Network] Provision Step [check_completed] Status [Error Processing check_completed]
is thrown when the service is ordered.
The Approval State shows "Approved" but Status "failed".
The automation.log is as follows :-
Probable Output:-
The task in the playbook should run successfully.
The text was updated successfully, but these errors were encountered: