-
Notifications
You must be signed in to change notification settings - Fork 33
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
Failing tests on CentOS-CI + KVM #121
Comments
Added a sleep statement for the |
Added sleep (as in #122)... but still failing: |
Issue still occasionally occurs as can be seen in the following build for different PRs: |
@gbraad Just to confirm, you have seen these kind of error with local runs too? |
less often, but yes. Although I was in a hurry to test, so didn't pay a lot
of attention.
…On Tue, Jul 25, 2017 at 7:53 PM, Lalatendu Mohanty ***@***.*** > wrote:
@gbraad <https://github.com/gbraad> Just to confirm, you have seen these
kind of error with local runs too?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#121 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZtHnZ2RkATvHJaARECXeOwJI36cLks5sRdcfgaJpZM4Odlv_>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
I am able to reproduce the error locally as well for even starting the VM:
|
add --show-libmachine-logs ;-) and let's see what happens....
This error happens when there is an issue with the provisioning not able to
start... which can be related to the IP address...
is it a lease issue?
…On Tue, Aug 22, 2017 at 10:05 PM, Budh Ram Gurung ***@***.***> wrote:
I am able to reproduce the error locally as well for even starting the VM:
Executing command : /home/budhram/redhat/minishift-centos-iso/tests/../build/bin/minishift start --vm-driver kvm --iso-url file:///home/budhram/redhat/minishift-centos-iso/tests/../build/minishift-centos7.iso
*******
2017-08-22 19:33:10,018 test L0119 DEBUG| Error: E0822 19:26:46.940451 12265 start.go:342] Error starting the VM: Error creating the VM. Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded. Retrying.
E0822 19:29:58.276836 12265 start.go:342] Error starting the VM: Error configuring authorization on host: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded. Retrying.
E0822 19:33:10.016776 12265 start.go:342] Error starting the VM: Error configuring authorization on host: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded. Retrying.
Error starting the VM: Error creating the VM. Error creating machine: Error detecting OS: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
Error configuring authorization on host: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
Error configuring authorization on host: Too many retries waiting for SSH to be available. Last error: Maximum number of retries (60) exceeded
...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#121 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAHZrYIRhIMv3XEkYlfkgt99iQzGwlyks5sauAggaJpZM4Odlv_>
.
--
Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]
|
@gbraad could you add those debugs lines here https://github.com/gbraad/minishift-centos-iso/blob/opt/tests/test.py#L90 then we can see why it is failing in CI. I am also trying locally. The upstream released latest ISO passed locally. |
Logs Logs with upstream releasted latest centos ISO
Logs with Locally built ISO or affected ISO
|
Logs of unsuccessful restart - https://gist.github.com/budhrg/1bdc7444d9796082c212f0b165286bfd |
A sleep of 90s added after the [1] https://github.com/minishift/minishift-centos-iso/blob/master/tests/test.sh#L129 |
This is a general issue, and I have seen this happen from time to time with the CentOS image:
It is unclear why this happens...
The text was updated successfully, but these errors were encountered: