Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
- The vCPUs in RHV are getting reset to one vCPU after editing a host in Satellite
Version-Release number of selected component (if applicable):
- Satellite 6.8.6
- Satellite 6.10.2
- RHV 4.4.9.5
How reproducible:
Whenever a host is edited in Satellite
Steps to Reproduce:
1. Set vCPU in RHV from 1 to 2
2. Go to edit page of the host in Satellite
3. Check how many vCPUs are assigned in the Virtual Machine tab, all fields are grayed out but it should show 2 vCPU
4. Save without changing anything
5. The ammount of vCPUs in RHV has now changed to 1 vCPU
Actual results:
- Satellite overrides the ammount of vCPUs that may have been changed in RHV
- If the memory has changed it is not changed by Satellite
Expected results:
- Satellite should not override the ammount of assigned vCPU after initial installation
Additional info:
- I was not able to reproduce this when using "hammer host update"
- Assigning a new hostgroup from the "All Hosts" page does not trigger the reset
The fix from https://github.com/fog/fog-ovirt/pull/104 has been successfully tested on
- Satellite 6.8.6
- Satellite 6.10.2
- Satellite 7.0 Snap 8
While 6.8 is out of maintenance support I like to request a backport to 6.9 and 6.10 for it.
Comment 13Lukáš Hellebrandt
2022-09-07 13:14:01 UTC
Verified with Sat 6.12 snap 9.0.
1) I created a VM through Satellite, have it running. It has 3 vCPUs (as per both Satellite and RHV).
2) I edited the VM in Satellite (Hosts -> <host> -> Edit), left vCPUs intact (it can't be edited anyway as it's greyed out). Submitted the form. It still has 3 vCPUs.
3) I shut the VM down through Satellite and did 2) again. It still has 3 vCPUs.
4) I edited the VM through RHV to have 5 vCPUs. It now shows 5 vCPUs both in RHV and in Satellite's edit form (greyed out).
5) I did 2) again. It still has 5 vCPUs.
6) I edited through Hammer:
```
# hammer host update --name <name> --comment 'Nobody expects the Spanish inquisition.'
Host updated.
```
It still has 5 vCPUs.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:8506