Description of problem: Red Hat web console on Satellite is disabled by default. Running "# satellite-installer --enable-foreman-plugin-remote-execution-cockpit" enables the web console. Once it is enabled, it cannot be disabled again and running "# satellite-installer --no-enable-foreman-plugin-remote-execution-cockpit" does not help. Version-Release number of selected component (if applicable):satellite-6.13.0-4.el8sat.noarch How reproducible: Always Steps to Reproduce: 1. Run following command on Satellite "# satellite-installer --enable-foreman-plugin-remote-execution-cockpit" and allow it execute successfully. 2. Navigate to Satellite WebUI -> Hosts -> All Hosts -> click on listed host -> Web Console button is visible/enabled. 3. Run "# satellite-installer --no-enable-foreman-plugin-remote-execution-cockpit" command. Allow it to complete. Actual results: The Web Console button is still listed on All Hosts page on Satellite WebUI and has not been disabled. Expected results: The Web Console button should get disabled after using "--no-enable-foreman-plugin-remote-execution-cockpit" parameter with satellite-installer. Additional info: 7.1. Enabling Red Hat web console on Satellite in https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_hosts/index?lb_target=preview
Well, yes, in general no plugin can really be disabled. The installer either manages things or leaves them alone, so enabling plugin and then changing your mind leaves things around. I don't see this changing in the foreseeable future. However, in this particular case, you should be able to 1) run satellite-installer --no-enable-foreman-plugin-remote-execution-cockpit to tell the installer to stop managing cockpit related things 2) Go into Administer > Settings > Remote Execution and set the "Cockpit URL" to be blank. This should make the web console button disappear 3) On your satellite, uninstall rubygem-foreman_remote_execution-cockpit package Also note, starting with 6.13 iirc, cockpit integration can be independently enabled/disabled on capsules, including the internal one. If you want to be extra safe, in addition to the three steps above you can also run the installer with --foreman-proxy-plugin-remote-execution-script-cockpit-integration=false With that being said, a "proper fix" is most likely not going to happen, but we can at least document it. Either in Satellite docs or just as a KCS
Upstream bug assigned to ekohlvan