Image refresh for fedora-35

[cockpituous]

Image refresh for fedora-35

• image-refresh fedora-35
• webui: use test images from the cockpit's image store rhinstaller/anaconda#3875
• Reformat code for eslint-plugin-react 7.29.x cockpit-podman#933
• src: Reformat EmptyState for eslint-plugin-react 7.29.x cockpit-certificates#83

[cockpituous]

image-refresh in progress on 3-ci-srv-04.
Log: https://logs.cockpit-project.org/logs/image-refresh-2960-20220218-021616/

[cockpituous]

image-refresh in progress on 4-cockpit-10.
Log: https://logs.cockpit-project.org/logs/image-refresh-2960-20220218-021616/

[cockpituous]

image-refresh fedora-35 done: https://github.com/cockpit-project/bots/commits/image-refresh-fedora-35-20220218-023636

[martinpitt]

@KKoukiou, @M4rtinK : You mentioned the python thing yesterday, are you on that?

[martinpitt]

Oh, it's part of rhinstaller/anaconda#3875 , blocking on that

[martinpitt]

Anaconda is broken on the current image as well, as that's related to the tasks container refresh, not the f35 image.

However, the stratis pixel test failure is odd. It's highly unlikely that it is related to the image, but let's retry and compare.

[martinpitt]

Anaconda got unblocked, but the stratis pixel test failure stays. Needs investigation.

[mvollmer]

However, the stratis pixel test failure is odd.

Looks exactly like the updates we did in cockpit-project/cockpit#17013, hmm.

[mvollmer]

However, the stratis pixel test failure is odd.

Looks exactly like the updates we did in cockpit-project/cockpit#17013, hmm.

Seems like #2877 is fixed and we now run more of the tests.

[mvollmer]

Blocked on cockpit-project/cockpit#17051

[martinpitt]

All blockers resolved. I pushed a clean rebase.

[martinpitt]

This now fails on a whole slew of new eslint errors. Could possibly be related to the eslint breakage worked around in cockpit-project/cockpit-machines#597 , but possibly the new eslint version just became a whole lot stricter.

[martinpitt]

I checked the eslint errors in c-podman; locally I don't get the "missing key" errors any more, just the two react/jsx-indent errors, and they are both bogus. The parser gets thoroughly confused.

starter-kit builds fine for me locally, even though on CI last week it ran into several key-errors as well.

The key errors were all due to jsx-eslint/eslint-plugin-react#3215 , so I'll do a round of retries to get an up to date status.

[martinpitt]

Auf ein neues!

[martinpitt]

At last! 🥳