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 2080348 - Repository sync jobs are failing with the Exception "NoMethodError undefined method `repository_href' for nil:NilClass" post upgrade to satellite version 6.10
Summary: Repository sync jobs are failing with the Exception "NoMethodError undefine...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.10.6
Assignee: Amit Upadhye
QA Contact: Gaurav Talreja
URL:
Whiteboard:
: 1995230 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-29 13:44 UTC by Brad Buckingham
Modified: 2022-10-19 17:29 UTC (History)
17 users (show)

Fixed In Version: rubygem-foreman_maintain-0.8.30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2024553
Environment:
Last Closed: 2022-05-31 16:37:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34706 0 Normal Closed Have an option to mark procedure or check non_whitelistable or non_skippable 2022-04-29 13:44:30 UTC
Red Hat Knowledge Base (Solution) 6932991 0 None None None 2022-04-29 13:44:30 UTC
Red Hat Product Errata RHBA-2022:4851 0 None None None 2022-05-31 16:37:29 UTC

Comment 2 Gaurav Talreja 2022-05-18 20:10:21 UTC 
Verified.
Tested on Satellite 6.9.9 with rubygem-foreman_maintain-0.8.30-1.el7sat.noarch (From 6.10.6 Snap 2.0)

Steps:
1. Prepare Sat 6.9 and sync some content with the immediate download policy
2. Make content migration to fail by 'corrupt' some data   
    # echo "somedata" > /var/lib/pulp/content/path/to/package.rpm
3. Upgrade to 6.10

Observations:
1. Upgrade to 6.10 fails because content-switchover is supposed to fail here due to corrupt content, but a fix in foreman_maintain prevents the possibility of whitelisting this check, along with content-prepare (check below example) and in the absence of whitelist option user can't proceed for an upgrade with skipping a failed step.
--------------------------------------------------------------------------------
Scenario [Migration scripts to Satellite 6.10] failed.

The following steps ended up in failing state:

  [content-switchover]


2. And for other checks in case of a fail state f-m asks a user the following message,
--------------------------------------------------------------------------------
Scenario [ForemanMaintain::Scenario::FilteredScenario] failed.

The following steps ended up in failing state:

  [validate-yum-config]

Resolve the failed steps and rerun the command.

If the situation persists and, you are unclear what to do next,
contact Red Hat Technical Support.

In case the failures are false positives, use
--whitelist="validate-yum-config"
Comment 5 errata-xmlrpc 2022-05-31 16:37:24 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 Maintenance 6.10.6 Async Bug Fix Update), 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-2022:4851
Comment 7 Daniel Alley 2022-10-19 17:29:13 UTC 
*** Bug 1995230 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.