Bug 658367 - [RFE] Provide channel last_modified value via api
[RFE] Provide channel last_modified value via api
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API (Show other bugs)
Unspecified Unspecified
low Severity medium
: ---
: ---
Assigned To: Tomas Lestach
Šimon Lukašík
: FutureFeature
Depends On:
Blocks: sat54-errata
  Show dependency treegraph
Reported: 2010-11-30 02:00 EST by Šimon Lukašík
Modified: 2011-01-18 07:16 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
This update adds an API call that provides access to the channel last_modified value. This helps users to identify whether the channel repodata are stale or not.
Story Points: ---
Clone Of:
Last Closed: 2010-12-16 10:45:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Šimon Lukašík 2010-11-30 02:00:01 EST
Description of problem:
Provide channel last_modified value via satellite frontend api
call. It may help users f.e. to identify whether are the channel
repodata stale or not.

This issue has been already resolved upstream.
spacewalk.git: a4e5de76986b6b2a613bea8bc3dad3e55332c1dc
Comment 1 Tomas Lestach 2010-11-30 07:34:34 EST
Moving to MODIFIED since the commit is already in #Description.
Comment 4 Šimon Lukašík 2010-12-07 05:38:19 EST
Changing to VERIFIED:

Testing procedure:
Automated script
  Compare values against getChannelLastBuildById
  Before and after the sync.

Verified against:

Thanks for this, Tomas!
Comment 6 errata-xmlrpc 2010-12-16 10:45:52 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Comment 7 Jaromir Hradilek 2010-12-16 11:36:31 EST
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    New Contents:
This update adds an API call that provides access to the channel last_modified value. This helps users to identify whether the channel repodata are stale or not.
Comment 8 Stephan Dühr 2011-01-18 03:07:33 EST
The quality of this erratum should be enhanced, because:
- it mentions an added API call but not the name of the new API call
- it does not mention, that the existing API call channel.software.getDetails was changed and that it now returns an last_modified also
- at least the API documentation should mention this
Comment 10 Tomas Lestach 2011-01-18 03:37:44 EST
Hey Stephan, you're right. The erratum text says incorrectly there's a new API call, instead of just enhancing the extended channel.software.getDetails. Sorry for confusion.
But API documentation look good to me.
Return struct of getDetails contains:
 dateTime.iso8601 "last_modified"
Just check /rhn/apidoc/handlers/ChannelSoftwareHandler.jsp#getDetails on your updated satellite.
Comment 11 Stephan Dühr 2011-01-18 06:30:22 EST
Thanks, good to know. I didn't think that the local documentation is more recent.
Then it's only missing in the public docs
Comment 12 Tomas Lestach 2011-01-18 07:16:32 EST
API Documentation available at rhn/apidoc/index.jsp on your satellite always reflects your available API. (It basically changes with every spacewalk-java erratum.)

Public documentation for RHN Satellite 5.4 available on http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.4/html/API_Overview/index.html describes API of released RHN Satellite 5.4 (so, no errata changes are reflected).

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