Description of problem:

As per documentation, to enable remote Cockpit feature, I should run

satellite-installer --enable-foreman-plugin-remote-execution-cockpit --reset-foreman-plugin-remote-execution-cockpit-ensure 

It doesn't mention I need to restart.

When I only do this without restart, then enable Cockpit on a host, then try to access host's Cockpit, I get page

The page you were looking for doesn't exist. 

and in foreman-tail:

2f08bcd5 | ActionController::RoutingError (No route matches [GET] "/webcon/=<FQDN>"):
 2f08bcd5 |   
 2f08bcd5 | lib/foreman/middleware/logging_context_request.rb:11:in `call'
 2f08bcd5 | katello (4.15.0.pre.master) lib/katello/prevent_json_parsing.rb:12:in `call' 

When I restart the services, it works as expected.

How reproducible:

Deterministic

Is this issue a regression from an earlier version:

No

Steps to Reproduce:

1. On Satellite, run

satellite-installer --enable-foreman-plugin-remote-execution-cockpit --reset-foreman-plugin-remote-execution-cockpit-ensure  

2. In WebUI -> Hosts -> <host> -> Schedule a job dropdown -> Enable web console, wait for the ReX job to finish

3. In the kebab menu, click Web console

Actual behavior:

The page you were looking for doesn't exist.  

Expected behavior:I should land on remote Cockpit page. So either documentation should tell me to restart the services, or, preferably, the installer should handle it.