Description of problem:
If a rhcos node is configured with multiple nic along with bond configuration. It is expected to see the bond on the rhcos node when you open the machine console.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup the a rhcos node with multiple nic and bond on the kernel cmd line
2. Finally once the node is up, check the console to see if you are able to see the bond configured or not.
Currently bond is not visible on the console.
The node works perfectly fine and the bond is working too, only issue seen is with machine console.
+1. Yes this does look like https://github.com/coreos/console-login-helper-messages/issues/34. Do we all agree it's a cosmetic issue? We should fix it but it's not a blocker for anything if I understand correctly.
Looks like a match to me; keeping Low priority and targeting for 4.6
Fix should now be in this build of RHCOS: https://releases-rhcos-art.cloud.privileged.psi.redhat.com/?stream=releases/rhcos-4.6&release=46.82.202009260308-0#46.82.202009260308-0
I verified this morning that booting with rhcos-46.82.202009260308-0-qemu.x86_64.qcow2 showed the ip address for bond0 on the console:
[ OK ] Started Update UTMP about System Runlevel Changes.
Red Hat Enterprise Linux CoreOS 46.82.202009260308-0 (Ootpa) 4.6
SSH host key: SHA256:LiyrBvwt9f7d0XL1HNW/N//Ba46HliBT59afNPxCBUU (ECDSA)
SSH host key: SHA256:si7fw5e7hDC1WoldYJgoZxE4TuvmTlQOtaceSPG+eBI (ED25519)
SSH host key: SHA256:H23cm/K0agW/9OlSxnqcfECeHlNZ5/jLshYubO0MbsU (RSA)
bond0: 192.168.122.111 fe80::5054:ff:fe05:3a6f
I used kernel arguments:
rd.neednet=1 ip=192.168.122.111::192.168.122.1:255.255.255.0:initrdhost:bond0 nameserver=22.214.171.124 bond=bond0:ens2,ens3:mode=active-backup
The 46.82.202009260308-0 version has:
$ rpm-ostree status
Version: 46.82.202009260308-0 (2020-09-26T03:12:09Z)
$ rpm -qa | grep console-login-helper-messages
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.