Hide Forgot
Description of problem: After successfully provisioning a VM and viewing the details of the request the # after "Provisioned VMs" is a link which fails with a "No route matches" error. Version-Release number of selected component (if applicable): 5.5 How reproducible: Always Steps to Reproduce: 1. Successfully provision a VM 2. Click on request Under Services -> Request to view request details 3. Click on number displayed after "Provisioned VMs" (See attached screenshot) Actual results: Error screen is displayed with: No route matches {:action=>"show/837", :controller=>"miq_request", :id=>"837", :sort_choice=>"Status"} [miq_request/show] Expected results: See list of provisioned VMs
Created attachment 1135416 [details] Provision Request details screen
Created attachment 1135417 [details] Error screenshot
Milan, Can you look into this one, looks like action is incorrect in the transaction has id included in it, causing routing error. Let me know if you have questions. Thanks, ~Harpreet
https://github.com/ManageIQ/manageiq/pull/7875
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/80fb6f247aa2c71221f24a126e6565d580802ee0 commit 80fb6f247aa2c71221f24a126e6565d580802ee0 Author: Milan Zazrivec <mzazrivec> AuthorDate: Mon Apr 11 20:27:09 2016 +0200 Commit: Milan Zazrivec <mzazrivec> CommitDate: Mon Apr 11 20:30:05 2016 +0200 Fix action_url for gtl view showing provisioned vms This is to fix the following error thrown by link_to(): No route matches {:action=>"show/10000000000272", :controller=>"miq_request", :id=>"10000000000272", :sort_choice=>"Status"} https://bugzilla.redhat.com/show_bug.cgi?id=1317074 app/views/miq_request/_provisions.html.haml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Fixed. Verified in 5.6.0.4-beta2.3.20160421172650_719e256
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/RHBA-2016:1348