Skip to content
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

FIx LXD drivers shutdown exception handling #3175

Closed
7 tasks
dann1 opened this issue Apr 3, 2019 · 0 comments
Closed
7 tasks

FIx LXD drivers shutdown exception handling #3175

dann1 opened this issue Apr 3, 2019 · 0 comments

Comments

@dann1
Copy link
Contributor

dann1 commented Apr 3, 2019

Description
During shutdown:

  • container is loaded 2 times even if no exception occur
  • vnc connection is not stopped if the container storage fails to be dismantled, leaving
  • wild containers do not get forced stop if timeout is detected
  • reboot action is susceptible to timeout issues

To Reproduce
Steps to reproduce the behavior.

Expected behavior

  • always stop vnc
  • always force shutdown wild containers if running after timeout
  • load only once the container if everything succeeds
  • validate timeout issues in reboot

Details

  • Affected Component: Virtualization Driver
  • Hypervisor: LXD
  • Version: 5.8.0

Additional context
Add any other context about the problem here.

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@dann1 dann1 added this to the Release 5.8.1 milestone Apr 3, 2019
@dann1 dann1 self-assigned this Apr 3, 2019
@rsmontero rsmontero modified the milestones: Release 5.8.1, Release 5.8.2 Apr 3, 2019
dann1 added a commit to dann1/one that referenced this issue Apr 3, 2019
dann1 added a commit that referenced this issue Apr 3, 2019
dann1 added a commit to dann1/one that referenced this issue Apr 5, 2019
dann1 added a commit to dann1/one that referenced this issue Apr 5, 2019
dann1 added a commit to dann1/one that referenced this issue Apr 5, 2019
rsmontero added a commit that referenced this issue Apr 8, 2019
Co-authored-by: Daniel Clavijo Coca <dclavijo@opennebula.systems>
(cherry picked from commit 103cada4150e76b6649ea62b73e8f6f31133b308)
rsmontero added a commit that referenced this issue Apr 8, 2019
Co-authored-by: Daniel Clavijo Coca <dclavijo@opennebula.systems>
(cherry picked from commit 103cada4150e76b6649ea62b73e8f6f31133b308)
dann1 added a commit to dann1/one that referenced this issue Apr 9, 2019
dann1 added a commit to dann1/docs that referenced this issue Apr 9, 2019
dann1 added a commit that referenced this issue Apr 9, 2019
rsmontero pushed a commit to OpenNebula/docs that referenced this issue Apr 9, 2019
dann1 added a commit that referenced this issue Apr 16, 2019
rsmontero pushed a commit that referenced this issue Apr 16, 2019
rsmontero pushed a commit that referenced this issue Aug 2, 2024
Co-authored-by: Tino Vázquez <cvazquez@opennebula.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants