Bug 2274152
Summary: | Cannot perform an incremental syncable export after doing a full importable Library export - RHEL9 Satellite 6.16 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Giovanni Formisano <gformisa> |
Component: | Inter Satellite Sync | Assignee: | Chris Roberts <chrobert> |
Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.16.0 | CC: | ahumbe, chrobert, dalley, jlenz, ofedoren, rlavi |
Target Milestone: | stream | Keywords: | MigratedToJIRA, Regression, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://projects.theforeman.org/issues/37381 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-06 17:28:02 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
Giovanni Formisano
2024-04-09 12:35:51 UTC
Hello Team, I am not expert about Katello but doing troubleshooting I would like to share my finding, maybe can help. Reading the production.log I have seen this call: ============================ 2024-04-09T14:22:00 [I|bac|f2ed5aee] Task {label: , execution_plan_id: 5cba365c-30db-4a51-8b90-e3aac884841e} state changed: pending 2024-04-09T14:22:00 [I|bac|f2ed5aee] Task {label: Actions::Pulp3::Orchestration::ContentViewVersion::ExportRepository, id: 95fba8f1-1465-4431-a13e-c5c5cbf93c72, execution_plan_id: 5cba365c-30db-4a51-8b90-e3aac884841e} state changed: planning 2024-04-09T14:22:00 [E|bac|f2ed5aee] wrong number of arguments (given 2, expected 1) (ArgumentError) f2ed5aee | /usr/share/gems/gems/katello-4.13.0.pre.master/app/lib/actions/pulp3/orchestration/content_view_version/export_repository.rb:6:in `plan' ============================ Checking inside call I though that there is something in this rb file /usr/share/gems/gems/katello-4.13.0.pre.master/app/controllers/katello/api/v2/exports_controller.rb And here my assumption, I guess is called this function: ==================================== def find_exportable_repository @repository = Repository.find_by_id(params[:id]) if @repository.blank? throw_resource_not_found(name: 'repository', id: params[:id]) end unless @repository.organization.can_export_content? throw_resource_not_found(name: 'organization', id: @repository.organization.id) end end ==================================== But the Repository.find needs 1 parameter. Looks like satellite try to pass <id> and <execution_plan_id> If I am right seems is not correct since that in the function is specify only the <:id> This is why I receive ==================== wrong number of arguments (given 2, expected 1) (ArgumentError) =================== I hope this comment can be helpful. For the maintainer: this looks like an overlook of https://github.com/Katello/katello/pull/10885. The actual issue seems to be in https://github.com/Katello/katello/blob/master/app/lib/actions/pulp3/orchestration/content_view_version/export_repository.rb#L6-L9, which should be fixed by extracting of keyword arguments into a hash similarly to https://github.com/Katello/katello/pull/10885/files#diff-b15de70362926747b6c8b3158a9c435bf00bb65745ee9a256552cac5a4d6175f. Connecting redmine issue https://projects.theforeman.org/issues/37381 from this bug This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |