Red Hat Bugzilla – Bug 1079975
suggested command do not work when created new trend counter
Last modified: 2017-02-23 16:18:11 EST
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: # 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.
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.
Created redmine issue http://projects.theforeman.org/issues/5833 from this bug
fixed https://github.com/theforeman/foreman/pull/1466
Moving to POST since upstream bug http://projects.theforeman.org/issues/5833 has been closed ------------- Joseph Magen https://github.com/theforeman/foreman/pull/1466 ------------- Joseph Magen Applied in changeset commit:c08d8dbd8895319ac536547572536471da43df7f.
New suggestion is: To start collecting trend data, set a cron job to execute foreman-rake trends:counter every Puppet Interval (30 minutes) *** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Verified in RHEL6/RHEL7 * candlepin-0.9.32-1.el7.noarch * candlepin-common-1.0.8-1.el7.noarch * candlepin-selinux-0.9.32-1.el7.noarch * candlepin-tomcat-0.9.32-1.el7.noarch * elasticsearch-0.90.10-7.el7.noarch * foreman-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * foreman-compute-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * foreman-gce-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * foreman-libvirt-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * foreman-ovirt-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * foreman-postgresql-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * foreman-proxy-1.7.0-0.develop.201410081229git52f0bac.el7.noarch * foreman-release-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el7.noarch * foreman-vmware-1.7.0-0.develop.201410091913git35b6fb9.el7.noarch * katello-2.1.0-1.201410091752gitc9c45c1.el7.noarch * katello-certs-tools-2.0.1-1.el7.noarch * katello-default-ca-1.0-1.noarch * katello-installer-2.1.0-1.201410021645git304e036.el7.noarch * katello-repos-2.1.1-1.el7.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.39-3.el7.x86_64 * pulp-docker-plugins-0.2.1-0.2.beta.el7.noarch * pulp-katello-0.3-3.el7.noarch * pulp-nodes-common-2.5.0-0.7.beta.el7.noarch * pulp-nodes-parent-2.5.0-0.7.beta.el7.noarch * pulp-puppet-plugins-2.5.0-0.7.beta.el7.noarch * pulp-puppet-tools-2.5.0-0.7.beta.el7.noarch * pulp-rpm-plugins-2.5.0-0.7.beta.el7.noarch * pulp-selinux-2.5.0-0.7.beta.el7.noarch * pulp-server-2.5.0-0.7.beta.el7.noarch * python-ldap-2.4.6-6.el7.x86_64 * ruby193-rubygem-ldap_fluff-0.3.1-1.el7.noarch * ruby193-rubygem-net-ldap-0.3.1-2.el7.noarch * ruby193-rubygem-runcible-1.2.0-1.el7.noarch * rubygem-hammer_cli-0.1.3-1.201409240954gitf3c47c7.el7.noarch * rubygem-hammer_cli_foreman-0.1.3-1.201409191432gitc38f9c8.el7.noarch * rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch * rubygem-hammer_cli_import-0.10.4-1.el7.noarch * rubygem-hammer_cli_katello-0.0.6-1.201410091836gitf7ca881.git.0.4d3b99d.el7.noarch
This bug is slated to be released with Satellite 6.1.
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-2015:1592