Bug 1194444 - hammer content-report CSV output of dates should be in form consumable by spreadsheet
Summary: hammer content-report CSV output of dates should be in form consumable by spr...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Adam Price
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-19 20:03 UTC by Tom McKay
Modified: 2017-02-23 20:28 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:26:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 9476 0 None None None 2016-04-22 16:40:32 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Tom McKay 2015-02-19 20:03:34 UTC
To test, try importing CSV into google docs spreadsheet and set column format to date.

Comment 1 Tom McKay 2015-02-19 20:03:35 UTC
Created from redmine issue http://projects.theforeman.org/issues/9476

Comment 3 Adam Price 2015-02-23 21:14:52 UTC
dates are displayed as YYYY-MM-DD.

merged to master.

https://github.com/Katello/foreman-gutterball/commit/e6b1bc1b4d03ddba35830ff8bb5beaeaf0756df2

Comment 6 Tazim Kolhar 2015-07-10 09:03:34 UTC
hi

please provide verification steps
thanks

thanks and regards,
Tazim

Comment 7 Adam Price 2015-07-10 13:43:11 UTC
You can run a system-status report or a status-trend report. Either of those should have a date field in YYYY-MM-DD format within the response data.

visit http://yourserver.com/apidoc/v2/content_reports for more info.

Comment 8 Tazim Kolhar 2015-07-15 06:42:14 UTC
VERIFIED:
# rpm -qa | grep foreman
ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.9-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-ovirt-1.7.2.30-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-debug-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
foreman-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.18-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-proxy-1.7.2.5-1.el7sat.noarch
ibm-x3755-02.ovirt.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
ibm-x3755-02.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-compute-1.7.2.30-1.el7sat.noarch
foreman-vmware-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch
foreman-libvirt-1.7.2.30-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ibm-x3755-02.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch
foreman-gce-1.7.2.30-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.17-1.el7sat.noarch
foreman-postgresql-1.7.2.30-1.el7sat.noarch

steps:
# hammer content-report content-host-status --organization-id 1
[Foreman] Username: admin
[Foreman] Password for admin: 
[......................................................................] [100%]

Hostname,Status,Date
hp-z600-02.ml3.eng.bos.redhat.com,valid,2015-07-09

Date field is in format YYYY-MM-DD format

Comment 10 errata-xmlrpc 2015-08-12 05:26:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2015:1592


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