Hide Forgot
Description of problem: We would like to have a CSV report about our estate. On the old Satellite this is done via "spacewalk-report inventory" and then some simple post-processing of the output. The same is not possible in Satellite 6.1 easily. There is "hammer content-report content-host-status" which is affected by the following bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1296009 https://bugzilla.redhat.com/show_bug.cgi?id=1297742 But even after fixing/workaournding these (as I tried in my local setup), the output will only contain three columns: Hostname,Status,Date This is not as detailed as the inventory report done by spacewalk. Especially it is missing the following fields: ip adress, registration time, last checkin time, list of entitelements, virtual or physical, architecture As such this is currently not useful to us. Most of the data can be fetched using the API directly, which we are going to implement as a workaround, but having it as a feature in the product would be great. Especially as it was present in Satellite 5. Version-Release number of selected component (if applicable): current 6.1.x How reproducible: always Steps to Reproduce: 1. hammer content-report content-host-status Actual results: output is missing columns Expected results: Should contain fields ip adress, registration time, last checkin time, list of entitelements, virtual or physical, architecture Additional info: bz1156582 requests other fields
API is a workaround, but much slower for this purpose, hammer would just do a single query to the underlying db.
Per 6.3 planning, moving out non acked bugs to the backlog
I have a customer looking for few features to be involved in this bug i.e listing the hostname with their last patching date. Customer is currently using satellite 6.2 and the feature of content-reports is not available in this version.
With Sat-6.2.7 custom reports can be exported that may satisfy the attached customer cases. See this comment: https://bugzilla.redhat.com/show_bug.cgi?id=1267445#c15
Hi, what is the status here? Does the comment #8 help with your use case?
(In reply to Ondřej Pražák from comment #9) > Hi, what is the status here? Does the comment #8 help with your use case? Stefan, any comments?
Closing current release based on Comment 8.