Bug 1378494

Summary: Suggested command for creating trends counter does not exist
Product: Red Hat Satellite Reporter: Steffen Froemer <sfroemer>
Component: BrandingAssignee: Bryan Kearney <bkearney>
Status: CLOSED ERRATA QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.2.2CC: bbuckingham, bkearney, inecas, jcallaha, jhutar, mburgerh, sjayapra, sshtein, szadok
Target Milestone: UnspecifiedKeywords: 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: 2018-02-21 17:32:10 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:

Description Steffen Froemer 2016-09-22 14:48:33 UTC 
Description of problem:
The suggested command for creating trends counter does not exists

Version-Release number of selected component (if applicable):
satellite-6.2.2-1.1.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. In Monitor -> Trends -> Add New Trend create new trend
2. Check info message which appears above the table of the trends after you
   submit the create form


Actual results:
This appears:
| No trend counter defined To define trend counters, use the Add Trend Counter button.
| To start collecting trend data, set a cron job to execute 'satellite-rake trends:counter' 
| every Puppet Interval (30 minutes). 

When running the suggested command, following error message is shown:
[root@satellite6 ~]# satellite-rake trends:counter
-bash: satellite-rake: command not found



Expected results:
The command should work.

Additional info:
It seems there is a renaming-issue. There is a working command available:

'foreman-rake trends:counter'
Comment 3 Shimon Shtein 2016-12-20 09:54:23 UTC 
*** Bug 1377679 has been marked as a duplicate of this bug. ***
Comment 4 Shimon Shtein 2016-12-26 13:16:03 UTC 
*** Bug 1335069 has been marked as a duplicate of this bug. ***
Comment 9 Bryan Kearney 2017-04-03 11:41:03 UTC 
6.3 with the translations on the fly will not hit this. I am moving this to ON_QA for 6.3 for verification.
Comment 11 Bryan Kearney 2018-02-21 17:32:10 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-2018:0336
Comment 12 Bryan Kearney 2018-02-21 17:32:52 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-2018:0336