Comments

320 Comments

I tested this new version with cockpit's tests. My previously reported regression (dispatcher denials for mv) does not happen any more. Thanks!

Actually, we do have the "installability" tests, and they did run -- so waiving them was premature. However, they failed with "Error: Unknown repo: 'brew-90145609'", not in an useful way.

Hmmm... How is it that we still allow obviously uninstallable packages through bodhi? I don't blame humans -- errors happen. I blame the apparent total lack of automated install tests/gating for such easy-to-detect, but critical failures.

$ sudo dnf install nodejs-devel
Last metadata expiration check: 0:00:05 ago on Wed Aug  3 07:15:53 2022.
Error: 
 Problem: conflicting requests
  - nothing provides nodejs-libs(x86-32) = 1:18.6.0-1.fc37 needed by nodejs-devel-1:18.6.0-1.fc37.1.i686
  - nothing provides nodejs(x86-32) = 1:18.6.0-1.fc37 needed by nodejs-devel-1:18.6.0-1.fc37.1.i686
  - nothing provides nodejs(x86-64) = 1:18.6.0-1.fc37 needed by nodejs-devel-1:18.6.0-1.fc37.1.x86_64
  - nothing provides nodejs-libs(x86-64) = 1:18.6.0-1.fc37 needed by nodejs-devel-1:18.6.0-1.fc37.1.x86_64

@zpytela: No, the tests themselves were okay. Just the many avcs.

@g6avk, can you please file a report at https://github.com/cockpit-project/cockpit/issues ? Let's investigate that. Thanks!

See here: https://github.com/cockpit-project/bots/pull/3627 Lots of tests fail with

audit: type=1400 audit(2114380829.764:191): avc:  denied  { search } for  pid=813 comm="mv" name="contexts" dev="vda5" ino=16829 scontext=system_u:system_r:NetworkManager_dispatcher_console_t:s0 tcontext=system_u:object_r:default_context_t:s0 tclass=dir permissive=0
audit: type=1400 audit(2114380829.770:192): avc:  denied  { sys_admin } for  pid=813 comm="mv" capability=21  scontext=system_u:system_r:NetworkManager_dispatcher_console_t:s0 tcontext=system_u:system_r:NetworkManager_dispatcher_console_t:s0 tclass=capability permissive=0
audit: type=1400 audit(2114380829.770:193): avc:  denied  { sys_admin } for  pid=813 comm="mv" capability=21  scontext=system_u:system_r:NetworkManager_dispatcher_console_t:s0 tcontext=system_u:system_r:NetworkManager_dispatcher_console_t:s0 tclass=capability permissive=0

NetworkManager did not change in this image, just

  • selinux-policy (36.11-1.fc36 -> 36.12-1.fc36)
  • kernel-core (5.18.10-200.fc36 -> 5.18.11-200.fc36)

and some others which sound less relevant.

Would you consider dropping this update? Or is a fix for this available in the next days?

This update has been unpushed.

There is something wrong in bodhi. This update keeps spamming me, and it is long obsolete. I'm just going to revoke it.

karma

I confirm this fixes https://bugzilla.redhat.com/show_bug.cgi?id=2074402 , thanks!

Any idea why this is stuck? It was submitted to stable 5 days ago already, but still did not land.

Install and upgrade works fine.

karma

Thanks! I confirm that this fixes https://bugzilla.redhat.com/show_bug.cgi?id=2063853

BZ#2063853 curl fails with "out of memory" on python https server

Thanks @spot! Works great now.

I get the same, can't start chromium any more:

❱❱❱ chromium-browser 
/usr/bin/chromium-browser: symbol lookup error: /usr/bin/chromium-browser: undefined symbol: wl_proxy_marshal_flags

Please, please pleeeease don't fast-pace selinux updates through updates-testing like that. This has broken the world for cockpit (again!), always takes us hours to sort through the fallout, and 10 hours is simply not enough time for us to even run tests -- even the mirrors are not that fast.

karma

Completely broken, as not installable:

Error: 
 Problem: conflicting requests
  - nothing provides (python3.10dist(astroid) < 2.9 with python3.10dist(astroid) >= 2.8) needed by python3-pylint-2.11.1-1.fc36.noarch
(try to add '--skip-broken' to skip uninstallable packages)

@ahmedalmeleh: Is this a regression from 257? I'm afraid this does not happen in general, and I am not sure what exactly you did. Can you please file an issue here: https://github.com/cockpit-project/cockpit-machines/issues/new

Then we can ask for some more details, attach screenshots and debug logs and so on. Thanks!

karma

Installs and upgrades fine, all pages look as expected.