Bug 1583729

Summary: All API GET calls to '/foreman_virt_who_configure/api/configs' fail
Product: Red Hat Satellite Reporter: Harshad More <hmore>
Component: Virt-who Configure PluginAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Chris Brown <dbrownjr>
Severity: medium Docs Contact: satellite-doc-list
Priority: unspecified    
Version: 6.3.1CC: gerben, hmore, jhutar, mhulan, rankumar, roarora, tstrachota, wpinheir
Target Milestone: 6.4.0Keywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: foreman_virt_who_configure-0.2.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-16 19:27: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:
Attachments:
Description Flags
https://<satellite-server>/foreman_virt_who_configure/api/configs none

Description Harshad More 2018-05-29 14:40:58 UTC 
Description of problem:

Using API trying to get virt-who configuration file fails


How reproducible: Always

Steps to Reproduce:
https://<satellite-server>/foreman_virt_who_configure/api/configs

Actual results:

The page renders as:

The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.

Expected results:

The page should be able to access

Additional info:

The foreman production log shows the following:

ActionController::RoutingError (No route matches [GET] "/foreman_vi
rt_who_configure/api/configs")
-----------

workaround:

The API worked after appending v2 in the API url 

https://<satellite-server>/foreman_virt_who_configure/api/v2/configs
Comment 1 Marek Hulan 2018-05-29 15:37:06 UTC 
Just curious, where did you get the URL? I was under impressions apidoc mentions https://<satellite-server>/foreman_virt_who_configure/api/v2/configs
Comment 2 Marek Hulan 2018-05-30 09:32:33 UTC 
Ah I see the wrong url is suggested in /apidoc. The fix will be in apidoc so that it suggests /foreman_virt_who_configure/api/v2/configs so your workaround is acutually right solution.
Comment 3 Harshad More 2018-05-30 11:26:58 UTC 
I guess you got the fix.
Comment 6 Chris Brown 2018-06-18 15:23:15 UTC 
Created attachment 1452667 [details]
https://<satellite-server>/foreman_virt_who_configure/api/configs

Page exists and I was able to access the website. Screenshot attached
Comment 8 Bryan Kearney 2018-10-16 19:27:02 UTC 
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/RHSA-2018:2927