Project

General

Profile

Actions

Bug #6342

closed

Compute profile should be used when empty volumes and interfaces passed in compute_attributes

Added by Dominic Cleal almost 10 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
API
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.


Related issues 7 (1 open6 closed)

Related to Foreman - Feature #4250: Expose compute profiles via APIClosedJoseph Magen02/04/2014Actions
Related to Hammer CLI - Feature #6344: Commands for read operations around compute profiles and attributesClosedTomáš StrachotaActions
Related to Foreman - Bug #13507: Creating VMs with hammer requires too many parametersResolved02/01/2016Actions
Related to Foreman - Bug #14179: Interface/NIC compute attributes in API host creation overwritten with compute profile attributesClosedDominic Cleal03/14/2016Actions
Related to Foreman - Bug #10223: Image provisoning over API doesn't start host automaticallyNew04/21/2015Actions
Has duplicate Hammer CLI - Bug #11829: hammer host create does not send correct compute-attributes information which breaks a condition on the server sideDuplicate09/15/2015Actions
Has duplicate Foreman - Bug #14485: hammer should consider everything from the "Compute Profile"Duplicate04/05/2016Actions
Actions

Also available in: Atom PDF