Bug #6342
closedCompute profile should be used when empty volumes and interfaces passed in compute_attributes
Description
When creating hosts through the API with hammer, it's fairly unavoidable that you get a params hash containing:
"compute_attributes"=>{"volumes_attributes"=>{},"interfaces_attributes"=>{},"nics_attributes"=>{}}
due to hammer not knowing if a compute profile will be used or not via the host group.
set_compute_attributes in Host::Managed checks for compute_attributes.empty?, which will return false when these empty sub-hashes are present. It should be possible to use the compute profile even when passing in this empty data.
Either that, or CR VM creation should be reliable without them set to {}, but it currently isn't.
Updated by Dominic Cleal almost 11 years ago
- Status changed from New to Ready For Testing
- Assignee set to Dominic Cleal
- Target version set to 1.8.1
Updated by Anonymous about 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 47990639ae6b02f541e5d76b392d5549afd74bc7.
Updated by Guido Günther about 9 years ago
Anonymous wrote:
Applied in changeset 47990639ae6b02f541e5d76b392d5549afd74bc7.
Could this be fixed on 1.10.x as well? We won't be able to update to 1.11.x in not time so this would be awesome.
Updated by Dominic Cleal about 9 years ago
Sorry, this is a behaviour change and has a bit of risk (one regression so far) so it'll only be in 1.11.