Bug 1997027

Summary: For RHEL6 hosts, output of "/api/hosts?full_result=true" shows null value for the 'uptime_seconds' field
Product: Red Hat Satellite Reporter: Prakash Ghadge <pghadge>
Component: HostsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9.0CC: apatel, aruzicka, inecas, ramsingh
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-14 09:02:16 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 Prakash Ghadge 2021-08-24 09:11:54 UTC 
Description of problem:
> For RHEL6 hosts, output of "/api/hosts?full_result=true"  shows null value for the 'uptime_seconds' field

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

How reproducible:
> Always

Steps to Reproduce:
1. Register a RHEL 6 host to satellite or use an existing RHEL 6 host.
2. Run the following command.

# curl -s -k -u admin -X GET 'https://localhost/api/hosts/<host id>?full_result=true' |json_reformat | grep -i uptime

Actual results:

For RHEL6 System -
# curl -s -k -u admin -X GET 'https://localhost/api/hosts/7?full_result=true' |json_reformat | grep -i uptime
    "uptime_seconds": null,

For RHEL 7 system -
# curl -s -k -u admin -X GET 'https://localhost/api/hosts/4?full_result=true' |json_reformat | grep -i uptime
    "uptime_seconds": 1222722,


Expected results:

For RHEL6 System -
# curl -s -k -u admin -X GET 'https://localhost/api/hosts/7?full_result=true' |json_reformat | grep -i uptime
    "uptime_seconds": <Uptime value in seconds>,

Additional info:
Comment 1 Brad Buckingham 2021-09-02 10:21:23 UTC 
*** Bug 1998719 has been marked as a duplicate of this bug. ***
Comment 4 Adam Ruzicka 2023-08-14 09:02:16 UTC 
Closing this bug out since we do not believe it will be fixed in the next multiple releases, chances are that RHEL6 will even go EOL before we get to this. If this is a large impact on you, please feel free to re-open.