Comments

292 Comments

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.

Breaks existing toolboxes, but that's acceptable at least to me -- containers are not supposed to live forever. Creating a new F34 and Debian unstable toolbox works fine at last, so I could now upgrade to Fedora 35 at last. Thank you!

BZ#1995439 /usr/bin/toolbox linked against glibc-2.34 doesn't run on older glibc

Confirmed to work against FreeiPA 4.9.7, fixes the getcert failure. Thanks!

BZ#2015102 ipa-getcert request fails with JSON-RPC error: 903: an internal error has occurred

Thanks @mgoodwin! As three weeks is still quite far out, do you plan to remove this erratum, so that CIs stop tripping over this?

karma

Same pmlogger service regression as in Fedora 34:

# systemctl start pmlogger
Job for pmlogger.service failed because the service did not take the steps required by its unit configuration.

Oct 11 04:30:00 fedora-35-127-0-0-2-2201 systemd[1]: Starting Performance Metrics Archive Logger...
Oct 11 04:30:00 fedora-35-127-0-0-2-2201 pmlogger[3290]: /usr/libexec/pcp/lib/pmlogger: Warning: Performance Co-Pilot archive logger(s) not permanently enabled.
Oct 11 04:30:00 fedora-35-127-0-0-2-2201 pmlogger[3290]:     To enable pmlogger, run the following as root:
Oct 11 04:30:00 fedora-35-127-0-0-2-2201 pmlogger[3290]:     # /usr/bin/systemctl enable pmlogger.service
Oct 11 04:30:00 fedora-35-127-0-0-2-2201 systemd[1]: pmlogger.service: Failed with result 'protocol'.
Oct 11 04:30:00 fedora-35-127-0-0-2-2201 systemd[1]: Failed to start Performance Metrics Archive Logger.
Oct 11 04:30:01 fedora-35-127-0-0-2-2201 systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 1.

systemctl enable --now pmlogger works, so somehow the "not enabled" warning breaks the service.

karma

Completely breaks pmlogger.service:

# systemctl start pmlogger
Job for pmlogger.service failed because the service did not take the steps required by its unit configuration.

# systemctl status pmlogger
× pmlogger.service - Performance Metrics Archive Logger
     Loaded: loaded (/usr/lib/systemd/system/pmlogger.service; disabled; vendor preset: enabled)
     Active: failed (Result: protocol) since Mon 2021-10-11 04:25:21 UTC; 4s ago
       Docs: man:pmlogger(1)
    Process: 3953 ExecStart=/usr/libexec/pcp/lib/pmlogger start-systemd (code=exited, status=0/SUCCESS)
   Main PID: 3953 (code=exited, status=0/SUCCESS)
        CPU: 110ms

Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Starting Performance Metrics Archive Logger...
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]: /usr/libexec/pcp/lib/pmlogger: Warning: Performance Co-Pilot archive logger(s) not permanently enabled.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]:     To enable pmlogger, run the following as root:
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 pmlogger[3545]:     # /usr/bin/systemctl enable pmlogger.service
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Failed with result 'protocol'.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: Failed to start Performance Metrics Archive Logger.
Oct 11 04:25:19 fedora-34-127-0-0-2-2201 systemd[1]: pmlogger.service: Scheduled restart job, restart counter is at 1.

We found that this makes the UI less discoverable, due to the UI review not being implemented enough yet. Hence, let's not push this version to stable yet.

We found that this makes the UI less discoverable, due to the UI review not being implemented enough yet. Hence, let's not push this version to stable yet.

This actually breaks mounting NTFS devices in udisks (and thus desktops), as ntfs-3g is now uninstallable: https://bugzilla.redhat.com/show_bug.cgi?id=2001755

Unfortunately that already landed in stable.