Bug #28383
Use the default route interface for the auto-created NIC VM
Seen in:
Severity:
High
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No
Description
VMs do not start with the latest master.
This is because the auto-created NIC somehow does not register.
Choosing Edit and clicking OK to save the NIC fixes this, and then the VM can start.
Associated revisions
- When we create a new VM the virtual nic has no attached device till users go there and choose one from the dropdown menu. In this case, we use the default route interface.
Ticket: #28383
- When we create a new VM the virtual nic has no attached device till users go there and choose one from the dropdown menu. In this case, we use the default route interface.
Ticket: #28383
- When we create a new VM the virtual nic has no attached device till users go there and choose one from the dropdown menu. In this case, we use the default route interface. (#831)
Ticket: #28383
- When we create a new VM the virtual nic has no attached device till users go there and choose one from the dropdown menu. In this case, we use the default route interface. (#832)
Ticket: #28383
History
#1
Updated by Marcelo Araujo almost 3 years ago
- Status changed from Not Started to In Progress
#2
Updated by Marcelo Araujo almost 3 years ago
- Needs Doc changed from Yes to No
#3
Updated by Marcelo Araujo almost 3 years ago
- Status changed from In Progress to Done
#4
Updated by Dru Lavigne almost 3 years ago
- Subject changed from VMs do not recognize the auto-created NIC until the device is edited and saved to Use the default route interface for the auto-created NIC VM
#5
Updated by Dru Lavigne almost 3 years ago
- Needs Merging changed from Yes to No