Bug 2127520
Summary: | Inventory sync would return "nothing to sync" if "All organizations" is selected. | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sahil Bhasin <sabhasin> |
Component: | RH Cloud | Assignee: | Shimon Shtein <sshtein> |
Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.11.2 | CC: | aruzicka, dsinglet, peter.vreman |
Target Milestone: | Unspecified | Keywords: | FutureFeature, MigratedToJIRA, Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-06-06 12:34:28 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
Sahil Bhasin
2022-09-16 16:33:47 UTC
The behavior you are describing is actually an incorrect message for this specific edge case. Theoretically the action can be performed only in the context of a specific org (as opposed to "Any org" selected in this case). In more techincal terms start_inventory_sync from https://github.com/theforeman/foreman_rh_cloud/blob/731a755c43691d9b61c45c22b94734c8b7e8ec53/app/controllers/concerns/inventory_upload/task_actions.rb#L13 is called with selected_org=nil and this will not return any hosts, causing the "Nothing to sync" message. I suppose we should either support "All orgs" (and then filter out those without manifest) or put a better message to indicate that "All orgs" are not supported. Renaming the issue to indicate that this is a bug. We need to either throw a meaningful message or run the sync task for each organization that the user can see. 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. |