Project

General

Profile

Actions
Copy link

Bug #22952

closed

Account for different datetime format in Suse errata

Added by Jake Callahan almost 7 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
John Mitsch
Category:
Errata Management
Target version:
Katello 3.6.1
Difficulty:
easy
Triaged:
Bugzilla link:
Pull request:
https://github.com/Katello/katello/pull/7255
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Suse uses a different datetime format than what Katello currently expects. Instead of a formatted data and time, they use seconds since Epoch. This is preventing Katello from correctly parsing the date, leading to a blank entry.

Further, it looks like the issue happens during or before the values are stored in the katello_errata table.
id | uuid | errata_id | created_at | updated_at | issued | updated | errata_type | severity |
1 | 003a57f6-48e7-4752-aa07-7c62ac288d17 | openSUSE-2017-1284 | 2018-03-19 13:54:40.547011 | 2018-03-19 13:54:40.552124 | | | recommended | moderate |

Example: <issued date="1519129773" />

Suse's documentation on their updateinfo metadata: https://en.opensuse.org/openSUSE:Standards_Rpm_Metadata_UpdateInfo

Verification steps:
1. Sync a suse repository that contains errata.
- http://download.opensuse.org/update/openSUSE-stable/
2. Check that the issued and updated dates (if applicable) show up correctly in the UI/CLI/API

Actions
Copy link

Also available in: Atom PDF