You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This concerns also smoke tests containing these failing network tests network-static-2-httpks bond2-httpks
In general it hits network tests using KSTEST_NETDEV<X> specification.
The failure happens early in initramfs so nothing can be seen in the logs:
The problem is network device naming scheme which is set by libvirt by os detection so it seems it fails on the iso built by the workflow. enpXxY is expected while ensX is used.
This issue has quite some history it might be good idea to search in git history or in closed issues.
Maybe we need to migrate our runners to Fedora-Cloud-Base-40 (similar to https://gitlab.cee.redhat.com/rhinstaller/builders/-/commit/c06f7b8c4c853de61b064b439e524cbfe99650ff) to be able to detect F42 correctly, but why the detection seems to be working on regular F42 boot iso?
I briefly checked the iso volume id, it seems correct, but the mechanism works probably on a bit different level.
The text was updated successfully, but these errors were encountered:
rvykydal
changed the title
network tests specifying device name failing on Fedora 42 iso built by Anaconda PR CI github workflow
network tests specifying device name failing (timeout) on Fedora 42 iso built by Anaconda PR CI github workflow
Feb 19, 2025
This concerns also smoke tests containing these failing network tests
network-static-2-httpks
bond2-httpks
In general it hits network tests using
KSTEST_NETDEV<X>
specification.The failure happens early in initramfs so nothing can be seen in the logs:

It works on regular F42 boot.iso, it fails on iso created by this workflow: https://github.com/rhinstaller/anaconda/actions/runs/13372582869/workflow
The problem is network device naming scheme which is set by libvirt by os detection so it seems it fails on the iso built by the workflow.
enpXxY
is expected whileensX
is used.This issue has quite some history it might be good idea to search in git history or in closed issues.
Maybe we need to migrate our runners to Fedora-Cloud-Base-40 (similar to https://gitlab.cee.redhat.com/rhinstaller/builders/-/commit/c06f7b8c4c853de61b064b439e524cbfe99650ff) to be able to detect F42 correctly, but why the detection seems to be working on regular F42 boot iso?
I briefly checked the iso volume id, it seems correct, but the mechanism works probably on a bit different level.
The text was updated successfully, but these errors were encountered: