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: | ASSIGNED --- | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.13.0 | CC: | ahumbe, aruzicka, ekohlvan, mdolezel |
| Target Milestone: | Unspecified | 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: | 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 |