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:
When I run `foreman-rake katello:receptor:extract_orgs` command, the following is the result:
```
# foreman-rake katello:receptor:extract_orgs OUTPUT_FILE=/tmp/out42.txt
disabled
Wrote results to /tmp/out42.txt. Please delete it when finished.
```
I don't know what 'disabled' means here and where it comes from but I think it shouldn't be there. This doesn't happen for other foreman-rake commands I tried, e.g. `console` or `katello:upgrade_check`.

Version-Release number of selected component (if applicable):
Reproduced on Sat 6.9 snap 12

How reproducible:
Deterministic

Steps to Reproduce:
1.run `foreman-rake katello:receptor:extract_orgs OUTPUT_FILE=/dev/null`

Actual results:
'disabled' in output, meaningless

Expected results:
The same output without 'disabled'

I guess this is completely harmless right? I don't think anyone is expected to run this rake task manually. But it's definitely a valid report, the output does not make sense to the user.

Exactly.
(Maybe it would be worth it to find the cause to make sure nothing more important is broken.)

Fix for this is tiny and should be safe for 6.9, otoh it has practically no impact.

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31887 has been resolved.

Verified with Sat 6.9 snap 16.

# foreman-rake katello:receptor:extract_orgs OUTPUT_FILE=/tmp/res
Wrote results to /tmp/res. Please delete it when finished.
# cat /tmp/res
[correct output]

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 (Moderate: Satellite 6.9 Release), 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-2021:1313