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:
Created redmine issue https://projects.theforeman.org/issues/29985 from this bug
Upstream bug assigned to mshira
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29985 has been resolved.
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!
Hi Brad, This PR wasn't released in any version yet, I will create a new release and package it.
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