-
Notifications
You must be signed in to change notification settings - Fork 12
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
failed to ssh to edge vm on cs9 #9155
Comments
This is the boot log, and after I login I found the network is not configured as expected. It should have an ip address of 192.168.100.50, our test script uses this ip to ssh to it. [ OK ] Finished Permit User Sessions. CentOS Stream 9 localhost login: admin |
So it looks like the only packages that changed in the compose are:
The logs show the first service failing as I struggle to understand how the packages that changed would cause that service to fail. Do we have complete boot logs from the failed edge VM? |
Another data point to gather is if this problem affects a "vanilla" CentOS Stream Server install. i.e. when installing from https://odcs.stream.centos.org/production/CentOS-Stream-9-20250108.0/compose/BaseOS/x86_64/iso/CentOS-Stream-9-20250108.0-x86_64-dvd1.iso |
Yes, I have full boot log, didn't paste it here cause it's too long, here it is:
[ 0.000000] Linux version 5.14.0-547.el9.x86_64 ([email protected]) (gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2), GNU ld version 2.35.2-59.el9) #1 SMP PREEMPT_DYNAMIC Mon Dec 30 20:10:38 UTC 2024 Welcome to CentOS Stream 9 dracut-057-79.git20241127.el9 (Initramfs)! [ 3.477360] systemd[1]: No hostname configured, using default hostname. [ 4.372664] systemd[1]: Reached target System Initialization. [ 4.997257] systemd[1]: Reached target Preparation for Remote File Systems. Welcome to CentOS Stream 9! [ 6.653651] systemd[1]: Initializing machine ID from VM UUID. CentOS Stream 9 localhost login: |
These packages are not changed between 20250103.0 and 20250108.0, they are just listed there to show osbuild-composer version that this CI tests with. |
We need to understand which packages have been updated/changed between composes for more hints on where to look for problems. Can we get that list somehow? If we aren't generating that list as part of the test, can we start doing that? |
Yes, we can start to do it, thanks. |
Filed a bug to composer team https://issues.redhat.com/browse/COMPOSER-2433 |
Looking at the test itself, my suggestion would be to capture the output of I don't know if there is a mechanism to store that output in a file somewhere (i.e S3) that can be referenced by future tests, but I think it is possible to make progress on this without waiting for the osbuild team to jump in. |
thanks, I will compare the packages and update the result in jira bug. |
Moved JIRA bug https://issues.redhat.com/browse/COMPOSER-2433 to ostree team https://issues.redhat.com/browse/RHEL-73827 |
Description:
Almost all edge test cases failed on cs9 with compose 20250108.0, after installed edge vm and boot, cannot ssh to vm. I can reproduce it in local test env, found some failures in boot log, after boot I login the vm and found network is not configured correctly, so ssh failed to connect to it.
CI job link:
#9147
Log link:
https://artifacts.osci.redhat.com/testing-farm/87b63988-7607-4a21-bf9f-034111b28436/
Note:
The CI result with compose 20250103.0 is PASS, CI job link #9125
The text was updated successfully, but these errors were encountered: