-
Notifications
You must be signed in to change notification settings - Fork 59
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
F36 VM fails to display the network device information on console #1153
F36 VM fails to display the network device information on console #1153
Comments
I think this issue is mostly related to #1156 $ cosa run -c --kargs='enforcing=0' --qemu-image fedora-coreos-36.20220325.1.0-qemu.x86_64.qcow2
Fedora CoreOS 36.20220325.1.0
Kernel 5.17.0-300.fc36.x86_64 on an x86_64 (ttyS0)
SSH host key: SHA256:QXCTTJ1XD7ATm+d7xjH0acBXiF6onkgfwcfF3klJuz0 (ECDSA)
SSH host key: SHA256:LrrKiADYVYG2Ecm2bRK1SA11ITVGu/uX101gFfa0CJ8 (ED25519)
SSH host key: SHA256:yvNdKoidNkRsiZUqbPJvh2FadFiB4r3LiBwh/US+tQU (RSA)
ens4: 10.0.2.15 fe80::c21:644a:fb6b:9bfc
Ignition: ran on 2022/04/18 20:39:37 UTC (this boot)
Ignition: user-provided config was applied
|
We need to write a test to verify if the network device information gets to the serial console of the machine i.e. a kola test that would fail if we encounter a similar situation in the future. |
The fix for #1156 (see #1156 (comment)) appears to just lead us to another failure:
It does still seem to be SELinux related, just a different fix than #1156 (so we'll need to file a new bug). Here is what I see if I set
|
@aaradhak opened a BZ for this: https://bugzilla.redhat.com/show_bug.cgi?id=2080043 |
I think this should be fixed with the new CLHM release. We'll need to double check. |
Still waiting on a bunch of random denials to get fixed. The latest is in https://bugzilla.redhat.com/show_bug.cgi?id=2080043#c17 |
Aashish Radhakrishnan (2): kola test to check the network device info Ref: coreos/fedora-coreos-tracker#1153 BZ : https://bugzilla.redhat.com/show_bug.cgi?id=2080043 added denial and snooze on network-device-info test Colin Walters (1): tests: Move skopeo test to rpm-ostree/container-deps
Aashish Radhakrishnan (2): kola test to check the network device info Ref: coreos/fedora-coreos-tracker#1153 BZ : https://bugzilla.redhat.com/show_bug.cgi?id=2080043 added denial and snooze on network-device-info test Colin Walters (1): tests: Move skopeo test to rpm-ostree/container-deps
Aashish Radhakrishnan (2): kola test to check the network device info Ref: coreos/fedora-coreos-tracker#1153 BZ : https://bugzilla.redhat.com/show_bug.cgi?id=2080043 added denial and snooze on network-device-info test Benjamin Gilbert (2): tests/kola: move initrd tests into a subdirectory overlay: compress initrd with zstd -19 on FCOS and RHCOS/SCOS 9 Colin Walters (1): tests: Move skopeo test to rpm-ostree/container-deps
The BZ mentioned here is now fixed and fedora-selinux/selinux-policy#1258 is closed, so we can probably re-test/revisit this one. |
@aaradhak - want to test this locally against |
@dustymabe sure, will work on it. |
@dustymabe tested |
Drop denial as the test no longer fails because of selinux-policy-36.13-3.fc36 update. Closes coreos/fedora-coreos-tracker#1153
Drop denial as the test no longer fails because of selinux-policy-36.13-3.fc36 update. Closes coreos/fedora-coreos-tracker#1153
This was fixed in |
The fix for this went into |
The fix for this went into |
Drop denial as the test no longer fails because of selinux-policy-36.13-3.fc36 update. Closes coreos/fedora-coreos-tracker#1153
Drop denial as the test no longer fails because of selinux-policy-36.13-3.fc36 update. Closes coreos/fedora-coreos-tracker#1153
Describe the bug
FCOS-36 VM fails to display the network device information on the serial console.
Reproduction steps
Steps to reproduce the behavior:
virt-install
to install a VMExpected behavior
The network device information should be displayed on the console.
For e.g.
ens2: 192.168.122.87 fe80::296e:b5ca:c85b:ed70
Actual behavior
The network device information is missing from the console.
System details
The text was updated successfully, but these errors were encountered: