Project

General

Profile

Actions

Bug #14211

closed

Host image_id has not effect on the actual image to be used when provisioning

Added by Ivan Necas over 8 years ago. Updated about 6 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

1. create compute resource (e.g. libvirt) with two images configured
2. create a compute profile (libvirt, configure image to be set to first one)
3. provision a host (image-based provisioning) with using the compute profile, but setting --image_id to the second image on the command line

Actual results:
the image from the compute profile is still used, even when other image was set in the hammer

Expected results:
The host image_id takes precedence over the one from the compute profile


Related issues 3 (2 open1 closed)

Related to Foreman - Bug #13764: The image selection in compute profile for image-based provisioning has no effectNew02/17/2016Actions
Related to Foreman - Refactor #14536: Better definition of the merging of compute attributes from different sourcesReady For TestingOndřej EzrActions
Is duplicate of Hammer CLI - Bug #6159: Updating image in compute resource doesn't update the image_id attribute in compute profilesClosedActions
Actions

Also available in: Atom PDF