Description of problem: When a package is uploaded to a repository in a custom product, the upload finishes successfully but the package isn't visible in neither UI nor CLI. It gets correctly uploaded into Pulp but it's not imported into Satellite. Workaround: Run foreman-rake katello:reindex after the upload How reproducible: 100% on machines with timezone other than UTC Steps to Reproduce: 1. Create a custom product and a repository 2. Upload a package to that repository 3. Click "Manage packages" to list packages in the repo 4. The list is empty even though the upload was successful Actual results: Packages aren't visible in Satellite Expected results: Uploaded packages should be immediately visible Additional info: The problem seems to be in Pulp/Mongo which doesn't interpret timezones in content search queries. Satellite's FinishUpload action plans FilteredIndexContent with filter set to "created > 5.minutes.ago.iso8601" to limit indexing only to recently created packages. Filtered query into Pulp in the latter action returns empty array when the time contains timezone component other than "Z". ("2016-10-19T11:42:02Z" vs "2016-10-19T13:42:02+02:00")
Opened up Pulp issue: https://pulp.plan.io/issues/2353
Upstream bug component is Pulp
Upstream PR: https://github.com/Katello/katello/pull/6404
Small addendum to the original bug description: the timezone must be AHEAD of UTC (e.g. UTC+6) to reproduce this bug.
*** Bug 1383566 has been marked as a duplicate of this bug. ***
Verified in Satellite 6.2.5 Uploaded 10 rpms to a custom repository, all were immediately counted for and visible in the UI. See attached screenshot for verification (note the el7 packages in an el6 repo).
Created attachment 1227007 [details] verification screenshot
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/RHBA-2016:2940
Basic scenario is covered properly in test automation scripts, but specific steps (non-UTC timezone) are too destructive from Jenkins CI flow (adding specific configuration just for one test case seems as not proper idea)