Bug 2168503
| Summary: | Cannot disable Red Hat web console on Satellite after it has been enabled | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jayant Bhatia <jbhatia> |
| Component: | Remote Execution | Assignee: | Ewoud Kohl van Wijngaarden <ekohlvan> |
| Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.13.0 | CC: | ahumbe, aruzicka, ekohlvan, mdolezel, rlavi, zhunting |
| Target Milestone: | 6.15.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-04-23 17:13:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jayant Bhatia
2023-02-09 08:55:14 UTC
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 Upstream bug assigned to ekohlvan Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36090 has been resolved. Checked on Satellite 6.15 snap 5, running installer with --no-enable-foreman-plugin-remote-execution-cockpit alone does not remove the web-console item from the host menu, the console is still accessible. Also the foreman-cockpit service remains running on satellite. Test machine available if needed talked to Ewoud offline, he confirmed the expected form is --foreman-plugin-remote-execution-cockpit-ensure=absent, moving back to on_qa for re-verification Checked again on Satellite 6.15 snap 5, using satellite-installer --foreman-plugin-remote-execution-cockpit-ensure=absent I was able to remove the console, service and package. Note that after this, to re-enable cockpit on satellite one needs to run satellite-installer --foreman-plugin-remote-execution-cockpit-ensure=present I've submitted https://github.com/theforeman/foreman-documentation/pull/2660 as a docs update. In a bit it should have rendered a preview. Would you mind checking those instructions? 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 (Important: Satellite 6.15.0 release), 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/RHSA-2024:2010 |