<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Dec 23, 2017 at 11:18 AM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><span class="gmail-"><div class="gmail_extra"><div class="gmail_quote">On Fri, Dec 22, 2017 at 10:22 PM, Sandro Bonazzola <span dir="ltr"><<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><span class="gmail-m_-2249562557521163007gmail-"><div><br><div class="gmail_extra"><br><div class="gmail_quote">Il 22 Dic 2017 10:12 PM, "Yaniv Kaul" <<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>> ha scritto:<br type="attribution"><blockquote class="gmail-m_-2249562557521163007gmail-m_-7204618760161936258quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div class="gmail-m_-2249562557521163007gmail-m_-7204618760161936258elided-text"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Dec 22, 2017 7:33 PM, "Gianluca Cecchi" <<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail-m_-2249562557521163007gmail-m_-7204618760161936258m_6654239614441438449quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">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...<div dir="auto">Is this an error or in 4.2 the access to host console is for plain OS nodes too?</div><div dir="auto">In that case is there any service I have to enable on host?</div><div dir="auto">It seems indeed my host is not currently listening on 9090 Port....</div></div></blockquote></div></div></div><div dir="auto"><br></div></div><div dir="auto">Cockpit + firewall settings to enable to get to it. </div></div></blockquote></div></div></div><div dir="auto"><br></div></span><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">Didi, can you help here? Gianluca, can you share host upgrade logs?</div><span class="gmail-m_-2249562557521163007gmail-"><div dir="auto"><br></div><div dir="auto"><br></div></span></div>
</blockquote></div></div><div class="gmail_extra"><br></div></span><div class="gmail_extra">Hello,</div><div class="gmail_extra">this is a plain CentOS, not ovirt-node-ng one, that was upgraded from 4.1.7 to 4.2<br></div><div class="gmail_extra">So the upgrade path has been to put the host into maintenance, yum update, reboot.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Indeed cockpit has been installed as part of the yum update part:</div><div class="gmail_extra"><br></div><div class="gmail_extra">Dec 22 10:40:07 Installed: cockpit-bridge-155-1.el7.<wbr>centos.x86_64<br>Dec 22 10:40:07 Installed: cockpit-system-155-1.el7.<wbr>centos.noarch<br>Dec 22 10:40:40 Installed: cockpit-networkmanager-155-1.<wbr>el7.centos.noarch<br>Dec 22 10:40:42 Installed: cockpit-ws-155-1.el7.centos.<wbr>x86_64<br>Dec 22 10:40:43 Installed: cockpit-155-1.el7.centos.x86_<wbr>64<br>Dec 22 10:40:52 Installed: cockpit-storaged-155-1.el7.<wbr>centos.noarch<br>Dec 22 10:40:57 Installed: cockpit-dashboard-155-1.el7.<wbr>centos.x86_64<br>Dec 22 10:41:35 Installed: cockpit-ovirt-dashboard-0.11.<wbr>3-0.1.el7.centos.noarch<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">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</div><div class="gmail_extra"><br></div><div class="gmail_extra">But if I run <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">[root@ovirt01 ~]# remotectl certificate<br>remotectl: No certificate found in dir: /etc/cockpit/ws-certs.d<br>[root@ovirt01 ~]# <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">So it seems that the cockpit.service ExecStartPre has not been ever run... <br></div><div class="gmail_extra">ExecStartPre=/usr/sbin/<wbr>remotectl certificate --ensure --user=root --group=cockpit-ws --selinux-type=etc_t</div><div class="gmail_extra"><br></div><div class="gmail_extra">[root@ovirt01 ~]# systemctl status cockpit.service<br>● cockpit.service - Cockpit Web Service<br> Loaded: loaded (/usr/lib/systemd/system/<wbr>cockpit.service; static; vendor preset: disabled)<br> Active: inactive (dead)<br> Docs: man:cockpit-ws(8)<br>[root@ovirt01 ~]# <br><span class="gmail-HOEnZb"><font color="#888888"><br></font></span></div><span class="gmail-HOEnZb"><font color="#888888"><div class="gmail_extra">Gianluca<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></font></span></div>
</blockquote></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">At the end I compared my CentOS 7.4 oVirt 4.2 configuration with the configuration of a RHEV 4.1 RHV-H environment and there I see this kind of config</div><div class="gmail_extra"><br></div><div class="gmail_extra">[root@rhevora1 ~]# systemctl status cockpit.socket<br>● cockpit.socket - Cockpit Web Service Socket<br> Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; enabled; vendor preset: enabled)<br> Active: active (listening) since Fri 2017-10-27 17:02:30 CEST; 1 months 29 days ago<br> Docs: man:cockpit-ws(8)<br> Listen: [::]:9090 (Stream)<br><br>Oct 27 17:02:30 rhevora1.mydomain systemd[1]: Listening on Cockpit Web Service Socket.<br>Oct 27 17:02:30 rhevora1.mydomain systemd[1]: Starting Cockpit Web Service Socket.<br>[root@rhevora1 ~]# <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">So there is basically the difference that on RHEV RHV-H the cockpit.socket systemd unit is enabled by default (cockpit-ws-148-1.el7.x86_64), while on this just updated to 4.2 oVirt host on plain CentOS we have</div><div class="gmail_extra"><br></div><div class="gmail_extra">[root@ovirt01 etc]# systemctl status cockpit.socket<br>● cockpit.socket - Cockpit Web Service Socket<br> Loaded: loaded (/usr/lib/systemd/system/cockpit.socket; disabled; vendor preset: disabled)<br> Active: inactive (dead)<br> Docs: man:cockpit-ws(8)<br> Listen: <a href="http://0.0.0.0:9090">0.0.0.0:9090</a> (Stream)<br>[root@ovirt01 etc]# <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">On oVirt 4.2 the version is currently cockpit-ws-155-1.el7.centos.x86_64</div><div class="gmail_extra"><br></div><div class="gmail_extra">What I've done has been</div><div class="gmail_extra">systemctl enable cockpit.socket</div><div class="gmail_extra">systemctl start cockpit.socket</div><div class="gmail_extra"><br></div><div class="gmail_extra">and now I have the ovirt01 host correctly listening on 9090 port and I'm able to web connect and enjoy...</div><div class="gmail_extra"><br></div><div class="gmail_extra">Let me know if this is a sort of regression of cockpit-ws package or what...</div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca<br></div></div>