[ovirt-users] Ovirt 4.2 and host console

Gianluca Cecchi gianluca.cecchi at gmail.com
Sat Dec 23 10:18:22 UTC 2017


On Fri, Dec 22, 2017 at 10:22 PM, Sandro Bonazzola <sbonazzo at redhat.com>
wrote:

>
>
> Il 22 Dic 2017 10:12 PM, "Yaniv Kaul" <ykaul at redhat.com> ha scritto:
>
>
>
> On Dec 22, 2017 7:33 PM, "Gianluca Cecchi" <gianluca.cecchi at gmail.com>
> wrote:
>
> Hello, after upgrading engine and then  plain CentOS 7.4 host from 4.1 to
> 4.2, I see in host section if I select line for the host, right click and
> host console... That tries to go to the typical 9090 cockpit Port of
> node-ng...
> Is this an error or in 4.2 the access to host console is for plain OS
> nodes too?
> In that case is there any service I have to enable on host?
> It seems indeed my host is not currently listening on 9090 Port....
>
>
> Cockpit + firewall settings to enable to get to it.
>
>
> Cockpit service should be up and running after the upgrade. Ovirt hist
> depliy takes care of it. Firewall is configured by the engine unless you
> disabled firewall config on the host configuration dialog.
>
> Didi, can you help here? Gianluca, can you share host upgrade logs?
>
>
>
Hello,
this is a plain CentOS, not ovirt-node-ng one, that was upgraded from 4.1.7
to 4.2
So the upgrade path has been to put the host into maintenance, yum update,
reboot.

Indeed cockpit has been installed as part of the yum update part:

Dec 22 10:40:07 Installed: cockpit-bridge-155-1.el7.centos.x86_64
Dec 22 10:40:07 Installed: cockpit-system-155-1.el7.centos.noarch
Dec 22 10:40:40 Installed: cockpit-networkmanager-155-1.el7.centos.noarch
Dec 22 10:40:42 Installed: cockpit-ws-155-1.el7.centos.x86_64
Dec 22 10:40:43 Installed: cockpit-155-1.el7.centos.x86_64
Dec 22 10:40:52 Installed: cockpit-storaged-155-1.el7.centos.noarch
Dec 22 10:40:57 Installed: cockpit-dashboard-155-1.el7.centos.x86_64
Dec 22 10:41:35 Installed:
cockpit-ovirt-dashboard-0.11.3-0.1.el7.centos.noarch

I also see that there is a systemd cockpit.service unit that is configured
as static and requires a cockpit.socket unit, that in turn is WantedBy
sockets.target

But if I run

[root at ovirt01 ~]# remotectl certificate
remotectl: No certificate found in dir: /etc/cockpit/ws-certs.d
[root at ovirt01 ~]#

So it seems that the cockpit.service ExecStartPre has not been ever run...
ExecStartPre=/usr/sbin/remotectl certificate --ensure --user=root
--group=cockpit-ws --selinux-type=etc_t

[root at ovirt01 ~]# systemctl status cockpit.service
● cockpit.service - Cockpit Web Service
   Loaded: loaded (/usr/lib/systemd/system/cockpit.service; static; vendor
preset: disabled)
   Active: inactive (dead)
     Docs: man:cockpit-ws(8)
[root at ovirt01 ~]#

Gianluca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20171223/1207a769/attachment.html>


More information about the Users mailing list