manageiq: ActionController::RoutingError

I’m seeing this error in the development.log. I fetched the latest from master, and confirmed that I have a config/cable.yml file. I then ran bin/setup and then bundle exec rake evm:start. Then, running on localhost, I just navigated pretty much anywhere within the UI and this error appears.

[----] D, [2017-03-15T11:38:34.642464 #43054:3ff61dd4a528] DEBUG -- :   MiqSearch Inst Including Associations (0.0ms - 0rows)
[----] I, [2017-03-15T11:38:34.643048 #43054:3ff61dd4a528]  INFO -- :   Rendered /Users/dberger/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/bundler/gems/manageiq-ui-classic-5737bd7a2aff/app/views/layouts/_adv_search_footer.html.haml (11.4ms)
[----] I, [2017-03-15T11:38:34.643153 #43054:3ff61dd4a528]  INFO -- :   Rendered /Users/dberger/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/bundler/gems/manageiq-ui-classic-5737bd7a2aff/app/views/layouts/_adv_search.html.haml (1110.0ms)
[----] I, [2017-03-15T11:38:34.712197 #43054:3ff61dd4a528]  INFO -- :   Rendered /Users/dberger/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/bundler/gems/manageiq-ui-classic-5737bd7a2aff/app/views/layouts/_footer.html.haml (1183.9ms)
[----] I, [2017-03-15T11:38:34.719255 #43054:3ff61dd4a528]  INFO -- : Completed 200 OK in 26955ms (Views: 26481.7ms | ActiveRecord: 266.2ms)


[----] D, [2017-03-15T11:38:34.722631 #43054:3ff61dd4a528] DEBUG -- : PostgreSQLAdapter#log_after_checkin, connection_pool: size: 8, connections: 3, in use: 2, waiting_in_queue: 0
[----] D, [2017-03-15T11:38:34.947431 #43030:3ff61ac3fa14] DEBUG -- :    (0.2ms)  SELECT pg_backend_pid()
[----] D, [2017-03-15T11:38:35.061784 #43033:3ff61ac3fa14] DEBUG -- :    (0.3ms)  SELECT pg_backend_pid()
[----] I, [2017-03-15T11:38:35.183927 #43054:3ff61dd4a370]  INFO -- : Started GET "/ws/notifications" for 127.0.0.1 at 2017-03-15 11:38:35 -0600
[----] F, [2017-03-15T11:38:35.219543 #43054:3ff61dd4a370] FATAL -- :   
[----] F, [2017-03-15T11:38:35.219704 #43054:3ff61dd4a370] FATAL -- : ActionController::RoutingError (No route matches [GET] "/ws/notifications"):
[----] F, [2017-03-15T11:38:35.219793 #43054:3ff61dd4a370] FATAL -- :   
[----] F, [2017-03-15T11:38:35.219907 #43054:3ff61dd4a370] FATAL -- : actionpack (5.0.2) lib/action_dispatch/middleware/debug_exceptions.rb:53:in `call'
actionpack (5.0.2) lib/action_dispatch/middleware/show_exceptions.rb:31:in `call'
railties (5.0.2) lib/rails/rack/logger.rb:36:in `call_app'
railties (5.0.2) lib/rails/rack/logger.rb:26:in `call'
sprockets-rails (3.2.0) lib/sprockets/rails/quiet_assets.rb:13:in `call'
actionpack (5.0.2) lib/action_dispatch/middleware/request_id.rb:24:in `call'
rack (2.0.1) lib/rack/method_override.rb:22:in `call'
rack (2.0.1) lib/rack/runtime.rb:22:in `call'
activesupport (5.0.2) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call'
actionpack (5.0.2) lib/action_dispatch/middleware/executor.rb:12:in `call'
actionpack (5.0.2) lib/action_dispatch/middleware/static.rb:136:in `call'
rack (2.0.1) lib/rack/sendfile.rb:111:in `call'
railties (5.0.2) lib/rails/engine.rb:522:in `call'
puma (3.3.0) lib/puma/configuration.rb:224:in `call'
puma (3.3.0) lib/puma/server.rb:561:in `handle_request'
puma (3.3.0) lib/puma/server.rb:406:in `process_client'
puma (3.3.0) lib/puma/server.rb:271:in `block in run'
puma (3.3.0) lib/puma/thread_pool.rb:111:in `block in spawn_thread'

This does not appear to prevent the app from functioning, but is a bit concerning.