Feature #10724
Need a better rake katello:reindex
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Description
The current katello reindex has some of the following issues
1) Stops at the first object failure and does not continue indexing the rest
2) Does not provide debug information on what exact object failed
We need it to be little more useful that that.
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot almost 8 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/5277 added
- Pull request deleted (
)
#2
Updated by Mike McCune almost 8 years ago
Updated by - Bugzilla link set to 1229909
#3
Updated by Partha Aji almost 8 years ago
Updated by - Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|7e246b8341bfce91035f1e31d0746e253cd227e8.
#4
Updated by Eric Helms over 7 years ago
Updated by - Related to Bug #10637: Reindex fails added
#5
Updated by Eric Helms over 7 years ago
- Legacy Backlogs Release (now unused) set to 31
- Triaged changed from No to Yes
Fixes #10724 - Peppier katello:reindex
This commit modifies the outcome of rake katello:reindex in the
following ways
1) It does not stop the task at the first object indexing failure.
2) It prints useful information on the object that it was unable to
index.
3) It does not run reindex unless Katello::Ping works. This will ensure
that customers are not running rake katello:reindex in a half baked
environment.
In the case of Repos and Content Hosts it provides information like
Candlepin/Pulp/Foreman data was out of sync etc