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:
This PR: https://github.com/theforeman/foreman_kubevirt/pull/118
added validation on the volumes capacity, the issue is that not all compute resource has a capacity, other use size_gb or other names,
the PR causes an issue with submitting the form of compute profile, and  prevent creating a new compute profiles in all compute resources (if the kubevirt plugin in installed.

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

How reproducible:
100%

Steps to Reproduce:
1. Try to create a new compute profile-> submit the form and see that nothing happens.
2.
3.

Actual results:


Expected results:
submitting the form should success

Additional info:

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

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