5:58 p.m.
Hello everyone,
I'd like to get cockpit to work because currently when I click "Host
Console" on a host I just get "connection refused". I checked and after the
engine installation the cockpit service was not running. When I start it, it runs and
answers on port 9090, however the SSL certificate is broken.
- How do I auto enable cockpit on installation?
- How do I supply my own SSL certification to cockpit?
Kind regards
Skrzetuski
9:17 p.m.
OK, it seems that SSL cert has to be placed in /etc/cockpit/ws-certs.d/.
It seems you have to start the cockpit.socket. Why is it not started with the engine?
And is there Single Sign On for cockpit? I don't want to give users passwords on my
host.
And how do I connect cockpit to the engine? I can't configure it over the Web UI, I
get the error: "Please provide valid oVirt engine fully qualified domain name (FQDN)
and port (443 by default)", however I am providing correct values.
10:16 a.m.
I tried to file a bug in Redhat bugzilla several times now but it's broken and
it's frustrating as hell. Now I get the following error. Open source is such a
beautiful world.
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request POST /post_bug.cgi.
Reason: Error reading from remote server
Apache Server at bugzilla.redhat.com Port 443
10:26 a.m.
I managed to supply my own SSL certificate and start Cockpit but the ovirt-cockpit-sso
service is all messed up so you need to configure a Linux user with password to login. The
SSO service logs following errors.
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
I'd file a bug in bugzilla but as I stated before it's not working either.
5:10 a.m.
On Fri, Jan 10, 2020, 11:28 <m.skrzetuski(a)gmail.com> wrote:
I managed to supply my own SSL certificate and start Cockpit but the
ovirt-cockpit-sso service is all messed up so you need to configure a Linux
user with password to login. The SSO service logs following errors.
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
I'd file a bug in bugzilla but as I stated before it's not working either.
I don't see any issues with bugzilla.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MYXGROXZYHC...
9:05 a.m.
On Mon, Jan 13, 2020 at 12:36 AM <m.skrzetuski(a)gmail.com> wrote:
Well if *you* don't see any issues then we can finally sleep at
night.
You mentioned issues with bugzilla or did I understood wrong? You are not
able to open a bug? Went to bugzilla and it seems that the process to open
a bug functions properly. In case not, let us know more details what are
you facing so as to have a chance to get some assistance.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2OZAXV2KFOW...
10:18 a.m.
I was not able to open a bug I was getting several different errors from bugzilla. But of
course after a while it was working again. Someone restarted the web server. Now
everything is OK but the experience of entering bugs in that tool is/was horrible.
12:17 p.m.
On Mon, Jan 13, 2020 at 11:23 AM <m.skrzetuski(a)gmail.com> wrote:
I was not able to open a bug I was getting several different errors
from
bugzilla. But of course after a while it was working again. Someone
restarted the web server. Now everything is OK but the experience of
entering bugs in that tool is/was horrible.
Glad that you managed to open the bug. I agree that the experience is
somehow outdated.
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/65RBRITLI4I...
1570
days inactive
1574
days old
8 comments
2 participants
participants (2)
-
Alex K -
m.skrzetuski＠gmail.com