Manageiq-ui-classic: Error with missing image when accessing Datastores page

[hstastna]

Steps to reproduce:

1. Go to _Compute > Infra > Datastores_
   and if you have there some CINDER Datastore Type, you will see this:

I, [2018-04-10T12:42:12.210869 #16854]  INFO -- : Started GET "/images/100/storagetype-cinder.png" for ::1 at 2018-04-10 12:42:12 +0200
F, [2018-04-10T12:42:12.339058 #16854] FATAL -- :   
F, [2018-04-10T12:42:12.339337 #16854] FATAL -- : ActionController::RoutingError (No route matches [GET] "/images/100/storagetype-cinder.png"):
F, [2018-04-10T12:42:12.341379 #16854] FATAL -- :   
F, [2018-04-10T12:42:12.341915 #16854] FATAL -- : actionpack (5.0.7) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
actionpack (5.0.7) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties (5.0.7) lib/rails/rack/logger.rb:36:in `call_app'
railties (5.0.7) lib/rails/rack/logger.rb:26:in `call'
sprockets-rails (3.2.1) lib/sprockets/rails/quiet_assets.rb:13:in `call'
actionpack (5.0.7) lib/action_dispatch/middleware/request_id.rb:24:in `call'
rack (2.0.4) lib/rack/method_override.rb:22:in `call'
rack (2.0.4) lib/rack/runtime.rb:22:in `call'
activesupport (5.0.7) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
actionpack (5.0.7) lib/action_dispatch/middleware/executor.rb:12:in `call'
actionpack (5.0.7) lib/action_dispatch/middleware/static.rb:136:in `call'
rack (2.0.4) lib/rack/sendfile.rb:111:in `call'
railties (5.0.7) lib/rails/engine.rb:522:in `call'
puma (3.7.1) lib/puma/configuration.rb:232:in `call'
puma (3.7.1) lib/puma/server.rb:578:in `handle_request'
puma (3.7.1) lib/puma/server.rb:415:in `process_client'
puma (3.7.1) lib/puma/server.rb:275:in `block in run'
puma (3.7.1) lib/puma/thread_pool.rb:120:in `block in spawn_thread'
I, [2018-04-10T12:42:12.541445 #16854]  INFO -- : NotificationChannel is transmitting the subscription confirmation
I, [2018-04-10T12:42:12.541769 #16854]  INFO -- : NotificationChannel is streaming from notifications_10000000000001

Question:
Don't we support CINDER Datastore Types anymore or are we missing the image?

---

UPDATE:
We don't support cinder (or swift) anymore at all.

TODO:

• migration
• removing appropriate controllers

[himdel]

@hstastna We don't support cinder (or swift) anymore at all... so, this is perfectly OK, you can solve this by removing that datastore.

[hstastna]

Awesome! Thank you very much, Martin! :star2:

[lpichler]

@himdel and are we removing them in some migration ? If not shouldn't we ?

[himdel]

Agreed, we should .. as far as I'm aware, only the UI bits have been removed so far.

(Well, most of them, we had to revert a bit, so @ZitaNemeckova has a TODO to remove the ems_cinder and ems_swift controllers, but apart from that, it's gone from the UI, and only the UI.)

[hstastna]

@himdel Should I reopen this issue or do we have another issues/pivotal tracker/whatever to finish this all and not to forget it or so? :angel:

[ZitaNemeckova]

@hstastna please reopen and I'll take it to remember better :)

[himdel]

@hstastna You'll have to reopen on the core repo, and assign to somebody else :)

That sounds like it needs to much internal knowledge for UI people to do that :).