Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
foreman-debug tarball contains a `pulp_running_tasks` file, however it only contains the following:
<pre>
COMMAND> mongo pulp_database /var/tmp/foreman-debug-auxtmp-3lIgY/tmp.k3Z4fmNeaD/pulp_running_tasks.js
/usr/sbin/foreman-debug: line 79: mongo: command not found
</pre>
This was working fine in 6.4.0-1 and has failed in 6.4.0-4.
Version-Release number of selected component (if applicable):
satellite 6.4.0-4
Steps to Reproduce:
1. get satellite 6.4.0 installed per installation instructions
2. generate a foreman-debug tarball using foreman-debug utility
3. check the pulp_running_tasks file from generated tarball
Actual results:
mongo: command not found
Expected results:
the mongo client is present and the file properly shows the running pulp tasks.
Got the same error mentioned above. Ran the following commands on a Satellite 6.4 machine:
# foreman-debug
# tar xf /var/tmp/foreman-debug-qqurl.tar.xz
# cat foreman-debug-qqurl/pulp-running_tasks
OMMAND> mongo pulp_database /var/tmp/foreman-debug-auxtmp-n2Kbn/tmp.gxjuzj8dnm/pulp_running_tasks.js
/usr/sbin/foreman-debug: line 79: mongo: command not found
With https://github.com/Katello/katello-installer/pull/658
I am able to see that MongoDB can be called:
[root@sat-6-4-qa-rhel7 foreman-debug-G90DT]# cat pulp-running_tasks
COMMAND> mongo pulp_database /var/tmp/foreman-debug-auxtmp-gIYdP/tmp.sIlz2MoP4J/pulp_running_tasks.js
MongoDB shell version v3.4.9
connecting to: mongodb://127.0.0.1:27017/pulp_database
MongoDB server version: 3.4.9
VERIFIED
on sat6.4.0-12
the mongo command cna now be successfully called again:
<pre>
$ cat ~/work/analysis/6.4.0-12/t3/foreman-debug/pulp-running_tasks
COMMAND> mongo pulp_database /var/tmp/foreman-debug-auxtmp-010bE/tmp.A1dKYv1eFR/pulp_running_tasks.js
MongoDB shell version v3.4.9
connecting to: mongodb://127.0.0.1:27017/pulp_database
MongoDB server version: 3.4.9
{
...
</pre>
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:2927