action #23774
Updated by nicksinger over 6 years ago
### Current Issue ============= We've had network issues with the IPMI worker in before. Now that they are fixed, it turns out that gnome@64bit-ipmi (https://openqa.suse.de/tests/1132258) is pretty unstable in establishing a new connection to the SUT after sshd has started. It times out to early. Unfortunately i could not make out where this test uses the variable SUT_IP (this IP gets accessed according to the autoinst-log.txt after installation over IPMI_HOSTNAME). Excerpt from the autoinst-log.txt: <blockquote> 13:46:50.8593 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused 13:46:51.8603 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused 13:46:52.8614 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused 13:46:53.8626 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused 13:46:54.8636 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused 13:46:55.8645 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused 13:46:56.8656 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused 13:46:57.8666 31832 Error connecting to host <10.162.2.87>: IO::Socket::INET: connect: Connection refused </blockquote> Until this issue is fixed I suggest to remove this test suite from our current tests. ### Proposed solution ================= The timeout to connect to the SUT_IP needs to be increased from 7 seconds to at least 30 seconds up to 2 minutes.