Bug #4324
closed
VMware NIC type incorrectly shows E1000 instead of vmxnet3
Added by Ewoud Kohl van Wijngaarden about 10 years ago.
Updated almost 6 years ago.
Category:
Compute resources
|
|
Description
When I edit a VM in Foreman 1.4.0-1.el6, it shows both NICs are E1000 while in fact they are vmxnet3.
- Related to Bug #4307: New VMware VM creation does not respect NIC type selection added
The same applies to the hard disk, no matter what you mark it's always set to thin provisioning ( it even happens when modifying the compute profile, it always goes back to thin )
marcelo veglienzone wrote:
The same applies to the hard disk, no matter what you mark it's always set to thin provisioning ( it even happens when modifying the compute profile, it always goes back to thin )
The thin provisioning option should be fixed via #4159 in Foreman 1.4.1.
Just saw the new version which supposedly fixed all this
- Status changed from New to Pending
Setting this to pending. This depends on a new version of fog to be released and set for foreman to be used.
- Has duplicate Bug #4933: Incorrect NIC type for VMware hosts added
- Status changed from Pending to Closed
- Assignee set to Martin Matuška
- Target version set to 1.8.4
- % Done changed from 0 to 100
- translation missing: en.field_release set to 4
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous