Red Hat Bugzilla – Bug 1314563
katello:reindex is not currently reindexing docker content
Last modified: 2016-07-27 05:25:30 EDT
Description of problem:
The 'foreman-rake katello:reindex' is often use to ensure that the Satellite (katello) database is kept in sync with backend services (e.g. pulp, candlepin). While this is not something that is used all of the time, there are times that it is run as part of debugging and resolving issues.
It appears that the current re-index does not include Docker content (i.e. Katello::DockerManifest & Katello::DockerTag). We should update this to be consistent.
Version-Release number of selected component (if applicable):
Satellite 6.2 snap 2
Steps to Reproduce:
first, let's destroy the docker content in the katello database, leaving in place the data from backend services. (Note: this should NOT be done on a production system, this is just for testing purposes)
1. foreman-rake console
3. Katello::DockerManifest.all.count # keep the count
4. Katello::DockerTag.all.count # keep the count
6. Katello::DockerManifest.all.count # should return 0
7. Katello::DockerTag.all.count # should return 0
from outside of the console:
8. foreman-rake katello:reindex
from inside of the console:
9. Katello::DockerManifest.all.count # should return same number as 3 above
10. Katello::DockerTag.all.count # should return same number as 4 above
The counts from 3 & 9 and 4 & 10 do not match.
The counts should be the same, indicating that the docker content was re-indexed. In addition, if look closer at the responses (without the '.count') the records should be similar (i.e. ids may be different, but the core content is the same).
Created redmine issue http://projects.theforeman.org/issues/14049 from this bug
Upstream bug component is Content Management
Upstream Katello PR: https://github.com/Katello/katello/pull/5844
Verified in Sat 6.2 snap 8.1.
The issue in not reproducible.
I see that, the counts of docker manifests and tags are same as earlier on re-indexing.
So moving this to verified.
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.