Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

testmap: Enable opensuse-tumbleweed on cockpit-podman #6175

Closed
wants to merge 1 commit into from

Conversation

martinpitt
Copy link
Member

No description provided.

@martinpitt
Copy link
Member Author

@Nykseli FYI

@martinpitt
Copy link
Member Author

So this is good progress! Some failures, but lots of green already!

@Nykseli
Copy link
Contributor

Nykseli commented Apr 4, 2024

Thanks!

The test are failing, and to me it seems to be an issue with cockpit-ws and not cockpit-podman. Is there a good workflow for running the podman test suite against locally built cockpit?

@martinpitt
Copy link
Member Author

@Nykseli How do you mean with "cockpit-ws"? That part seems to work fine. Do the failures look differently when you run the test locally?

Going through the failures:

  • testCheckpointRestore screenshot says "crun checkpoint ... failed". Might be missing criu, or some other bug. Should be straightforward to reproduce on the command line. If tumbleweed simply doesn't have criu, then adjust self.has_criu in def setUp() accordingly.
  • testCreatePod{System,User} and testRunImage{System,User}: all the same root cause. perhaps opensuse doesn't use SELinux ? If not, adjust self.has_selinux accordingly
  • testLifecycleOperationsUser: podman doesn't report memory usage, perhaps that cgroup controller isn't enabled? Needs CLI investigation.

So at first sight the failures are all quite straightforward?

@Nykseli
Copy link
Contributor

Nykseli commented Apr 5, 2024

I saw that there was bunch of errors like this:

CDP: {"source":"network","level":"error","text":"Failed to load resource: the server responded with a status of 404 (ERROR)","timestamp":1712242957368.314,"url":"http://127.0.0.2:9291/cockpit/@localhost/*/po.js","networkRequestId":"12805.21"}

Which seemed like something wrong with cockpit-ws. But I guess those are not fatal errors?

Thanks @martinpitt for pointing me into the right direction. I'll look into fixing those issues!

@martinpitt
Copy link
Member Author

@Nykseli Ah, ignore these -- that just means it was looking for English translation files and there aren't any. Indeed it's annoying, I suppose in the cockpit team we just all learned to not even "see" these any more 😅

@Nykseli
Copy link
Contributor

Nykseli commented Apr 5, 2024

Ah, so errors that are not really errors. Good to know. I'll stop seeing them as well! 😄

@martinpitt
Copy link
Member Author

Closing this for now, it's stale. Let me know if/when you want to enable this project for opensuse.

@martinpitt martinpitt closed this May 29, 2024
@martinpitt martinpitt deleted the suse-podman branch May 29, 2024 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants