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.

Bug 1995421

Summary: The foreman-maintain should only ask to run failed step with whitelist option if step has whitelist option
Product: Red Hat Satellite Reporter: Shekhar Raut <sraut>
Component: Satellite MaintainAssignee: Amit Upadhye <aupadhye>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: ahumbe, apatel, aupadhye, ehelms, kgaikwad, myoder, wclark
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-10 00:43:19 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 Shekhar Raut 2021-08-19 05:06:46 UTC
Description of problem:

While performing Satellite upgrade 6.9 to 6.10, tried to perform "Content Migration to Pulp3".

Command suggested to use "use --whitelist="content-prepare" option but using the same option, command is failing with error, "ERROR: Unrecognised option '--whitelist'"

You can find full details in "Steps to Reproduce:"

Version-Release number of selected component (if applicable):
6.9, "Content Migration to Pulp3" [while performing pre-upgrade task for 6.10]

How reproducible:

Steps to Reproduce:

On Satellite 6.9, start performing "Content Migration to Pulp3"

1. # satellite-maintain content migration-stats

2. # satellite-maintain prep-6.10-upgrade

3. # satellite-maintain content prepare

   Above command failed with an error:

~~~
   Failed executing foreman-rake katello:pulp3_migration, exit status 1
--------------------------------------------------------------------------------
Scenario [Prepare content for Pulp 3] failed.

The following steps ended up in failing state:

  [content-prepare]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-prepare"
~~~

4. Using this option failing with another error:

~~~
[root@satellite ~]# satellite-maintain content prepare --whitelist="content-prepare"
ERROR: Unrecognised option '--whitelist'

See: 'satellite-maintain content prepare --help'
~~~

- Please see the full command output in next comment

Actual results:

~~~
[root@satellite ~]# satellite-maintain content prepare --whitelist="content-prepare"
ERROR: Unrecognised option '--whitelist'

See: 'satellite-maintain content prepare --help'
~~~

- Please see the full command output in next comment

Expected results:

If the option is not available then it should not suggest the same in the output.

Comment 1 Shekhar Raut 2021-08-19 05:07:59 UTC
Full Command Output

~~~

Prepare content for Pulp 3: 
Checking for valid Katello configuraton.
Starting task.
2021-08-19 00:39:54 -0400: Pre-migrating Pulp 2 rpm content (detail info) 38000/46158Migration failed, You will want to investigate: https://vm249-161.gsslab.pnq2.redhat.com/foreman_tasks/tasks/481ecb32-1606-42b7-909d-a70e63b3c501
rake aborted!
ForemanTasks::TaskError: Task 481ecb32-1606-42b7-909d-a70e63b3c501: Katello::Errors::Pulp3Error: out of memory
DETAIL:  Failed on request of size 268435456 in memory context "ErrorContext".
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.33/lib/katello/tasks/pulp3_migration.rake:35:in `block (2 levels) in <top (required)>'
/opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
Tasks: TOP => katello:pulp3_migration
(See full trace by running task with --trace)
                                                                      [FAIL]
Failed executing foreman-rake katello:pulp3_migration, exit status 1
--------------------------------------------------------------------------------
Scenario [Prepare content for Pulp 3] failed.

The following steps ended up in failing state:

  [content-prepare]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-prepare"


[root@satellite ~]# satellite-maintain content prepare --whitelist="content-prepare"
ERROR: Unrecognised option '--whitelist'

See: 'satellite-maintain content prepare --help'
Enabling the following service(s):
pulpcore-api, pulpcore-content, pulpcore-resource-manager, pulpcore-worker@1, pulpcore-worker@2, pulpcore-worker@3, pulpcore-worker@4
/ All services enabled                                                [OK]      
--------------------------------------------------------------------------------
Start applicable services: 

Starting the following service(s):
pulpcore-api, pulpcore-content, pulpcore-resource-manager, pulpcore-worker@1, pulpcore-worker@2, pulpcore-worker@3, pulpcore-worker@4
\ All services started                                                [OK]      
--------------------------------------------------------------------------------
Prepare content for Pulp 3: 
Checking for valid Katello configuraton.
Starting task.
2021-08-19 00:39:54 -0400: Pre-migrating Pulp 2 rpm content (detail info) 38000/46158Migration failed, You will want to investigate: https://vm249-161.gsslab.pnq2.redhat.com/foreman_tasks/tasks/481ecb32-1606-42b7-909d-a70e63b3c501
rake aborted!
ForemanTasks::TaskError: Task 481ecb32-1606-42b7-909d-a70e63b3c501: Katello::Errors::Pulp3Error: out of memory
DETAIL:  Failed on request of size 268435456 in memory context "ErrorContext".
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.33/lib/katello/tasks/pulp3_migration.rake:35:in `block (2 levels) in <top (required)>'
/opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
Tasks: TOP => katello:pulp3_migration
(See full trace by running task with --trace)
                                                                      [FAIL]
Failed executing foreman-rake katello:pulp3_migration, exit status 1
--------------------------------------------------------------------------------
Scenario [Prepare content for Pulp 3] failed.

The following steps ended up in failing state:

  [content-prepare]

Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="content-prepare"


[root@satellite ~]# satellite-maintain content prepare --whitelist="content-prepare"
ERROR: Unrecognised option '--whitelist'

See: 'satellite-maintain content prepare --help'

~~~

Comment 2 Amit Upadhye 2021-08-25 10:44:04 UTC
Hello Shekhar,

The content prepare does not have whitelist option as upgrade should not happen without it. The problem is whitelist message there for a step which does not support the whitelist. The foreman-maintain has scenarios and then procedures are run as a step in scenario. Each scenario can have one or more than one step and hence its not possible to remove whitelist option from output for all the failed steps as some of them can have that.

Considering this I have changed the summary of bz to reflect what will be implemented for handling this situation.

To solve actual problem you will need to allocate more memory to the system.
_
Amit Upadhye.

Comment 5 Amit Upadhye 2022-05-05 14:10:05 UTC
*** Bug 1907710 has been marked as a duplicate of this bug. ***

Comment 8 Brad Buckingham 2023-09-01 21:10:52 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 10 Brad Buckingham 2023-10-04 20:47:42 UTC
Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.

Comment 12 Eric Helms 2024-04-10 00:43:19 UTC
As this issue is specific to the Pulp 2 to Pulp 3 migration which happened in Satellite 6.10 which is no longer a supported version, we are closing the issue.