Bug 1943306

Summary: Hammer Report-Template Complains about 'Input Days from Now' Being Blank
Product: Red Hat Satellite Reporter: myoder
Component: ReportingAssignee: Quinn James <qjames>
Status: CLOSED ERRATA QA Contact: Sam Bible <sbible>
Severity: medium Docs Contact:
Priority: high    
Version: 6.8.0CC: apatel, iballou, jlenz, kgaikwad, mhulan, ofedoren, paji, pcreech, saydas, sbible, wpinheir, zhunting
Target Milestone: 6.15.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-23 17:10:41 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description myoder 2021-03-25 18:43:47 UTC
Description of problem:

This seems like a regression from earlier versions of Satellite.  Trying to generate a Subscription - Entitlement Report throws an error about Input Days from Now.  Earlier versions of Satellite (6.6, 6.7) did not show this issue:

~~~
# hammer report-template list | grep 130
130 | Subscription - Entitlement Report

# hammer report-template generate --report-format yaml --id 130 

Input Days from Now: Value can't be blank
Input Days from Now: Value is not included in the list
~~~

Adding the "--inputs" flag with a value works:

~~~
# hammer report-template generate --report-format yaml --id 130 --inputs "Days from Now"="no limit"
~~~

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

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
report template fails to run due to error about "Days from Now"

Expected results:
report template should generate without warning

Additional info:

Comment 1 Marek Hulan 2021-03-30 09:00:17 UTC
I think the earlier versions of Satellite didn't contain this report template. This was introduced with 6.8 if I'm not mistaken. CC Jeremy who introduced it, perhaps he has more thoughts. I think the valid value for this filter is "no limit" as you found out. Perhaps we should also permit nil value for making API/hammer experience easier.

Comment 2 Jeremy Lenz 2021-03-30 13:24:46 UTC
You can see the other possible values if you generate the report in the web UI.  "No limit" is the default.  No hammer changes were made as a part of this feature addition, so maybe something additional needs to be done to make hammer not require that parameter..

Comment 3 Waldirio M Pinheiro 2021-03-30 18:50:42 UTC
Hello,

Could you set "no limit" as standard when calling the hammer command as below?

---
# hammer report-template generate --report-format yaml --id 130
---

I believe this is the main point here.


Thank you friends!

Waldirio

Comment 4 Waldirio M Pinheiro 2021-03-30 18:51:27 UTC
*standard input.

Thank you
Waldirio

Comment 5 Oleh Fedorenko 2021-04-20 14:18:32 UTC
Created redmine issue https://projects.theforeman.org/issues/32359 from this bug

Comment 14 Brad Buckingham 2023-10-30 11:29:29 UTC
Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Comment 15 Bryan Kearney 2023-12-06 20:01:16 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32359 has been resolved.

Comment 16 Sam Bible 2024-01-10 03:34:14 UTC
Verified on 6.15 - Snap 5

Steps to test:
1. Navigate to Monitor -> Reports -> Report Templates
2. Edit the 'Subscription - Entitlement Reports'

Expected Results:
The 'Days from Now' field has "no limit" set as the default.

Actual Results:
The 'Days from Now' field has "no limit" set as the default.

Comment 20 errata-xmlrpc 2024-04-23 17:10:41 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 (Important: Satellite 6.15.0 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-2024:2010