Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-15860

Document the steps for 'Disabling Red Hat web console on Satellite'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 6.13.0
    • Documentation
    • False
    • Moderate
    • Sat_docs_2_2023
    • None
    • None
    • None
    • None

      For Background, please refer following BugZilla: https://bugzilla.redhat.com/show_bug.cgi?id=2168503

      This Bug is being filed to include the steps for 'Disabling Red Hat web console on Satellite' in official Satellite 6.13 documentation.

      Document URL:

      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

      Section Number and Name:

      There should be a new section preferably within "Chapter 7. Host Management and Monitoring Using Red Hat Web Console" for disabling Red Hat web console on Satellite.

      Describe the issue:

      Below are the steps that should be included as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=2168503.
      ~~~
      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
      ~~~

              rhn-support-alazik Adam Lazik
              jira-bugzilla-migration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: