Project

General

Profile

Feature #10761

Need a foreman-rake katello:check

Added by Partha Aji almost 5 years ago. Updated 9 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Web UI
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

One of the common rake tasks used in diagnosing state of a Katello/Sat server is foreman-rake katello::reindex. The purpose of that task is to update elastic indices and not really suitable for diagnosis.
What we need is a task that checks the followwing
  • Broken Repo associations (repo not in cp/ not in pulp)
  • Broken Host associations (content host not in cp/pulp/foreman)
  • Broken org associations (not in cp/pulp)
  • Broken org : smart proxy associations..
  • others

We need a way to say foreman-rake katello:check and have that dump things it finds inconsistent so that the user can ask for help if needed.


Related issues

Blocks Katello - Feature #10763: Need a foreman-rake katello:fixNeed more information

History

#1 Updated by Partha Aji almost 5 years ago

#2 Updated by Stephen Benjamin almost 5 years ago

  • Category changed from Installer to Web UI

One more:

  • Check that a Capsule has a Content Host attached

#3 Updated by Eric Helms almost 5 years ago

  • Status changed from New to Need more information
  • Legacy Backlogs Release (now unused) set to 70
  • Triaged changed from No to Yes

Partha, I am targeting this for 2.4 -- please confirm whether that priority for release target makes sense.

#4 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 70 to 86

#5 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 114

#6 Updated by John Mitsch 9 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from Need more information to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF