Bug 1997027 - For RHEL6 hosts, output of "/api/hosts?full_result=true" shows null value for the 'uptime_seconds' field
Summary: For RHEL6 hosts, output of "/api/hosts?full_result=true" shows null value fo...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hosts
Version: 6.9.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 1998719 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-24 09:11 UTC by Prakash Ghadge
Modified: 2023-08-14 09:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-14 09:02:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.