Bug 1789733 - Host console SSO not working at all!
Summary: Host console SSO not working at all!
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.3.7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.4.0
: ---
Assignee: Liran Rotenberg
QA Contact: Beni Pelled
URL:
Whiteboard:
Depends On: 1826248
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-10 09:53 UTC by Maciej Skrzetuski
Modified: 2020-05-20 20:02 UTC (History)
4 users (show)

Fixed In Version: ovirt-cockpit-sso-0.1.3
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-20 20:02:17 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)
sosreport as requested (on clean ovirt install) (5.30 MB, application/gzip)
2020-01-10 17:51 UTC, Maciej Skrzetuski
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-cockpit-sso pull 21 0 None closed fix float cockpit version comparison 2020-06-09 10:22:37 UTC

Description Maciej Skrzetuski 2020-01-10 09:53:31 UTC
On a fresh oVirt installation the "Host Console" is not working. When cockpit service is started manually then the SSO service throws errors. 

I am trying to enter this bug for the 5th time now. Bugzilla is throwing errors so bare with me for this short description.

Jan 09 23:21:09 localhost.localdomain systemd[1]: Starting oVirt-Cockpit SSO service...
Jan 09 23:21:09 localhost.localdomain prestart.sh[2669]: /bin/ln: failed to create
symbolic link ‘/usr/share/ovirt-cockpit-sso/config/cockpit/ws-certs.d/ws-certs.d’: File
exists
Jan 09 23:21:09 localhost.localdomain systemd[1]: Started oVirt-Cockpit SSO service.
Jan 09 23:21:09 localhost.localdomain start.sh[2676]: (standard_in) 1: syntax error
Jan 09 23:21:09 localhost.localdomain start.sh[2676]: Installed cockpit version:
Jan 09 23:21:09 localhost.localdomain start.sh[2676]:
/usr/share/ovirt-cockpit-sso/start.sh: line 9: [: : integer expression expected
Jan 09 23:21:09 localhost.localdomain start.sh[2676]: Installed Cockpit version is old, at
least 140 is required for ovirt-cockpit SSO

Comment 1 Maciej Skrzetuski 2020-01-10 10:04:57 UTC
The start.sh script of the SSO service has errors.

usr/share/ovirt-cockpit-sso/start.sh
++ rpm -q --queryformat '%{VERSION}' cockpit-ws
+ COCKPIT_VERSION=195.1
+ echo Installed cockpit version: 195.1
Installed cockpit version: 195.1
+ '[' 195.1 -ge 140 ']'
/usr/share/ovirt-cockpit-sso/start.sh: line 10: [: 195.1: integer expression expected
+ logger Installed cockpit-ws version is 195.1 but at least 140 is required. Cockpit-ovirt-sso will be effectively disabled.
+ echo Installed Cockpit version 195.1 is old, at least 140 is required for ovirt-cockpit SSO
Installed Cockpit version 195.1 is old, at least 140 is required for ovirt-cockpit SSO
+ tail -f /dev/null

Even when fixed the single sign on is not working for me with "Authentication failed: internal-error: Error validating auth token" error in the web ui.

Comment 2 RHEL Program Management 2020-01-10 11:03:14 UTC
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.

Comment 3 Sandro Bonazzola 2020-01-10 11:04:25 UTC
Can you please attach sos report from the host running the engine?

Comment 4 Maciej Skrzetuski 2020-01-10 12:26:25 UTC
This is on a private machine at home. Can I upload sos report privately somehow? I don't want to expose my hostnames. And can you provide sos reports for CentOS?

Comment 5 Sandro Bonazzola 2020-01-10 13:37:52 UTC
sos is already included in CentOS. You can cleanup the reports using tools like https://github.com/soscleaner/soscleaner

Comment 6 Maciej Skrzetuski 2020-01-10 17:51:35 UTC
Created attachment 1651345 [details]
sosreport as requested (on clean ovirt install)

This is on a clean 4.3.7 install. Host console opens but login is requested so SSO is not working.

Comment 7 Maciej Skrzetuski 2020-01-10 18:08:48 UTC
I just notice when I go to https://myhost.com:9090/machines then there is no connection to oVirt. When I enter myhost.com as FQDN and 443 as port then I get the error "Please provide valid oVirt engine fully qualified domain name (FQDN) and port (443 by default)".

Comment 8 Ryan Barry 2020-03-24 12:07:20 UTC
Beni, reproducible?

Comment 9 Beni Pelled 2020-03-24 12:46:41 UTC
Yes,

Verified on:
- RHV 4.3.9.4-11.el7
- Red Hat Enterprise Linux Server 7.8 (Maipo)
- ovirt-cockpit-sso-0.1.1-1.el7.noarch (not sure is the right )

The ovirt-cockpit-sso wasn't installed so I installed http://people.redhat.com/mlibra/repos/ovirt-cockpit-sso/epel-7-x86_64/ovirt-cockpit-sso-0.1.1-1.el7.noarch.rpm,
And the ovirt-cockpit-sso service doesn't start due to an issue with the COCKPIT_VERSION (float number):

    [root@ocelot05 ~]# bash /usr/share/ovirt-cockpit-sso/start.sh
    Installed cockpit version: 195.6
    /usr/share/ovirt-cockpit-sso/start.sh: line 8: [: 195.6: integer expression expected
    Installed Cockpit version 195.6 is old, at least 140 is required for ovirt-cockpit SSO

After I manually fixed the problem, I see two missing directory (and certificates) issues: 
    [root@ocelot05 ~]# bash /usr/share/ovirt-cockpit-sso/start.sh
    Installed cockpit version: 195
    Cockpit version check passed
    /usr/share/ovirt-cockpit-sso/start.sh: line 11: /var/run/ovirt-cockpit-sso/ovirt-cockpit-sso.pid: No such file or directory
    cockpit-ws: Error loading certificates from /usr/share/ovirt-cockpit-sso/config/cockpit/ws-certs.d: Error opening directory ?/usr/share/ovirt-cockpit-sso/config/cockpit/ws-certs.d?: No such file or directory

Comment 11 Beni Pelled 2020-03-24 13:37:56 UTC
Same issues with ovirt-cockpit-sso-0.1.2-1.el7.noarch

Comment 13 Beni Pelled 2020-05-13 12:40:44 UTC
Verified with:
- ovirt-engine-4.4.0-0.37.master.el8ev.noarch
- ovirt-cockpit-sso-0.1.4-1.el8ev.noarch
- libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64
- vdsm-4.40.14-1.el8ev.x86_64


Verification steps:
1. Make sure 'ovirt-cockpit-sso.service' is running on the engine
2. Go to the Hosts window, select one of the hosts and select 'Host Console'

Result:
- A new windows opens for the cockpit service - authenticated by SSO


PS> The cockpit service page presents 'Not Found' but it has nothing with this bug.

Comment 14 Sandro Bonazzola 2020-05-20 20:02:17 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.