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

kola multipath tests fail on F42 with dracut-103-1.fc42 #1803

Open
marmijo opened this issue Sep 26, 2024 · 2 comments
Open

kola multipath tests fail on F42 with dracut-103-1.fc42 #1803

marmijo opened this issue Sep 26, 2024 · 2 comments
Labels
jira for syncing to jira pipeline failure This issue or pull request is derived from CI failures

Comments

@marmijo
Copy link
Member

marmijo commented Sep 26, 2024

The multipath.day1 and multipath.day2 kola tests are failing after updating to the latest dracut package in F42 rawhide.

The following is seen in the console output of the two tests:

Welcome to Fedora CoreOS 42.20240923.dev.0 dracut-103-1.fc42 (Initramfs)!

[    0.639444] systemd[1]: No hostname configured, using default hostname.
[    0.639766] systemd[1]: Hostname set to <localhost>.
[    0.640027] systemd[1]: Initializing machine ID from VM UUID.
[    0.677426] systemd[1]: bpf-restrict-fs: LSM BPF program attached
[    0.688114] ln: 
[    0.688116] failed to create symbolic link '/var/log'
[    0.688245] : Read-only file system
[    0.688468] 
[    0.736799] systemd[1]: Failed to isolate default target: Unit multipathd.service not found.
[!!!!!!] Failed to isolate default target.
[    0.782942] systemd[1]: Freezing execution.

Full console output: multipath.day2.console.txt

pinning dracut-102-2.fc41 in rawhide, as well as the dependent clevis package, allows these tests to pass without issue.


EDIT: opened the issue before filling out all information:

The recent changes to the dracut package can be found here:

@marmijo marmijo added the pipeline failure This issue or pull request is derived from CI failures label Sep 26, 2024
marmijo added a commit to marmijo/fedora-coreos-config that referenced this issue Sep 26, 2024
dustymabe pushed a commit to coreos/fedora-coreos-config that referenced this issue Sep 26, 2024
@marmijo marmijo added the jira for syncing to jira label Sep 30, 2024
@jlebon
Copy link
Member

jlebon commented Oct 1, 2024

Offhand perusing the dracut commits, this looks like a possibly a regression from dracut-ng/dracut-ng@377d52c and dracut-ng/dracut-ng@4957ffa, and which was then fixed by dracut-ng/dracut-ng@1e802f1. We could verify that it fixes the tests, and propose to have it backported to the dracut maintainers in Fedora.

The /var/log message in the output above is likely non-fatal and unrelated to the hard failure here. It's probably a systemd generator that needs to be adapted to work with latest systemd (see coreos/fedora-coreos-config#3014, esp. coreos/fedora-coreos-config#3014 (comment)).

jlebon added a commit to jlebon/fedora-coreos-config that referenced this issue Oct 1, 2024
The multipath module has been included by default so we didn't need to
do this, but a bug has recently made it stop being included:

coreos/fedora-coreos-tracker#1803 (comment)

We should have been declaring that dependency here anyway.
@jlebon
Copy link
Member

jlebon commented Oct 1, 2024

Threw up coreos/fedora-coreos-config#3187

dustymabe pushed a commit to coreos/fedora-coreos-config that referenced this issue Oct 1, 2024
The multipath module has been included by default so we didn't need to
do this, but a bug has recently made it stop being included:

coreos/fedora-coreos-tracker#1803 (comment)

We should have been declaring that dependency here anyway.
dustymabe added a commit to dustymabe/fedora-coreos-config that referenced this issue Oct 1, 2024
This reverts commit abe168b.

We think we have addressed the underlying problem now with
coreos#3187

Closes: coreos/fedora-coreos-tracker#1803
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jira for syncing to jira pipeline failure This issue or pull request is derived from CI failures
Projects
None yet
Development

No branches or pull requests

2 participants