cockpit-devel July 2019

cockpit-devel@lists.fedorahosted.org

6 participants
7 discussions

Cockpit 199
by Katerina Koukiou 25 Jul '19

25 Jul '19

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 199: http://cockpit-project.org/blog/cockpit-199.html Summary: - Redesigned logs all over cockpit - Services: Design and accesibility improvements - System: Show DIMM information on Hardware Info page - Machines: VM creation dialog now shows the recommended memory for the selected OS Cockpit 199 is available for download here: - Fedora 30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d73df27df4 - Source: https://github.com/cockpit-project/cockpit/releases/tag/199 Regards, Katerina Koukiou

1 0

Tests names changed
by Matej Marusak 23 Jul '19

23 Jul '19

Hey all, Today we land [1] which changes tests names. This affects all opened pull requests as they need to be rebased and also you won't be able to re-run any tests with the same (old) name. Tests names now have form osimage[/scenario][@owner/project]. So for example: `verify/fedora-30` is now `fedora-30` (`verify` is default scenario for cockpit-project/cockpit) `avocado/fedora` is now `fedora-30/avocado` `selenium/firefox` is now `fedora-30/selenium-firefox` (there cannot be `/` in scenario) `cockpit/fedora-30@cockpit-project/cockpit-podman` is now `fedora-30@cockpit-project/cockpit-podman` (dropping the `cockpit` prefix) Hope it makes sense :) If not or you encounter any problem please ping me on IRC. MM [1] https://github.com/cockpit-project/cockpit/pull/12367

1 0

Problem with FF 68 and Cockpit plugins
by Mark Reynolds 22 Jul '19

22 Jul '19

So we just noticed that FireFox has problems loading our UI plugin on Fedora 30. Sometimes it works, sometimes it does not (typically it does not work even with reload). We don't see any problems with other browsers. There are no console log errors or warnings. It's just a blank screen. It also appears the plugins listed below ours also do not work (our plugin is "389 Directory Server" so it's always first in the list. Not sure it's related or not to the other plugins not working Is anyone else seeing problems with the latest version of FF? I'm not sure if this is something that has to be fixed in Cockpit, or our plugin, or FF. To see the problem please install the rpms from here, or visit: https://kvm-03-guest17.hv2.lab.eng.bos.redhat.com:9090/389-console root/redhat https://koji.fedoraproject.org/koji/taskinfo?taskID=36350813 <https://koji.fedoraproject.org/koji/taskinfo?taskID=36350813> Thanks, Mark -- 389 Directory Server Development Team

1 0

Cockpit 198, cockpit-composer 3, and cockpit-podman 5 released
by Martin Pitt 10 Jul '19

10 Jul '19

Cockpit is the modern Linux admin interface. We release regularly. Here are the release notes from version 198: http://cockpit-project.org/blog/cockpit-198.html Summary: - PatternFly4 user interface design - SELinux: Show changes - Machines: Deletion of Virtual Networks - Machines: Support more disk types - Docker: Change menu label - Web server: More flexible https redirection for proxies You can get Cockpit here: http://cockpit-project.org/running.html Cockpit 198 is available in Fedora 30: https://bodhi.fedoraproject.org/updates/cockpit-198-1.fc30 Or download the tarball here: https://github.com/cockpit-project/cockpit/releases/tag/198 cockpit-composer 3 was released today: - Use cockpit's PatternFly CSS, to pick up the new PatternFly 4 styling - Add additional blueprint name validation - Fix images not loading on refresh - Add notification for source repo deletion It is available in Fedora 30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-5fd6da4784 Or download the tarball here: https://github.com/weldr/cockpit-composer/releases/3 cockpit-podman 5 was released today: - Add container Terminal It is available in Fedora 30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-edb4d9b942 Or download the tarball here: https://github.com/cockpit-project/cockpit-podman/releases/5 Take care, Martin Pitt

1 0

Semaphore images update
by Allison Karlitskaya 09 Jul '19

09 Jul '19

[tl;dr: rebase all PRs on master, tell lis about any problems with semaphore.] hi all, I've updated the semaphore images today to a Ubuntu 19.04, as a test. You'll need to ensure that any pull requests that you submit are rebased on top of the commits from https://github.com/cockpit-project/cockpit/pull/12255 in order for your builds to succeed. These commits are on master since last night. I'll be trying to keep an eye on things over the course of the day, but if you see anything suspicious, please let me know. Thanks, and happy hacking! Allison

1 0

unable to login to fedora server cockpit-ws
by Albert Szostkiewicz 05 Jul '19

05 Jul '19

After running fedora update, I am unable to log-in into the cocpit-ws and I am not sure what went wrong. I am using FreeIPA, (installed on the same machine). I am able to ssh to the box using ipa credentials or freeIPA dashboard without issue. But cocpit gives me "wrong username or password" Errors I'm getting in journal 'couldn't read from connection: Peer sent fatal TLS alert: Unknown certificate' Maybe someone had similar issue or some ideas where to start debugging it ? Log snippet when I am trying to log in: myserver.domain.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=cockpit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' myserver.domain.com cockpit-ws[13295]: Using certificate: /etc/cockpit/ws-certs.d/0-self-signed.cert myserver.domain.com cockpit-ws[13295]: couldn't read from connection: Peer sent fatal TLS alert: Unknown certificate myserver.domain.com cockpit-session[13298]: pam_sss(cockpit:auth): authentication success; logname= uid=0 euid=0 tty= ruser= rhost=10.0.5.44 user=myuser myserver.domain.com audit[13298]: USER_AUTH pid=13298 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_succeed_if,pam_succeed_if,pam_sss acct="myuser" exe="/usr/libexec/cockpit-session" hostname=10.0.5.44 addr=10.0.5.44 terminal=? res=success' myserver.domain.com audit[13298]: USER_ACCT pid=13298 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_unix,pam_sss,pam_permit acct="myuser" exe="/usr/libexec/cockpit-session" hostname=10.0.5.44 addr=10.0.5.44 terminal=? res=success' myserver.domain.com audit[13298]: CRED_ACQ pid=13298 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_localuser,pam_sss acct="myuser" exe="/usr/libexec/cockpit-session" hostname=10.0.5.44 addr=10.0.5.44 terminal=? res=success' myserver.domain.com cockpit-session[13298]: pam_ssh_add: Identity added: /home/myuser/.ssh/id_rsa (myuser(a)myserver.domain.com) myserver.domain.com systemd-logind[1067]: New session 39 of user myuser. -- Subject: A new session 39 has been created for user myuser -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new session with the ID 39 has been created for the user myuser. -- -- The leading process of the session is 13298. myserver.domain.com systemd[1]: Started Session 39 of user myuser. -- Subject: Unit session-39.scope has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-39.scope has finished starting up. -- -- The start-up result is done. myserver.domain.com cockpit-session[13298]: pam_unix(cockpit:session): session opened for user myuser by (uid=0) myserver.domain.com audit[13298]: USER_START pid=13298 uid=0 auid=1907400001 ses=39 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_ssh_add,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_sss,pam_umask,pam_lastlog acct="myuser" exe="/usr/libexec/cockpit-sessi> myserver.domain.com audit[13298]: CRED_REFR pid=13298 uid=0 auid=1907400001 ses=39 msg='op=PAM:setcred grantors=pam_localuser,pam_sss acct="myuser" exe="/usr/libexec/cockpit-session" hostname=10.0.5.44 addr=10.0.5.44 terminal=? res=success' myserver.domain.com cockpit-ws[13295]: 3: Permission denied. myserver.domain.com audit[13298]: CRED_DISP pid=13298 uid=0 auid=1907400001 ses=39 msg='op=PAM:setcred grantors=pam_localuser,pam_sss acct="myuser" exe="/usr/libexec/cockpit-session" hostname=10.0.5.44 addr=10.0.5.44 terminal=? res=success' myserver.domain.com cockpit-session[13298]: pam_unix(cockpit:session): session closed for user myuser myserver.domain.com audit[13298]: USER_END pid=13298 uid=0 auid=1907400001 ses=39 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_keyinit,pam_ssh_add,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_sss,pam_umask,pam_lastlog acct="myuser" exe="/usr/libexec/cockpit-sessio> myserver.domain.com systemd-logind[1067]: Session 39 logged out. Waiting for processes to exit. myserver.domain.com systemd-logind[1067]: Removed session 39. -- Subject: Session 39 has been terminated -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A session with the ID 39 has been terminated.

1 0

Renamed "priority" github label to "release-blocker"
by Martin Pitt 04 Jul '19

04 Jul '19

Hello all, in practice we've been using the "priority" label as "must go into the next release" for a while. Since our move of CI to AMQP the label actually hasn't influenced the test queue priority; in principle we could implement that, but so far we never bothered as we have enough capacity anyway. So I renamed the label to "release-blocker", and also gave it a nice red tint: https://github.com/cockpit-project/cockpit/labels/release-blocker Martin

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

cockpit-devel July 2019