Bug 1323735
| Summary: | ramdisk log file have old date | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Raviv Bar-Tal <rbartal> |
| Component: | openstack-ironic-inspector | Assignee: | Miles Gould <mgould> |
| Status: | CLOSED ERRATA | QA Contact: | Raviv Bar-Tal <rbartal> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.0 (Liberty) | CC: | ddomingo, dnavale, jschluet, mburns, sclewis, slinaber |
| Target Milestone: | beta | Keywords: | Triaged |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-ironic-inspector-3.3.1-0.20160607104948.457c127.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the modification dates were not being set on the IPA RAM disk logs when creating a tarfile. As a result, the introspection logs appeared to have the modification date of 1970-01-01, causing GNU tar to issue a warning when extracting the files.
With this update, the modification dates are set correctly when creating a tarfile. The timestamps are now correct and GNU tar no longer issues the warning.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-14 15:29:48 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
Raviv Bar-Tal
2016-04-04 14:34:52 UTC
Thanks for reporting. I think it's due to the fact we build the tarball in Python. I need to check the documentation. I think the code responsible is here: https://github.com/openstack/ironic-inspector/blob/master/ironic_inspector/plugins/standard.py#L346-L348 We're just writing out the data, and not setting any tar headers. And the file's actually being created here: https://github.com/openstack/ironic-python-agent/blob/master/ironic_python_agent/inspector.py#L262 Is the system time being set correctly on the machine being introspected? Looks like this is a well-known gotcha with Python's tarfile module: http://stackoverflow.com/questions/8648872/how-can-i-programmatically-create-a-tar-archive-of-nested-directories-and-files#comment10744694_8649029 Patch submitted to upstream here: https://review.openstack.org/#/c/301225/ This bug did not make the OSP 8.0 release. It is being deferred to OSP 10. Patch has been merged into upstream. Removed unnecessary "the"s in doc text. 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://rhn.redhat.com/errata/RHEA-2016-2948.html |