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

Image refresh for arch #5804

Closed
wants to merge 1 commit into from
Closed

Conversation

cockpituous
Copy link
Contributor

@cockpituous cockpituous commented Jan 18, 2024

Image refresh for arch

  • image-refresh arch

@github-actions github-actions bot added the bot label Jan 18, 2024
@cockpituous cockpituous changed the title Image refresh for arch WIP: 1-cockpit-8: [no-test] Image refresh for arch Jan 18, 2024
@cockpituous
Copy link
Contributor

cockpituous pushed a commit that referenced this pull request Jan 18, 2024
@cockpituous cockpituous force-pushed the image-refresh-arch-20240118-225023 branch from 341ff24 to c08d767 Compare January 18, 2024 22:50
@cockpituous
Copy link
Contributor

@cockpituous cockpituous changed the title WIP: 1-cockpit-8: [no-test] Image refresh for arch Image refresh for arch Jan 18, 2024
@martinpitt
Copy link
Member

The testRaidRepair failure with "losetup: /var/tmp/loop.gAT7: failed to set up loop device: Device or resource busy" and the subsequent cleanup failure is similar to the failures that now often happen in rawhide, e.g. in fedora-selinux/selinux-policy#1998 with this log, or the gating tests in yesterday's rawhide release with this log. That failure has some catastrophic effect on the test VM which doesn't let it recover.

@martinpitt
Copy link
Member

That actually feels very similar to the testMaxLayoutSizes() failure from two weeks ago which also caused the busy loop devices and broken VM. That's been on our pilot board for two weeks, but we didn't look into that yet either.

@martinpitt
Copy link
Member

Let's try this again after cockpit-project/cockpit#19875

@martinpitt martinpitt force-pushed the image-refresh-arch-20240118-225023 branch from c08d767 to d7f62b5 Compare January 22, 2024 14:54
@martinpitt
Copy link
Member

Meh, testMaxLayoutSizes failure again.

@jelly
Copy link
Member

jelly commented Jan 26, 2024

It seems that the kernel was updated linux (6.6.10.arch1-1 -> 6.7.arch3-1) so that might be related.

@martinpitt
Copy link
Member

Superseded by #5861, let's continue debugging there.

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.

3 participants