Description of problem: On the "Select Product(s) to Deploy" page when creating a new deployment, clicking the "Download these requirements" link gives a File not found for https://<hostname>/r/QCI_Requirements.txt In /var/log/foreman/production.log: 2016-05-09 15:03:25 [F] ActionController::RoutingError (No route matches [GET] "/r/QCI_Requirements.txt"): /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request' /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request' /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop' /usr/share/gems/gems/passenger-4.0.18/lib/phusion_passenger/request_handler.rb:441:in `block (3 levels) in start_threads' This happens regardless of which products are selected. Version-Release number of selected component (if applicable): QCI-1.1-RHEL-7-20160428.t.0 How reproducible: 100% Steps to Reproduce: 1.) Create a new deployment. 2.) Click the "Download these requirements" link on the product selection page. 3.) Get a "File not found" error. Actual results: File not found error. Expected results: No error, successful download of requirements. Additional info:
PR: https://github.com/fusor/fusor/pull/970
Addressed in ISO Set: QCI-1.2-RHEL-7-20160623.t.0-QCI-x86_64-dvd1.iso QCIOOO-8.0-RHEL-7-20160623.t.0-QCIOOO-x86_64-dvd1.iso
The link is still broken on QCI-1.2-RHEL-7-20160627.t.0.
We've confirmed this is an issue in the iso environment and not in the dev environment -- it's related to how the project is structured to serve static after fusor_ui has been packaged with foreman in a production setting. Should have a fix in a compose shortly.
This should be fixed as of compose QCI-1.2-RHEL-7-20160711.t.1-QCI-x86_64-dvd1.iso Relevant PRs: https://github.com/fusor/fusor/pull/1017 https://github.com/fusor/fusor/pull/1024
QCI-1.2-RHEL-7-20160718.t.0
Verified on QCI-1.2-RHEL-7-20160718.t.0.
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, 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/RHEA-2016:1862