Bug 1754864 - [Kubevirt-Foreman] The creation of a compute profile with volumes and interfaces is not working properly.
Summary: [Kubevirt-Foreman] The creation of a compute profile with volumes and interfa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - CNV
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.7.0
Assignee: Shira Maximov
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks: 1755449 1755451
TreeView+ depends on / blocked
 
Reported: 2019-09-24 09:16 UTC by Shira Maximov
Modified: 2020-04-14 13:26 UTC (History)
4 users (show)

Fixed In Version: rubygem-foreman_kubevirt-0.1.5.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1755449 1755451 (view as bug list)
Environment:
Last Closed: 2020-04-14 13:26:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1454 0 None None None 2020-04-14 13:26:11 UTC

Description Shira Maximov 2019-09-24 09:16:50 UTC
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:

Comment 3 Shira Maximov 2019-09-24 09:17:57 UTC
Created redmine issue https://projects.theforeman.org/issues/27929 from this bug

Comment 10 errata-xmlrpc 2020-04-14 13:26:00 UTC
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


Note You need to log in before you can comment on or make changes to this bug.