Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Unable to delete Ansible repository -> https://github.com/jonnyfiveiq/Ansible_Playbooks Version-Release number of selected component (if applicable): 5.8.0 How reproducible: Always Steps to Reproduce: 1. Navigate to Automate -> Ansible -> Repository 2. select the repository(https://github.com/jonnyfiveiq/Ansible_Playbooks) and click on delete repository. 3. The specific mentioned repository cannot be deleted. Seems like some repos are not able to delete. Actual results: The mentioned repository is not able to delete. Expected results: The mentioned repository should be deleted Additional info: If we add new repository with same git path then it will delete the old repository and add a new one.
I also ran into this. Stack trace here: [----] E, [2017-04-05T14:58:41.108536 #15875:32f140] ERROR -- : MIQ(MiqQueue#deliver) Message id: [10000000000403], Error: [{:status=>404, :headers=>{"date"=>"Wed, 05 Apr 2017 18:58:41 GMT", "server"=>"nginx/1.10.2", "content-type"=>"application/json", "x-api-time"=>"0.033s", "allow"=>"GET, PUT, PATCH, DELETE, HEAD, OPTIONS", "content-language"=>"en", "vary"=>"Accept,Accept-Language,Cookie", "x-api-node"=>"localhost", "connection"=>"close", "transfer-encoding"=>"chunked"}, :body=>"{\"detail\":\"Not found.\"}"}] [----] E, [2017-04-05T14:58:41.108798 #15875:32f140] ERROR -- : [AnsibleTowerClient::ResourceNotFoundError]: {:status=>404, :headers=>{"date"=>"Wed, 05 Apr 2017 18:58:41 GMT", "server"=>"nginx/1.10.2", "content-type"=>"application/json", "x-api-time"=>"0.033s", "allow"=>"GET, PUT, PATCH, DELETE, HEAD, OPTIONS", "content-language"=>"en", "vary"=>"Accept,Accept-Language,Cookie", "x-api-node"=>"localhost", "connection"=>"close", "transfer-encoding"=>"chunked"}, :body=>"{\"detail\":\"Not found.\"}"} Method:[rescue in deliver] [----] I, [2017-04-05T14:58:41.108932 #7689:32f140] INFO -- : MIQ(MiqSmartProxyWorker::Runner#worker_monitor_drb) MIQ(MiqSmartProxyWorker::Runner) Initializing DRb Connection to MiqServer with ID=[10000000000001], NAME=[EVM], PID=[12931], GUID=[5a61ff7e-1a2c-11e7-b43d-5254001827c5] DRb URI=[druby://127.0.0.1:44650] [----] E, [2017-04-05T14:58:41.109033 #15875:32f140] ERROR -- : /opt/rh/cfme-gemset/gems/ansible_tower_client-0.10.0/lib/ansible_tower_client/middleware/raise_tower_error.rb:18:in `on_complete' /opt/rh/cfme-gemset/gems/faraday-0.9.2/lib/faraday/response.rb:9:in `block in call' /opt/rh/cfme-gemset/gems/faraday-0.9.2/lib/faraday/response.rb:57:in `on_complete' /opt/rh/cfme-gemset/gems/faraday-0.9.2/lib/faraday/response.rb:8:in `call' /opt/rh/cfme-gemset/gems/faraday-0.9.2/lib/faraday/request/url_encoded.rb:15:in `call' /opt/rh/cfme-gemset/gems/faraday_middleware-0.10.1/lib/faraday_middleware/response/follow_redirects.rb:76:in `perform_with_redirection' /opt/rh/cfme-gemset/gems/faraday_middleware-0.10.1/lib/faraday_middleware/response/follow_redirects.rb:64:in `call' /opt/rh/cfme-gemset/gems/faraday_middleware-0.10.1/lib/faraday_middleware/request/encode_json.rb:23:in `call' /opt/rh/cfme-gemset/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response' /opt/rh/cfme-gemset/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request' /opt/rh/cfme-gemset/gems/faraday-0.9.2/lib/faraday/connection.rb:140:in `get' /opt/rh/cfme-gemset/gems/ansible_tower_client-0.10.0/lib/ansible_tower_client/api.rb:87:in `method_missing' /opt/rh/cfme-gemset/gems/ansible_tower_client-0.10.0/lib/ansible_tower_client/collection.rb:30:in `find' /var/www/miq/vmdb/app/models/manageiq/providers/ansible_tower/shared/automation_manager/configuration_script_source.rb:69:in `block in delete_in_provider' /var/www/miq/vmdb/app/models/provider.rb:49:in `with_provider_connection' /var/www/miq/vmdb/app/models/manageiq/providers/ansible_tower/shared/automation_manager.rb:5:in `with_provider_connection' /var/www/miq/vmdb/app/models/manageiq/providers/ansible_tower/shared/automation_manager/configuration_script_source.rb:68:in `delete_in_provider' /var/www/miq/vmdb/app/models/miq_queue.rb:347:in `block in deliver' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:91:in `block in timeout' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `block in catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:33:in `catch' /opt/rh/rh-ruby23/root/usr/share/ruby/timeout.rb:106:in `timeout' /var/www/miq/vmdb/app/models/miq_queue.rb:343:in `deliver' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:107:in `deliver_queue_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:135:in `deliver_message' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:153:in `block in do_work' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:147:in `loop' /var/www/miq/vmdb/app/models/miq_queue_worker_base/runner.rb:147:in `do_work' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:334:in `block in do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:331:in `loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:331:in `do_work_loop' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:153:in `run' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:128:in `start' /var/www/miq/vmdb/app/models/miq_worker/runner.rb:21:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:339:in `block in start_runner' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork' /opt/rh/cfme-gemset/gems/nakayoshi_fork-0.0.3/lib/nakayoshi_fork.rb:24:in `fork' /var/www/miq/vmdb/app/models/miq_worker.rb:337:in `start_runner' /var/www/miq/vmdb/app/models/miq_worker.rb:348:in `start' /var/www/miq/vmdb/app/models/miq_worker.rb:266:in `start_worker' /var/www/miq/vmdb/app/models/miq_worker.rb:150:in `block in sync_workers' /var/www/miq/vmdb/app/models/miq_worker.rb:150:in `times' /var/www/miq/vmdb/app/models/miq_worker.rb:150:in `sync_workers' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:53:in `block in sync_workers' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `each' /var/www/miq/vmdb/app/models/miq_server/worker_management/monitor.rb:50:in `sync_workers' /var/www/miq/vmdb/app/models/miq_server.rb:160:in `start' /var/www/miq/vmdb/app/models/miq_server.rb:251:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:65:in `start' /var/www/miq/vmdb/lib/workers/evm_server.rb:91:in `start' /var/www/miq/vmdb/lib/workers/bin/evm_server.rb:4:in `<main>' [----] I, [2017-04-05T14:58:41.109202 #15875:32f140] INFO -- : MIQ(MiqQueue#delivered) Message id: [10000000000403], State: [error], Delivered in [0.074849233] seconds [----] I, [2017-04-05T14:58:41.110477 #15875:32f140] INFO -- : MIQ(MiqQueue#m_callback) Message id: [10000000000403], Invoking Callback with args: ["Finished", "error", "{:status=>404, :headers=>{\"date\"=>\"Wed, 05 Apr 2017 18:58:41 GMT\", \"server\"=>\"nginx/1.10.2\", \"content-type\"=>\"application/json\", \"x-api-time\"=>\"0.033s\", \"allow\"=>\"GET, PUT, PATCH, DELETE, HEAD, OPTIONS\", \"content-language\"=>\"en\", \"vary\"=>\"Accept,Accept-Language,Cookie\", \"x-api-node\"=>\"localhost\", \"connection\"=>\"close\", \"transfer-encoding\"=>\"chunked\"}, :body=>\"{\\\"detail\\\":\\\"Not found.\\\"}\"}", "nil"] [----] I, [2017-04-05T14:58:41.110632 #15875:32f140] INFO -- : MIQ(MiqTask#update_status) Task: [10000000000011] [Finished] [Error] [{:status=>404, :headers=>{"date"=>"Wed, 05 Apr 2017 18:58:41 GMT", "server"=>"nginx/1.10.2", "content-type"=>"application/json", "x-api-time"=>"0.033s", "allow"=>"GET, PUT, PATCH, DELETE, HEAD, OPTIONS", "content-language"=>"en", "vary"=>"Accept,Accept-Language,Cookie", "x-api-node"=>"localhost", "connection"=>"close", "transfer-encoding"=>"chunked"}, :body=>"{\"detail\":\"Not found.\"}"}]
Interesting additional note, may require a new BZ - if you add a new repo and give it the same name, it will overwrite the old repo with the new values. In my case this allowed me to fix a typo in the SCM URL despite not being able to edit/delete the old repo.
Neha, Please see https://bugzilla.redhat.com/show_bug.cgi?id=1437042. This seems to be a duplicate of that. regards, James
This is for the Ansible Inside, versus that bug is for Ansible Tower. I am not sure if they have the same problem.
Neha/Cameron, Can you do the following test, 1. add 2 to 3 repos 2. delete 1 of them 3. after a few moment, refresh your CF UI and see if the deletion is successful. Please let me know. Thanks, James PS Cameron, Ansible Inside is really a Ansible Tower embedded in CFME.
Hello James, Its working now.We are able to delete the repositories and after 2-3 minutes of refresh, it is cleared from the queue. This has been verified after deleting 4-5 repos. May I know what all changes you have made? or, have you applied any hot fix for the same. Thanks and Regards, Neha Chugh
Neha, I'll mark this as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1437042 for now. Thanks, James *** This bug has been marked as a duplicate of bug 1437042 ***