Broken with current Foreman 1.15.1 - Without Katello? #14
Comments
|
I have the same problem here, I'm using |
|
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. |
|
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 |
|
Update. |
Change default port ssl from 9090 to 9093 because is not compatible with cockpit theforeman/foreman_cockpit#14
Change default port ssl from 9090 to 9093 because is not compatible with cockpit theforeman/foreman_cockpit#14
|
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... 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? |
|
@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? |
|
@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? |
|
So I've made this work on my Katello 3.5/Foreman 1.16 system with the following steps: AS A WORKAROUND:
From there, start cockpit. The web interface will now be on "https://:9091"
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_cockpit-2.0.3/app/views/foreman_cockpit/hosts/_cockpit.html.erb
|
|
@Illydth ok you have right. I don't have experience with Ruby but this is the time to lear it :-) |
|
@Illydth Any idea how I can solve these? |
|
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. |
|
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? |
|
Hi Eric, I was referring to the posted messages in this thread, to where suggestions was to change the default port of Cockpit to something other than port 9090. I post, that I discourage this, as it's much easier to choose another port for Foreman/Katello Smart Proxy: ( ie: 9025 ). The Global picture, that other third party products discover / interface with cockpit running on port 9090, the default. That being said: Cockpit with Foreman 1.61.1 / Katello 3.5.1 is currently broken, and has been since the release. Installed: All latest packages: The current problem: Choosing a host where cockpit is installed, the button [Cockpit] is displayed. Choosing the box, drop-down of selections as per normal. Choosing any selection, produces no results.
Any action chosen, does not spawn any action. In /var/log/foreman/production.log ==> /var/log/foreman/production.log <== |
|
I am trying to understand why the default port needs to be changed to decide how to address this in Katello. To understand if this is simply a breakage accessing cockpit for the Foreman server itself or for all hosts being managed, And if the latter, why the issue exists, what errors users run into. |
|
Katello, out of the box --- foreman_proxy: Changing foreman-proxy port (9025), is much easier and does not cause an issue. Plugins, tfm-rubygem-foreman_openscap even adjusts the smart parameters for the foreman-proxy port, to 9025, SO: Foreman 13.x. - 15.x.x, Katello 3.2 - 3.4 --- Cockpit plugin has worked flawlessly, with minor code fixes. #12 Foreman 16.x, Katello 3.5 -- Cockpit plugin is completely broken, and as I have posted. Perhaps a fix for this soon please? |
|
Is there several issues currently impacting Cockpit and Foreman/Katello?
I have a new install of the latest Foreman, I'll see how it behaves right now with Cockpit. |
|
Just did a clean install of foreman with Katello and cockpit and can confirm that it is still broken, ill try changing the smart proxy port, but on a fresh install this still seems to be an issue. |
|
I'm seeing this on 1.17 without katello |
|
same here : Cockpit Version 172. No cockpit box on host page. |
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?
The text was updated successfully, but these errors were encountered: