Broken with current Foreman 1.15.1 - Without Katello?

[LaurentDumont]

Hey guys,

Running 1.15.1 and Cockpit-plugin 2.0.3 with Cockpit142-0 on a remote Debian host. If I browse directly to host_ip:9090, I get the Cockpit interface and everything works fine. But in the host page in Foreman, there is no Cockpit icon or graphs.

There is nothing relevant in the production.log. The host page does have a bit of HTML/JS that references Cockpit.

<script src="/assets/hosts-2cc1218e5cacff90b5d5b1eacbf11809020dbca6bf6f0024358ec7096b99cf00.js" data-turbolinks-track="true"></script><script src="/assets/foreman_cockpit/load_partial-6e55161e03a2c7f54effe6d906a227b878d6a8367fc9755ba68f7dbf41715c40.js" data-turbolinks-track="true"></script>

Where could I look to debug this further?

[meisterchecho]

I have the same problem here, I'm using foreman 1.15.3 and cockpit is tfm-rubygem-foreman_cockpit-2.0.3-1-fm1_15.el7.noarch. My system is Centos 7.4.1708

[Illydth]

Sure, I'll add a "me too" here just to get some visibility to the issue. It appears as if the plugin does not work with a katello installation of Foreman, and a foreman installation without katello cannot be changed into a Katello installation either, so it appears this is no-dice all around at this point.

[peppos]

Same problem with foreman-1.15.6-1 and cockpit tfm-rubygem-foreman_cockpit-2.0.3-1.fm1_15 on Centos 7.4.1708

[peppos]

Update.
Cockpit is not conpatible with Katello because use the same port TCP 9090.
Is possible to change the foreman proxy port:
foreman-installer --scenario=katello --foreman-proxy-ssl-port 9093
For me works fine.

[Illydth]

So I apologize for bringing this back up, but Instead of changing the foreman-proxy-ssl-port (from 9090) given that I ALREADY have Proxies installed and running, it'd be nice to simply change the port that the Foreman-Cockpit plugin is looking for to match whatever we set Cockpit to run on.

Re-configuring cockpit to run on a different port is as easy as setting a drop-in file into Systemd...

mkdir /etc/systemd/system/cockpit.socket.d/
vi /etc/systemd/system/cockpit.socket.d/listen.conf
[Socket]
ListenStream=
ListenStream=9091

The problem, of course, is that the foreman-proxy is looking for a specific port (9090 by default). Where do we go to change where foreman-proxy is looking for the cockpit port?

[peppos]

@Illydth I have tried to change cockpit port but in the plugin code is used always the 9090 port. If not possible to change Foreman-proxy port, is possible to use a parameter in the puglin for specify the cockpit port?

[Illydth]

@peppos Yea, that's what I was wondering. I know you're getting pushback from the devs on making changes to Foreman / Katello itself so why not look at whoever's maintaining this plugin and simply get a parameter on installation/execution of the plugin for what port the plugin looks for? That would seem to be the 'right' thing anyway...instead of hard coding a specific port in Foreman for attachment to Cockpit, or trying to get Cockpit to change to use an allowable port...why not just make the plugin itself configurable?

[Illydth]

So I've made this work on my Katello 3.5/Foreman 1.16 system with the following steps:

AS A WORKAROUND:

• Change Cockpit to work on an address that is NOT controlled by Katello/Foreman: (I'm currently using 9091).
  mkdir /etc/systemd/system/cockpit.socket.d/
vi /etc/systemd/system/cockpit.socket.d/listen.conf

[Socket]
ListenStream=
ListenStream=9091

systemctl daemon-reload
systemctl restart cockpit.socket

From there, start cockpit. The web interface will now be on "https://:9091"

• MODIFY Foreman Plugin: There are 3 files that contain the port address within the cockpit plugin that should be modified for consistency.

• On my Katello 3.5 installation the live foreman plugin installs to:
  /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_cockpit-2.0.3

• Modify the following files, replacing "9090" with whatever port you chose in the dropin file (Again 9091 is the example).

/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_cockpit-2.0.3/app/views/foreman_cockpit/hosts/_cockpit.html.erb
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_cockpit-2.0.3/app/models/concerns/foreman_cockpit/host_extensions.rb
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_cockpit-2.0.3/app/controllers/concerns/foreman_cockpit/hosts_controller_extensions.rb

• Reboot your Katello Installation to pick up the new code for the Foreman Plugin and you should have foreman contacting Cockpit on the port you've selected.

[peppos]

@Illydth ok you have right. I don't have experience with Ruby but this is the time to lear it :-)
In your opinion is possible to use a fact per customiza the cockpitk port?

[hscheffers]

@Illydth
I have done the same thing as you (using port 9093 instead of 9091) but I am getting errors in the foreman log (and cockpit not working...):

2018-02-08 15:11:23 56c08d30 [app] [W] Action failed
 | Foreman::Exception: ERF42-5531 [Foreman::Exception]: unknown permission for hosts#system
 | /usr/share/foreman/app/controllers/application_controller.rb:150:in `action_permission'
 | /usr/share/foreman/app/controllers/concerns/foreman/controller/action_permission_dsl.rb:19:in `action_permission'

Any idea how I can solve these?

[kolproductions]

Personal preference, but I would no way shape or form; change a port number from a distributed product, ie: Cockpit. Sub products which recognize cockpit, and typical 9090 is built-in. Smart Proxy port is easier to change, ie ( 9025 ) and won't break something like ManageIQ. Up to you of course, but 1 product ( Katello - Smart Proxy ) .vs. Every single machine where Cockpit is installed, and modification of additional products integrations.

[ehelms]

Can you give me some clarity here that I am missing to consider this further:

a) Does this issue only affect the host Foreman + Katello itself is running on?
b) If not, how does the running smart proxy affect the plugin reaching out to each host? I assumed it reached out to each by their hostname which would bypass hitting the Foreman host itself?