Actions
Bug #4324
closed
VMware NIC type incorrectly shows E1000 instead of vmxnet3
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.
Updated by Ewoud Kohl van Wijngaarden almost 11 years ago
- Related to Bug #4307: New VMware VM creation does not respect NIC type selection added
Updated by marcelo veglienzone almost 11 years ago
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 )
Updated by Dominic Cleal almost 11 years ago
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.
Updated by marcelo veglienzone almost 11 years ago
Just saw the new version which supposedly fixed all this
Updated by Ewoud Kohl van Wijngaarden almost 11 years ago
Updated by Anonymous almost 11 years ago
- 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.
Updated by Dominic Cleal almost 11 years ago
- Blocked by Tracker #4582: Upgrade to fog > 1.20 added
Updated by Dominic Cleal almost 11 years ago
- Has duplicate Bug #4933: Incorrect NIC type for VMware hosts added
Updated by Dominic Cleal over 10 years ago
- 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
Actions