Bug 1994212
Summary: | Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Ganesh Payelkar <gpayelka> | |
Component: | Repositories | Assignee: | Justin Sherrill <jsherril> | |
Status: | CLOSED ERRATA | QA Contact: | Sam Bible <sbible> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 6.10.0 | CC: | ahumbe, jbhatia, jkrajice, jsherril, pcreech, sbible | |
Target Milestone: | 6.11.0 | Keywords: | EasyFix, Triaged | |
Target Release: | Unused | |||
Hardware: | x86_64 | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 2030445 (view as bug list) | Environment: | ||
Last Closed: | 2022-07-05 14:29:34 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
Ganesh Payelkar
2021-08-17 03:53:30 UTC
Is this for specific repositories? Is this only for a particular manifest? Do the repositories get enabled despite the error message? Thanks! This is not specific to any repository set, when we try to expand the repository set then we see the below messages in the logs. 2021-08-19T12:29:36 [I|app|09c02915] Started GET "/katello/api/v2/products/36/repository_sets/4117/available_repositories" for 10.74.9.96 at 2021-08-19 12:29:36 -0400 2021-08-19T12:29:36 [I|app|09c02915] Processing by Katello::Api::V2::RepositorySetsController#available_repositories as JSON 2021-08-19T12:29:36 [I|app|09c02915] Parameters: {"api_version"=>"v2", "product_id"=>"36", "id"=>"4117"} 2021-08-19T12:29:36 [E|app|16c8c4e0] Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass 2021-08-19T12:29:36 [E|app|16c8c4e0] Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass 2021-08-19T12:29:36 [E|app|16c8c4e0] Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass 2021-08-19T12:29:36 [E|app|16c8c4e0] Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass 2021-08-19T12:29:36 [E|app|16c8c4e0] Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass 2021-08-19T12:29:36 [E|app|16c8c4e0] Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass 2021-08-19T12:29:36 [E|app|16c8c4e0] Failed at scanning for repository: undefined method `resolve_substitutions' for nil:NilClass I'm suggesting we move this off of 6.10 for these reasons: 1. Its easily reproducible on 6.8 and 6.9 (not a regression) 2. This only adds some errors to the logs, scanning the repository causes no issues 3. It only happens with certain content sets, such as 'rhel-7-server-extras-rpms' Steps to reproduce: 1. import a manifest 2. go to the RH repos page, scan repos for the 'rhel-7-server-extras-rpms' content set 3. Notice you see no errors, and see the repository as expected. You can enable it with no issue 4. Check /var/log/foreman/production.log for errors, notice the errors mentioned here. Thanks for the reproducer details Ganesh! Created redmine issue https://projects.theforeman.org/issues/33383 from this bug Upstream bug assigned to jsherril Upstream bug assigned to jsherril Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33383 has been resolved. Verified on: 6.11 - 18 Steps to reproduce: 1. import a manifest 2. go to the RH repos page, scan repos for the 'rhel-7-server-extras-rpms' content set 3. Notice you see no errors, and see the repository as expected. 4. Check /var/log/foreman/production.log for errors. Expected Results: No errors appearing in the production log Actual Results: No errors in the production log. 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.11 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-2022:5498 |