Bug 1192176

Summary: Fully configuring Trends cannot be done through the Web UI, have to finish task using CLI
Product: Red Hat Satellite Reporter: Matt Reid <mreid>
Component: ReportingAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.6CC: bbuckingham, bkearney, oezr, oprazak, rohoover
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/9441
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-06 19:26:45 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 Matt Reid 2015-02-12 18:46:44 UTC 
Description of problem:
I'll admit I don't fully understand what Trends will end up showing me, since I haven't gotten it working, but it seems odd that we force users to use both the Web UI and the CLI to get them set up.

When you first visit the Trends page, and there's nothing configured, you see:
"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 'rake trends:counter' every Puppet Interval (30 minutes)."

If you click on New Trend Counter, and make something, the message changes:
"No trend counter found.
To start collecting trend data, set a cron job to execute 'RAILS_ENV=production bundle exec rake trends:counter' every Puppet Interval (30 minutes)"

Why can't I fully configure Trends through the Web UI? Couldn't we configure that through Satellite and have Sat push any CLI commands needed in the background? 


Also, there's no ending punctuation for that second message.


Version-Release number of selected component (if applicable):
6.0.6
Comment 1 RHEL Program Management 2015-02-12 19:03:28 UTC 
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3 Bryan Kearney 2015-02-18 21:08:35 UTC 
Created redmine issue http://projects.theforeman.org/issues/9441 from this bug
Comment 4 Bryan Kearney 2015-08-25 18:33:47 UTC 
Upstream bug component is Provisioning
Comment 5 Bryan Kearney 2015-08-25 18:53:18 UTC 
Upstream bug component is WebUI
Comment 6 Bryan Kearney 2016-07-08 20:31:20 UTC 
Per 6.3 planning, moving out non acked bugs to the backlog
Comment 8 Bryan Kearney 2016-08-10 19:06:21 UTC 
Upstream bug component is Reporting
Comment 9 Bryan Kearney 2016-08-10 20:07:19 UTC 
Upstream bug component is WebUI
Comment 10 Bryan Kearney 2016-08-10 22:07:07 UTC 
Upstream bug component is Reporting
Comment 11 Bryan Kearney 2017-01-06 19:26:45 UTC 
This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.
Comment 12 Ondřej Ezr 2020-10-21 13:53:11 UTC 
The upstream bug has been resolved.