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 1861344

Summary:	Scenarios present inside satellite-maintain content should be restricted
Product:	Red Hat Satellite	Reporter:	anerurka
Component:	Satellite Maintain	Assignee:	Kavita <kgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Jameer Pathan <jpathan>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.8.0	CC:	apatel, gtalreja, kgaikwad, mawerner, pcreech
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	rubygem-foreman_maintain-0.6.9	Doc Type:	Known Issue
Doc Text:	Scenarios present inside satellite-maintain content should be restricted	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:38:46 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 anerurka 2020-07-28 10:54:07 UTC

Description of problem:

Scenarios present inside satellite-maintain content should be restricted  

Version-Release number of selected component (if applicable):

Satellite 6.8 Beta
rubygem-foreman_maintain-0.6.8-1.el7sat.noarch

How reproducible:

# satellite-maintain content switchover
Running Switch support for certain content from Pulp 2 to Pulp 3
================================================================================
Switch support for certain content from Pulp 2 to Pulp 3: 
Performing final content migration before switching content           [FAIL]
Failed executing foreman-rake katello:pulp3_migration, exit status 127:
 sh: foreman-rake: command not found
--------------------------------------------------------------------------------
Scenario [Switch support for certain content from Pulp 2 to Pulp 3] failed.

The following steps ended up in failing state:

  [content-switchover]

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


Actual results:

Scenario to switch content from Pulp 2 to Pulp 3 is attempted.


Expected results:

Red Hat Satellite 6.x, still has Pulp-2, so "# satellite-maintain content" should be hide or scenarios present should not be executed.

Comment 1 Kavita 2020-07-28 12:28:52 UTC

Hello Ameya,

Pull-request already opened and currently under review. 
With this change, it won't run any steps inside but those sub-commands will be visible.

https://github.com/theforeman/foreman_maintain/pull/376

Linking the upstream issue to BZ for further tracking.

Thanks for reporting this.
- Kavita

Comment 2 Bryan Kearney 2020-07-29 12:04:00 UTC

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

Comment 3 Jameer Pathan 2020-09-07 10:45:02 UTC

Verified

verified with:
- Satellite 6.8.0 snap 14
- rubygem-foreman_maintain-0.6.9-1.el7sat.noarch

Test steps:
1. foreman-maintain content prepare
2. foreman-maintain content switchover

Observation:
- Scenario present in prepare and switchover command are not executed.

Comment 6 errata-xmlrpc 2020-10-27 12:38:46 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 (Satellite 6.8 Satellite Maintenance 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/RHBA-2020:4365