Bug 1363804

Summary: Candlepin version being replaced with katello version in API response
Product: Red Hat Satellite Reporter: Barnaby Court <bcourt>
Component: Subscription ManagementAssignee: Justin Sherrill <jsherril>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2.0CC: bbuckingham, bcourt, bkearney, jcallaha
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-04 17:42:45 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 Barnaby Court 2016-08-03 15:34:03 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
every time

Steps to Reproduce:
Use curl to query the Candlepin status API directly and via the API. From a consumer that is registered to the Satellite 6.2.0 GA server this looks as follows:
[root@rhel6 ~]# curl -s --cert /etc/pki/consumer/cert.pem  --key /etc/pki/consumer/key.pem  -k -X GET https://sat-rhel7.example.com/rhsm/status -H "Content-Type:application/json" | python -m json.tool
{
    "managerCapabilities": [
        "cores", 
        "ram", 
        "instance_multiplier", 
        "derived_product", 
        "cert_v3", 
        "guest_limit", 
        "vcpu", 
        "storage_band"
    ], 
    "result": true, 
    "rulesSource": "DEFAULT", 
    "rulesVersion": "5.15.2", 
    "standalone": true, 
    "timeUTC": "2016-08-03T15:23:38.454Z", 
    "version": "3.0.0.68"
}
[root@rhel6 ~]# curl -s --cert /etc/pki/consumer/cert.pem  --key /etc/pki/consumer/key.pem  -k -X GET https://sat-rhel7.example.com:8443/candlepin/status -H "Content-Type:application/json" | python -m json.tool
{
    "managerCapabilities": [
        "cores", 
        "ram", 
        "instance_multiplier", 
        "derived_product", 
        "cert_v3", 
        "guest_limit", 
        "vcpu", 
        "storage_band"
    ], 
    "release": "1", 
    "result": true, 
    "rulesSource": "DEFAULT", 
    "rulesVersion": "5.15.2", 
    "standalone": true, 
    "timeUTC": "2016-08-03T15:24:06.137+0000", 
    "version": "0.9.54.7"
}
Actual results:
version field is "3.0.0.68"

Expected results:
version field should be "0.9.54.7"

Additional info:

Comment 1 Brad Buckingham 2016-08-05 15:54:23 UTC
Hi Barnaby, is the incorrect version causing any troubles?  (e.g. is it currently being used by other processes?)

Comment 2 Barnaby Court 2016-08-05 17:01:18 UTC
The biggest issue is that because the 'release' field is being dropped entirely older versions of subscription-manager show a stack trace in the logs. Newer versions should be ok, but will present bad information which will lead to confusion for anyone debugging a problem.

Comment 6 Brad Buckingham 2017-10-04 19:41:01 UTC
Created redmine issue http://projects.theforeman.org/issues/21199 from this bug

Comment 7 Satellite Program 2017-10-12 16:02:35 UTC
Upstream bug assigned to jsherril

Comment 8 Bryan Kearney 2018-09-04 17:42:45 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.