Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-24282

Using hammer to change the hostgroup of a host to a hostgroup that is mapped to a different compute profile tries to update the VM hardware

XMLWordPrintable

    • Bug Fix
    • Hide
      .Compute profile not applied on host update when using Hammer or API

      Previously, when you used Hammer to change a host group associated with a different compute profile, Hammer attempted to update the hardware of your virtual machine.
      The Foreman core has been fixed to prevent compute profile application when a host is updated.
      As a result, when you change a host group of a virtual machine by using Hammer or API, Satellite no longer attempts to update the hardware.
      This behavior is now consistent with the Satellite web UI.
      Show
      .Compute profile not applied on host update when using Hammer or API Previously, when you used Hammer to change a host group associated with a different compute profile, Hammer attempted to update the hardware of your virtual machine. The Foreman core has been fixed to prevent compute profile application when a host is updated. As a result, when you change a host group of a virtual machine by using Hammer or API, Satellite no longer attempts to update the hardware. This behavior is now consistent with the Satellite web UI.
    • Done
    • To Do
    • No

      Description of problem:

      Consider the situation below:

      • hostgroup A created in the past for RHEL7 using a specific compute profile
      • hostgroup B create for RHEL8 using same compute profile as A
      • host H was assigned to hostgroup A. At some point, it has its hardware increased (after being first created)
      • host H was leapped to RHEL8 and now we want to change its hostgroup

      This is what happens:

      1. using hammer (or an ansible playbook) to update the host and change its hostrgroup, will trigger a hardware update on the VM trying to apply the hardware configuration defined on the compute profile

      2. making the hostgroup change on the webUI does not make any changes to the VM

      Version-Release number of selected component (if applicable):

      6.13

      How reproducible:
      Always

      Steps to Reproduce:
      1. Create two compute profiles (with different memory)
      2. Create two hostgroups. Each using one of the compute profiles from 1
      3. Create host with one of the hostgroups
      4. Use hammer to update the host and change to the other hostgroup.

      Actual results:

      • hammer will try to apply the hardware configuration defined on the compute profile into the running VM
      • webUI will bring the current properties of the VM and send it back when updating the host's properties, not triggering a hardware update

      Expected results:

      Ideally, both tools to behave the same way (or at least have a flag to chose if the VM is to be updated or not)

      Additional info:

              Unassigned Unassigned
              rhn-support-jpasqual Joniel Pasqualetto
              Amol Patil Amol Patil
              Lena Ansorgová Lena Ansorgová
              Votes:
              1 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: