Bug #13980
closed
VMWARE: since 1.10, NIC type and Network different from profile configuration
Description
Hi,
It was working fine before update to 1.10, but now when I create a VMware host, interface details such as NIC type and Network are not filled with values configured into vmware profiles.
Foreman propose the first element on each list.
If I look into production log file:
Started POST "/hosts/interfaces"
Processing by HostsController#interfaces as */*
Parameters: (...)"compute_attributes"=>{"type"=>"VirtualE1000", "network"=>"NET1"}}(...)
I can see that parameters sent are not the one defined in profiles.
Thanks.
Updated by Dominic Cleal over 8 years ago
Could you confirm precisely which Foreman version you're on? The Found in release field says 1.10.0, in which case, please update to 1.10.2 as there were a couple of fixes in .1 that might be applicable.
Updated by Lionel Beard over 8 years ago
Dominic Cleal wrote:
Could you confirm precisely which Foreman version you're on? The Found in release field says 1.10.0, in which case, please update to 1.10.2 as there were a couple of fixes in .1 that might be applicable.
Sorry, I made a mistake in release field.
The bug appears in 1.10.0 version, and I have just updated to 1.10.2, and the bug is still here.
It was also present on 1.10.1.
Updated by Dominic Cleal over 8 years ago
- Category changed from VM management to Host creation
- Translation missing: en.field_release set to 145
No problem, thanks for confirming.
Could you run through the exact steps you take on the New Host form, e.g. the order of which boxes you select from and if your compute profile is set on the host group or you're selecting it? If you have the ability to record a video/GIF, this can be very helpful to show the issue.
It might also be worth trying to create a new compute profile in case it's that, and to try some different steps such as selecting the compute profile explicitly or changing the order. The inheritance of profiles changed a lot in 1.10 and is sensitive to this.
Updated by Lionel Beard over 8 years ago
Thanks for your message because, thanks to that, I found a way to resolve the issue.
Actually, no compute profile was set into my host groups. And the bug appears, even if I set a compute profile on host creation form.
Now, I have set a default compute profile on each host groups, and interface details are correct.
It is good for me.
Do you still consider is it a bug?
Do you still want the video?
Updated by Dominic Cleal over 8 years ago
- Related to Bug #11124: Interface compute attributes not merged from API request over compute profile added
Updated by Dominic Cleal over 8 years ago
I think I've reproduced it now rather simply! Are these the same as your steps without the host group?
1. Select the compute resource
2. Select a compute profile
3. Check interfaces tab
Any time you change the compute profile, the attributes/network settings aren't updated.
This seems to work properly if I revert #11124.
Updated by Dominic Cleal over 8 years ago
- Status changed from New to Assigned
- Assignee set to Dominic Cleal
Updated by Dominic Cleal over 8 years ago
- Has duplicate Bug #13779: Setting compute profile in EC2 provisioning over-rides image AMI with a default AMI added
Updated by The Foreman Bot over 8 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3314 added
Updated by Dominic Cleal over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset b299f9c95102be50b1b755376963efed7b3bb6c2.
Updated by Dominic Cleal over 8 years ago
- Related to Bug #13581: Clicking "Resolve" in Operating System -> Provisioning templates causes UI issues with drop-downs in the Interfaces tab added
Updated by Matthew Ceroni over 8 years ago
This fix is applicable to 1.10, however the change does not apply to 1.11 as hosts_controller.rb does not appear to contain the function that is modified.
Has this change been updated in version 1.11 as well?
Updated by Dominic Cleal over 8 years ago
The fix is in both 1.10.3 and 1.11.0-RC3. You're right that the 1.10 and 1.11 fixes differ, I had to rewrite it a little for 1.10.
Fix from 1.11.0-RC3: https://github.com/theforeman/foreman/commit/c404041c6fe4816b9c44e78f1e2225960ab95c9d
Fix from 1.10.3: https://github.com/theforeman/foreman/commit/b3a5c5ffc32536e2514b24f2297aece6273d09b2
Updated by