Bug #5196
vCenter NICs attached or detached are not reflected on CONTEXT after the VM is deployed
| Status: | Closed | Start date: | 06/18/2017 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | vCenter | |||
| Target version: | Release 5.4 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | Development |
Description
No matter how a NIC is attached or detached, the CONTEXT does not reflect changes for NICs added once the VM was deployed. It doesn't seem an issue with vCenter driver as the nics are correctly attached or detached, the CONTEXT section of OpenNebula's template does not change and hece the extra config variable in vCenter does not reflect changes in context.
If you detach a NIC that was present in the CONTEXT section, OpenNebula removes it from the CONTEXT but new NICS are invisible to CONTEXT.
History
#1
Updated by Miguel Ángel Álvarez Cabrerizo about 4 years ago
- Status changed from Pending to Closed
- Resolution set to fixed
It was an issue in OpenNebula's core related with object cache, the context is regenerated when a NIC is attached.