Description of problem: After generating the Inventory file, the file doesn't exist - I can't either upload it to c.r.c. or download it through WebUI. It's not present in the filesystem, either. Attempt to upload causes: """ ==> /var/log/foreman/production.log <== 2020-02-27T05:15:23 [I|app|126a16b8] Started POST "/foreman_inventory_upload/1/uploads" for 10.40.205.144 at 2020-02-27 05:15:23 -0500 2020-02-27T05:15:23 [F|app|126a16b8] 2020-02-27T05:15:23 [F|app|126a16b8] ActionController::RoutingError (No route matches [POST] "/foreman_inventory_upload/1/uploads"): 2020-02-27T05:15:23 [F|app|126a16b8] 2020-02-27T05:15:23 [F|app|126a16b8] lib/foreman/middleware/logging_context_request.rb:11:in `call' katello (3.14.0.12) lib/katello/prevent_json_parsing.rb:12:in `call' """ Attempt to download causes error in WebUI: "Path doesn't exist: /var/lib/foreman/red_hat_inventory/uploads/report_for_1.tar.gz" Version-Release number of selected component (if applicable): Sat 6.7 snap 13 How reproducible: On the same system, upload worked at least once before so I'm not sure how I caused the error. Reproducer might not work for you. Steps to Reproduce: 1. RH Inventory -> Manage -> Restart 2. After the file seems to be generated, go to Upload tab 3. Click Restart 4. Click Download Report Actual results: The file doesn't exist in the filesystem, can't be uploaded to c.r.c., can't be downloaded Expected results: Inventory file generated, uploaded to c.r.c., downloaded locally Additional info:
There is no traceback or error shown when generating.
Even though there are errors shown when uploading/downloading, the system appears in c.r.c.'s inventory after some time.
*** Bug 1817489 has been marked as a duplicate of this bug. ***
Report file can be downloaded every time. Tested on: Satellite 6.8.0 snap 5 pulp-server-2.21.2-1.el7sat.noarch satellite-6.8.0-0.4.beta.el7sat.noarch foreman-2.1.0-0.20.rc2.el7sat.noarch katello-3.16.0-0.3.rc1.el7sat.noarch tfm-rubygem-foreman_rh_cloud-2.0.7-1.el7sat.noarch
*** Bug 1862249 has been marked as a duplicate of this bug. ***
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 (Important: Satellite 6.8 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-2020:4366