Description of problem: After deploying an Ansible Job Template, an object is created in "my services". The icon for that object is not shown correctly. Version-Release number of selected component (if applicable): 5.6.0.7-beta2.6.20160516171555_b1be31f How reproducible: always Steps to Reproduce: 1. create a service catalog item which executes an Ansible Tower Job Template 2. order the item 3. navigate to "my services" - the icon is not shown correctly. Additional info: see attached screenshot
Created attachment 1158648 [details] screenshot
HiHo, I don't know how to find the name of the missing icon. Did you see the screenshot I attached to this BZ? I also see the following errors in vmdb/production.log, maybe that helps to identify the issue: [----] I, [2016-05-20T12:33:34.014532 #3059:1104464] INFO -- : Started GET "/images/100/.png" for 217.231.105.126 at 2016-05-20 12:33:34 -0400 [----] F, [2016-05-20T12:33:34.021355 #3059:1104464] FATAL -- : [----] F, [2016-05-20T12:33:34.021497 #3059:1104464] FATAL -- : ActionController::RoutingError (No route matches [GET] "/images/100/.png"): [----] F, [2016-05-20T12:33:34.021564 #3059:1104464] FATAL -- : [----] F, [2016-05-20T12:33:34.021649 #3059:1104464] FATAL -- : /opt/rh/cfme-gemset/bundler/gems/rails-a44497f6c9ef/actionpack/lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call' [----] F, [2016-05-20T12:33:34.021733 #3059:1104464] FATAL -- : /opt/rh/cfme-gemset/bundler/gems/rails-a44497f6c9ef/actionpack/lib/action_dispatch/middleware/show_exceptions.rb:31:in `call' [----] F, [2016-05-20T12:33:34.021796 #3059:1104464] FATAL -- : railties (5.0.0.rc1) lib/rails/rack/logger.rb:36:in `call_app' [----] F, [2016-05-20T12:33:34.021892 #3059:1104464] FATAL -- : railties (5.0.0.rc1) lib/rails/rack/logger.rb:26:in `call' [----] F, [2016-05-20T12:33:34.022011 #3059:1104464] FATAL -- : request_store (1.3.1) lib/request_store/middleware.rb:9:in `call' [----] F, [2016-05-20T12:33:34.022072 #3059:1104464] FATAL -- : /opt/rh/cfme-gemset/bundler/gems/rails-a44497f6c9ef/actionpack/lib/action_dispatch/middleware/request_id.rb:24:in `call' [----] F, [2016-05-20T12:33:34.022128 #3059:1104464] FATAL -- : rack (2.0.0.rc1) lib/rack/method_override.rb:22:in `call' [----] F, [2016-05-20T12:33:34.022251 #3059:1104464] FATAL -- : rack (2.0.0.rc1) lib/rack/runtime.rb:22:in `call' [----] F, [2016-05-20T12:33:34.022309 #3059:1104464] FATAL -- : /opt/rh/cfme-gemset/bundler/gems/rails-a44497f6c9ef/activesupport/lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call' [----] F, [2016-05-20T12:33:34.022373 #3059:1104464] FATAL -- : /opt/rh/cfme-gemset/bundler/gems/rails-a44497f6c9ef/actionpack/lib/action_dispatch/middleware/executor.rb:12:in `call' [----] F, [2016-05-20T12:33:34.022450 #3059:1104464] FATAL -- : rack (2.0.0.rc1) lib/rack/sendfile.rb:111:in `call' [----] F, [2016-05-20T12:33:34.022506 #3059:1104464] FATAL -- : railties (5.0.0.rc1) lib/rails/engine.rb:522:in `call' [----] F, [2016-05-20T12:33:34.022561 #3059:1104464] FATAL -- : puma (3.3.0) lib/puma/configuration.rb:224:in `call' [----] F, [2016-05-20T12:33:34.022616 #3059:1104464] FATAL -- : puma (3.3.0) lib/puma/server.rb:561:in `handle_request' [----] F, [2016-05-20T12:33:34.022671 #3059:1104464] FATAL -- : puma (3.3.0) lib/puma/server.rb:406:in `process_client' [----] F, [2016-05-20T12:33:34.022760 #3059:1104464] FATAL -- : puma (3.3.0) lib/puma/server.rb:271:in `block in run' [----] F, [2016-05-20T12:33:34.022819 #3059:1104464] FATAL -- : puma (3.3.0) lib/puma/thread_pool.rb:111:in `call' [----] F, [2016-05-20T12:33:34.022903 #3059:1104464] FATAL -- : puma (3.3.0) lib/puma/thread_pool.rb:111:in `block in spawn_thread' [----] F, [2016-05-20T12:33:34.022960 #3059:1104464] FATAL -- : logging (1.8.2) lib/logging/diagnostic_context.rb:323:in `call' [----] F, [2016-05-20T12:33:34.023016 #3059:1104464] FATAL -- : logging (1.8.2) lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context Please let me know, if you still need more information. Regards, Christian
https://github.com/ManageIQ/manageiq/pull/9063
*** Bug 1341873 has been marked as a duplicate of this bug. ***
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/4a9dc88288a7825230373a660ab13701d46dd0f6 commit 4a9dc88288a7825230373a660ab13701d46dd0f6 Author: Laura Galis <lgalis> AuthorDate: Tue May 31 15:51:05 2016 -0400 Commit: Laura Galis <lgalis> CommitDate: Thu Jun 2 09:44:10 2016 -0400 The Ansible service does not display an icon https://bugzilla.redhat.com/show_bug.cgi?id=1337070 app/assets/images/100/ansible_tower.png | Bin 0 -> 3246 bytes app/helpers/quadicon_helper.rb | 2 +- .../layouts/quadicon/_service_ansible_tower.html.haml | 16 ++++++++++++++++ 3 files changed, 17 insertions(+), 1 deletion(-) create mode 100644 app/assets/images/100/ansible_tower.png create mode 100644 app/views/layouts/quadicon/_service_ansible_tower.html.haml
Hi Pavol, Just like other types of services, the Ansible Tower ones will use the default service icon that can be seen in your attachement. This user has the option to upload a custom image - see the screenshots here without and with a custom image uploaded: https://github.com/ManageIQ/manageiq/pull/9063 Thanks, Laura
https://github.com/ManageIQ/manageiq/pull/9133
https://github.com/ManageIQ/manageiq/pull/7620
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348