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.

Created attachment 1358644 [details]
RHEV memory add

Description of problem:


Version-Release number of selected component (if applicable):
Build:Satellite 6.3.0 snap26

How reproducible:
Always

Steps to Reproduce:
1. Provsion a Host on RHEV
2. Edit the host, go to Virtual machine tab. All options are greyed
3. Use the min max controller to increase the memory

Actual results:
The increase memory Config is sent to rhev and is applied on the Host's next run

Expected results:
1) The Memory field shouldn't be greyed out and it should show a not on editing, that changes would take effect in next run
OR 
2) If we don't want the configuration edited from satellite ,Completely disable the min max field. 

I think we should go with 1.

Additional info:
This behavior doesn't Happen with CPU Cores

Created redmine issue https://projects.theforeman.org/issues/24160 from this bug

Upstream bug assigned to mshira

Upstream bug assigned to mshira

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24160 has been resolved.

This will probably be reverted in upstream by https://projects.theforeman.org/issues/27391 as the solution introduced other issues.

Verified with Sat 6.7 snap 15 using reproducer from OP. The field is greyed out and the up/down arrows are not shown at all.

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, 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-2020:1454