The failure here seems to be a genuine one, but hard to debug. The update test failed the same way - the update transaction seems to complete, then immediately the right pane goes to blank grey and "Ooops!" in red text appears at top right - on both aarch64 and x86_64, on both prod and staging, twice each (so eight times in total), and has never failed that way on another update before or since AFAICT, so it definitely seems to be caused by this update.
This seems to be easily reproducible manually - just run Cockpit and install some updates (it doesn't have to be the special one openQA sets up in its test, I hit it just updating a day-old Rawhide VM). Console log messages:
Object { problem: null, name: "org.freedesktop.DBus.Error.UnknownInterface", message: "Unknown interface 'org.freedesktop.systemd1.Service'.", toString: toString() }
overview.js:69:70827
Transaction has an invalid timespec=2026-01-29T12:57:49.112827-08 updates.js:45:39523
TypeError: can't access property "packages", i[0] is undefined
TR http://localhost:9090/cockpit/@localhost/updates/updates.js:160
lb http://localhost:9090/cockpit/@localhost/updates/updates.js:6
yk http://localhost:9090/cockpit/@localhost/updates/updates.js:8
xk http://localhost:9090/cockpit/@localhost/updates/updates.js:8
DT http://localhost:9090/cockpit/@localhost/updates/updates.js:8
gd http://localhost:9090/cockpit/@localhost/updates/updates.js:8
Eu http://localhost:9090/cockpit/@localhost/updates/updates.js:8
bk http://localhost:9090/cockpit/@localhost/updates/updates.js:8
gg http://localhost:9090/cockpit/@localhost/updates/updates.js:1
fg http://localhost:9090/cockpit/@localhost/updates/updates.js:1
updates.js:8:161
Uncaught TypeError: can't access property "packages", i[0] is undefined
TR http://localhost:9090/cockpit/@localhost/updates/updates.js:160
lb http://localhost:9090/cockpit/@localhost/updates/updates.js:6
yk http://localhost:9090/cockpit/@localhost/updates/updates.js:8
xk http://localhost:9090/cockpit/@localhost/updates/updates.js:8
DT http://localhost:9090/cockpit/@localhost/updates/updates.js:8
gd http://localhost:9090/cockpit/@localhost/updates/updates.js:8
Eu http://localhost:9090/cockpit/@localhost/updates/updates.js:8
bk http://localhost:9090/cockpit/@localhost/updates/updates.js:8
gg http://localhost:9090/cockpit/@localhost/updates/updates.js:1
fg http://localhost:9090/cockpit/@localhost/updates/updates.js:1
updates.js:160:7569
they look like they're a bit minified, but maybe it's still enough? If not I can try to install unminified cockpit somehow...
For help debugging failed Fedora CI tests (fedora-ci.*), contact the Fedora CI team.
For help debugging failed Fedora CoreOS tests (coreos.*), contact the Fedora CoreOS team.
For help debugging failed openQA tests (update.*), contact the Fedora Quality team, who will usually investigate and diagnose all failures within 24 hours.
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
The failure here seems to be a genuine one, but hard to debug. The update test failed the same way - the update transaction seems to complete, then immediately the right pane goes to blank grey and "Ooops!" in red text appears at top right - on both aarch64 and x86_64, on both prod and staging, twice each (so eight times in total), and has never failed that way on another update before or since AFAICT, so it definitely seems to be caused by this update.
Note openQA is currently using a scratch build I did to deal with https://github.com/cockpit-project/cockpit/pull/22800 while awaiting the release of this new version. The scratch build was the same as the 354-2.fc44 official build but with the initial, simple version of my PR - not Martin's improved version - backported. It did not have any other changes.
I'll try and find time to see if I can reproduce this manually later and find any more information about it.
This seems to be easily reproducible manually - just run Cockpit and install some updates (it doesn't have to be the special one openQA sets up in its test, I hit it just updating a day-old Rawhide VM). Console log messages:
they look like they're a bit minified, but maybe it's still enough? If not I can try to install unminified cockpit somehow...
I figured out the problem here and sent a fix. That was a pretty fun one...
This update has been unpushed.
This update was unpushed as part of Fedora 44 Mass Branching because it failed gating tests. Please resubmit these changes for F44 and/or F45/Rawhide.