Bug 2272107

Summary: 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
Product: Red Hat Satellite Reporter: Joniel Pasqualetto <jpasqual>
Component: Compute ResourcesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: gformisa, nalfassi, rlavi, wpinheir
Target Milestone: UnspecifiedKeywords: MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 17:27:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joniel Pasqualetto 2024-03-28 20:53:45 UTC 
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:
Comment 2 Eric Helms 2024-06-06 17:27:14 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.