Project

General

Profile

Actions

Bug #5833

closed

suggested command do not work when created new trend counter

Added by Dominic Cleal almost 10 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Web Interface
Target version:
Difficulty:
trivial
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1079975
Description of problem:
Suggested command do not work when created new trend counter (or companying text message does not make it clear how to use it)

Version-Release number of selected component (if applicable):
Satellite-6.0.3-RHEL-6-20140321.2

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 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)

When I run it on Sat6 command line I get:
  1. RAILS_ENV=production bundle exec rake trends:counter
    bash: bundle: command not found

Expected results:
It should be clear what i should do and how.

Actions #1

Updated by Dominic Cleal almost 10 years ago

  • Category set to Web Interface
  • Difficulty set to trivial

This should refer to "foreman-rake".

Actions #2

Updated by Joseph Magen almost 10 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Joseph Magen
  • Target version set to 1.8.2
Actions #3

Updated by Anonymous over 9 years ago

  • Target version changed from 1.8.2 to 1.8.1
Actions #4

Updated by Anonymous over 9 years ago

  • Target version changed from 1.8.1 to 1.8.0
Actions #5

Updated by The Foreman Bot over 9 years ago

  • Pull request https://github.com/theforeman/foreman/pull/1466 added
Actions #6

Updated by Anonymous over 9 years ago

  • Target version changed from 1.8.0 to 1.7.5
Actions #7

Updated by Anonymous over 9 years ago

  • Target version changed from 1.7.5 to 1.7.4
Actions #8

Updated by Anonymous over 9 years ago

  • Target version changed from 1.7.4 to 1.7.3
Actions #9

Updated by Dominic Cleal over 9 years ago

  • Target version changed from 1.7.3 to 1.7.2
Actions #10

Updated by Joseph Magen over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #11

Updated by Daniel Lobato Garcia over 9 years ago

  • translation missing: en.field_release set to 21
Actions

Also available in: Atom PDF