Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

Cloud-Hypervisor sporadically fails #732

Closed
sboeuf opened this issue Feb 4, 2020 · 0 comments
Closed

Cloud-Hypervisor sporadically fails #732

sboeuf opened this issue Feb 4, 2020 · 0 comments
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.

Comments

@sboeuf
Copy link

sboeuf commented Feb 4, 2020

Some failures related to Cloud-Hypervisor have been reported here.
@sboeuf sboeuf added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Feb 4, 2020
sboeuf pushed a commit to sboeuf/agent that referenced this issue Feb 4, 2020
protocols: client: Increase connection retry timeout
e255378 
The client needs more than 15s to retry connecting to the agent since
we know the agent might take some time to be ready and listen onto
vsock. Indeed, in the context of the CI running nested virtualization,
the VM might take some time to be spawned and it might boot a bit slower
than expected, which means we need to let more time to the agent to
listen on the AF_VSOCK socket.

Bumping to 60s is acceptable since it will still make the container
fails fairly quickly if things are really broken for some other reasons.

Fixes kata-containers#732

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
@sboeuf sboeuf mentioned this issue Feb 4, 2020
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Incorrect behaviour needs-review Needs to be assessed by the team.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

protocols: Fix Cloud-Hypervisor CI regarding hvsock sboeuf/agent
2 participants
@jodh-intel @sboeuf