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.
DescriptionVladimír Sedmík
2020-03-17 12:24:31 UTC
Description of problem:
The storage size verification implemented for BZ [1] and [2] behaves differently when 'G' unit is provided.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1700769
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1737418
Version-Release number of selected component (if applicable):
satellite-6.7.0-6.el7sat.noarch
tfm-rubygem-foreman_kubevirt-0.1.7-1.el7sat.noarch
tfm-rubygem-fog-kubevirt-1.3.3-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
see the steps in [1] and [2]
Actual results:
for [1] different error is shown
for [2] passes successfully but shouldn't
Expected results:
for [1] and [2] similar error message as for M,T,P,E units or pass assuming the provided value is in GB
Additional info:
Hi Shira,
Has this fix been built/delivered in a version of foreman kubevirt?
It looks like current Satellite 6.9 builds have: tfm-rubygem-fog-kubevirt-1.3.3-1.el7sat.noarch.rpm , tfm-rubygem-foreman_kubevirt-0.1.8-1.el7sat.noarch.rpm
Thanks!
Verified on Sat 6.10 snap 7.0
tfm-rubygem-foreman_kubevirt-0.1.9-2.el7sat.noarch
tfm-rubygem-fog-kubevirt-1.3.3-2.el7sat.noarch
The values with "G" still pass. However, there is clearly additional parsing done later, as the pvc request passes with correct values.
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 (Moderate: Satellite 6.10 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-2021:4702