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

VM in service roles may have nil 'vm_info' #6406

Closed
3 tasks
rsmontero opened this issue Nov 21, 2023 · 1 comment
Closed
3 tasks

VM in service roles may have nil 'vm_info' #6406

rsmontero opened this issue Nov 21, 2023 · 1 comment

Comments

@rsmontero
Copy link
Member

/!\ To report a security issue please follow this procedure:
[https://github.com/OpenNebula/one/wiki/Vulnerability-Management-Process]

Description
In some cases the 'vm_info' of a VM of a role maybe missing after instantiation. It seems, some short of race condition with vm.info call. Code for vm_info initialization

To Reproduce
No deterministic way to reproduce.

Expected behavior
vm_info is either in place or Role fails instantation

Details

  • Affected Component: OneFlow
  • Hypervisor: -
  • Version: -

Additional context
Add any other context about the problem here.

Progress Status

  • Code committed
  • Testing - QA
  • Documentation (Release notes - resolved issues, compatibility, known issues)
@rsmontero rsmontero added this to the Release 6.8.1 milestone Nov 21, 2023
@rsmontero rsmontero self-assigned this Nov 21, 2023
rsmontero added a commit that referenced this issue Nov 23, 2023
After a VM Template is instantiated, the associated VM info is
retreived. This commit retries in case of failure up to 3 times with
linear spacing. If VM info cannot be retreived flow deployment fails
@rsmontero
Copy link
Member Author

rsmontero commented Dec 1, 2023

Code: OpenNebula/one-ee@8a266d770
Docs: OpenNebula/docs@2ca6fac3d

rsmontero added a commit to OpenNebula/docs that referenced this issue Dec 1, 2023
rsmontero added a commit that referenced this issue Mar 11, 2024
After a VM Template is instantiated, the associated VM info is
retreived. This commit retries in case of failure up to 3 times with
linear spacing. If VM info cannot be retreived flow deployment fails

(cherry picked from commit 4b73241)
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

1 participant