Investigating in https://github.com/cockpit-project/cockpit-machines/pull/110 , this smells like a regression in libvirt 7.2.0

previous CI run failure flaked TestMachinesNICs.testNICAdd. Retrying for comparison.

I downloaded from the current 241-1.fc34 to 242.1-1.fc34. The upgrade worked fine, the Page works, and there is no visual difference (as intended).

Confirming that this package works well together with the new tmt in https://copr.fedorainfracloud.org/coprs/frantisekz/testcloud-wip/packages/ for running in toolbox with session qemu. Splendid, thank you!

I ran all of cockpit's realmd tests (FreeIPA and AD) against this update, and it works fine again. Thank you!

@kalev: Ack, sorry about that. Thank you! I rebuilt my tree with -8, and firefox works.

New package dropped the libXt dependency, which is still needed. Firefox does not start up any more. Reported as https://bugzilla.redhat.com/show_bug.cgi?id=1922935

Thanks a lot @spot for your work in maintaining chromium. I can assure you that we (cockpit team) depend on having a good Chromium Fedora package, and that your effort is much appreciated!

Honestly I have a hard time shedding a lot of emotions about this. People who care about not using Google proprietary stuff (like me, although I use Firefox on desktop and phone) shouldn't/won't use the proprietary bookmark sync either; and people who don't care will either not care much about using chrome vs. chromium?

My current fedora-32 VM still has pam-1.3.1-28.fc32.x86_64. I don't see the root:wheel/0640 cockpit motd for neither unprivileged nor wheel users.

Upgrading to pam 1.3.1-29.fc32 in updates, same result.

Upgrading to 1.3.1-30.fc32 in updates-testing (this bodhi update), I see the motd for a wheel user, but not for an unpriv user. So this works exactly as advertised. Thank you!

Validation

Without this fix, the upgrade fails:

$ podman run -it --rm registry.fedoraproject.org/f33/fedora-toolbox:33 dnf install -y vim
[..]
Error: Transaction test error:
  file /etc/profile.d/vim.sh from install of vim-enhanced-2:8.2.2115-1.fc33.x86_64 conflicts with file from package vim-minimal-2:8.2.1885-1.fc33.x86_64

With this fix, it works fine:

$ podman run -it --rm registry.fedoraproject.org/f33/fedora-toolbox:33 dnf install --enablerepo=updates-testing -y vim
[...]
  Preparing        :                                                                                                                   1/1 
  Installing       : gpm-libs-1.20.7-24.fc33.x86_64                                                                                    1/6 
  Installing       : vim-filesystem-2:8.2.2143-1.fc33.noarch                                                                           2/6 
  Installing       : vim-common-2:8.2.2143-1.fc33.x86_64                                                                               3/6 
  Installing       : vim-enhanced-2:8.2.2143-1.fc33.x86_64                                                                             4/6 
  Upgrading        : vim-minimal-2:8.2.2143-1.fc33.x86_64                                                                              5/6 
  Cleanup          : vim-minimal-2:8.2.1885-1.fc33.x86_64                                                                              6/6 
  Running scriptlet: vim-minimal-2:8.2.1885-1.fc33.x86_64                                                                              6/6 
  Verifying        : vim-common-2:8.2.2143-1.fc33.x86_64                                                                               1/6 
  Verifying        : vim-enhanced-2:8.2.2143-1.fc33.x86_64                                                                             2/6 
  Verifying        : vim-filesystem-2:8.2.2143-1.fc33.noarch                                                                           3/6 
  Verifying        : gpm-libs-1.20.7-24.fc33.x86_64                                                                                    4/6 
  Verifying        : vim-minimal-2:8.2.2143-1.fc33.x86_64                                                                              5/6 
  Verifying        : vim-minimal-2:8.2.1885-1.fc33.x86_64                                                                              6/6 

Upgraded:
  vim-minimal-2:8.2.2143-1.fc33.x86_64                                                                                                     

Installed:
  gpm-libs-1.20.7-24.fc33.x86_64                  vim-common-2:8.2.2143-1.fc33.x86_64         vim-enhanced-2:8.2.2143-1.fc33.x86_64        
  vim-filesystem-2:8.2.2143-1.fc33.noarch       

Thanks!

Missing comma in this commit:

--- /usr/share/containers/seccomp.json  1970-01-01 01:00:00.000000000 +0100
+++ /tmp/seccomp.json   2020-10-25 20:09:18.724815976 +0100
@@ -760,7 +760,7 @@
            "names": [
                "settimeofday",
                "stime",
-               "clock_settime"
+               "clock_settime",
                "clock_settime64"
            ],
            "action": "SCMP_ACT_ALLOW",

Indeed, completely broken, same error. It's a syntax error in the seccomp profile:

❱❱❱ json_reformat < /usr/share/containers/seccomp.json
parse error: after array element, I expect ',' or ']'
                                        {   "defaultAction": "SCMP_ACT_
                     (right here) ------^

This was pilot error in our test infrastructure. Argh, how do I unpush this? :-(

Installs fine now, many thanks!

Weird.. This was submitted two days ago, and is still not "visible" by dnf updates. Apparently the upload → testing propagation already took 1½ days. I'll test this ASAP.

Thanks for your fast fix, @limb!

Awesome, this is the first-ever toolbox version that Just Works™ for me for both Fedora and Debian containers. I dropped all my hacks. Well done!

Works well and unbreaks cockpit-podman.

logs

• The above sssd-infopipe error is fixed by https://src.fedoraproject.org/rpms/cockpit/pull-request/27
• TestServices.testBasic gets fixed by https://github.com/cockpit-project/cockpit/pull/14338

I'm still investigating why the libvirt default network disappears. This happens upstream as well in rare occasions, but is some race condition.

Oops, this looks like a regression in sssd:

+ busctl call org.freedesktop.sssd.infopipe /org/freedesktop/sssd/infopipe/Users org.freedesktop.sssd.infopipe.Users FindByCertificate s -- "$(cat /var/lib/cockpittest/alice.pem)" | sed 's/^o "//; s/"$//' 
?[0;1;31mCall failed: The name is not activatable?[0m