The status of the issue: `ssh issue on libvirt based images` of project:
`atomic-wg` has been updated to: Closed by dustymabe.
https://pagure.io/atomic-wg/issue/232
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to
dustymabe added a new comment to an issue you are following:
``
haven't seen this lately - let's close it and re-open if the issue pops back up
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/232
___
cloud
ilmostro added a new comment to an issue you are following:
``
>Finally managed to isolate the issue. If we boot the image with only one CPU,
>the error comes up. If we boot with 2 or more CPU(s), no issues at all. Now
>the question is if we should make local testing on Autocloud with 2 CPU(s) o
mattdm added a new comment to an issue you are following:
``
I'd like to look at the logs still. :)
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/232
___
cloud mailing list -- cloud@lists.fedoraproject.o
kushal added a new comment to an issue you are following:
``
> Kushal, were you able to get the system logs from a failed image?
Nope, but I managed to get the tests working on the same boxes if we wait much
longer time for the ssh to come back.
So I pushed tunir-0.17.1 in production after tes
mattdm added a new comment to an issue you are following:
``
Kushal, were you able to get the system logs from a failed image?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/232
___
cloud mailing list --
trishnag added a new comment to an issue you are following:
``
It worked fine for me. Tested with 1 vcpu and 2 vcpu(s). Unable to reproduce
the issue.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/232
_
roshi added a new comment to an issue you are following:
``
I can say that with my ansible tests (run on an instance locally with
testcloud) this issue does not happen.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/232
___
dustymabe added a new comment to an issue you are following:
``
hey @kushal, is there any way at all to reproduce this issue outside of the
test suite? I'm thinking this probably falls into one of a few different
categories:
- This is easily reproducible with a specific VM libvirt configuration
kushal reported a new issue against the project: `atomic-wg` that you are
following:
``
During our Atomic tests, after disabling the chronyd service, we reboot the VM.
After that the ssh serivce is not coming back on time. This VM has one vcpu in
it.
Sometimes we saw behaviour on Vagrant libvi
10 matches
Mail list logo