Bug 1927842

Summary:	Bogus output of `foreman-rake katello:receptor:extract_orgs`
Product:	Red Hat Satellite	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	RH Cloud - Cloud Connector	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.9.0	CC:	aruzicka, zhunting
Target Milestone:	6.9.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.18.1.10-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-04-21 13:10:31 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 Lukáš Hellebrandt 2021-02-11 16:29:25 UTC

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'

Comment 1 Marek Hulan 2021-02-15 15:18:25 UTC

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.

Comment 2 Lukáš Hellebrandt 2021-02-15 15:52:53 UTC

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

Comment 3 Adam Ruzicka 2021-02-16 10:57:14 UTC

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

Comment 4 Bryan Kearney 2021-03-02 16:04:28 UTC

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

Comment 6 Lukáš Hellebrandt 2021-03-10 11:36:04 UTC

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]

Comment 9 errata-xmlrpc 2021-04-21 13:10:31 UTC

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