Bug #4603
VM template with non-existing VNET can be instantiated in Sunstone (not on cli)
| Status: | Closed | Start date: | 06/28/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Sunstone | |||
| Target version: | - | |||
| Resolution: | worksforme | Pull request: | ||
| Affected Versions: | OpenNebula 5.0 |
Description
When a VNET is referenced (in advanced mode in Sunstone) that does not exist, the VM template can still be instantiated and the VM will not contain the non-existing vnet interface. However, no error message is given. On the cli this does still work. For example:
[TemplateInstantiate] Error allocating a new virtual machine template. User 0 does not own a network with name: vlan2689 . Set NETWORK_UNAME or NETWORK_UID of owner in NIC.
History
#1
Updated by Ruben S. Montero about 5 years ago
- Target version set to Release 5.0.2
#2
Updated by Carlos Martín about 5 years ago
Hi,
Can you share your NIC section? It is working as it should for me, I'm testing with
NIC = [ NETWORK = "doesnotexist" ]
#3
Updated by Carlos Martín about 5 years ago
- Category set to Sunstone
#4
Updated by Jaime Melis almost 5 years ago
- Target version deleted (
Release 5.0.2)
"Worksforme", waiting for feedback in order to reproduce the issue.
#5
Updated by Tino Vázquez over 4 years ago
- Status changed from Pending to Closed
- Resolution set to worksforme