Bug 1378494 - Suggested command for creating trends counter does not exist
Summary: Suggested command for creating trends counter does not exist
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Branding
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: Unspecified
Assignee: Bryan Kearney
QA Contact: Katello QA List
URL:
Whiteboard:
: 1335069 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-22 14:48 UTC by Steffen Froemer
Modified: 2021-03-11 14:43 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 17:32:10 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


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