ThothSolversThothS2iOfferedMismatch

[sesheta]

Alertmanager URL: https://alertmanager-main-openshift-monitoring.apps.smaug.na.operate-first.cloud

• firing https://thanos-querier-openshift-monitoring.apps.smaug.na.operate-first.cloud/graph?g0.expr=thoth_graphdb_solvers_number_match%7Bfield%3D%22metrics-exporter-thoth-infra-prod.apps.smaug.na.operate-first.cloud%22%2Cnamespace%3D%22thoth-infra-prod%22%7D+%3D%3D+1&g0.tab=1

  Labels:

  • alertname = ThothSolversThothS2iOfferedMismatch
  • cluster = moc/smaug
  • container = metrics-exporter
  • endpoint = metrics
  • field = metrics-exporter-thoth-infra-prod.apps.smaug.na.operate-first.cloud
  • instance = 10.129.5.88:8080
  • job = metrics-exporter
  • namespace = thoth-infra-prod
  • pod = metrics-exporter-7-qjm5f
  • prometheus = openshift-user-workload-monitoring/user-workload
  • service = metrics-exporter

  Annotations:

  • severity = MEDIUM
  • summary = Number of solvers from ConfigMap and from database do not match!

TODO: add graph url from annotations.

[goern]

/assign @fridex /assign @mayaCostantini /kind bug /priority critical-urgent

@fridex @mayaCostantini @Gregory-Pereira could you have a look at a short documentation how to handle this kind of alerts? thx :100:

/sig devsecops /triage accepted

[fridex]

The issue here might be the new solver f35-py310 installation. This alert is triggered when database records do not list a solver that is installed in openshift and ready to solve packages (in the configmap) or vice versa.

The issue here that triggers alert:

• there are solver records in the database that do not conform to solvers configured - this means Thoth operator should either remove solver database records (by running purge job) or install the missing solver to have the ability to solve new packages with the given solver

• there are solvers installed that do not have any database records - this means to either remove the old solver (the database was purged but there is still installed old solver) or a new solver did not solve new packages (I suspect this is the reason behind this alert).

Both cases might produce inconsistencies in the recommendations given. Hence we provide this warning to users for now (until we solve packages with f35-py310).

[fridex]

BTW this alert should go away once the database in moc/smaug gets updated with f35-py310 records from stage where the ingestion is happening. I think @harshad16 is aware of this and the reason behind this alert.

[harshad16]

Thanks for the details and yes I m aware of these errors https://github.com/thoth-station/thoth-application/issues/2542#issuecomment-1117333488

/unassign @fridex /unassign @mayaCostantini

[goern]

is this still valid?

[harshad16]

This is fixed closing this issue if such problem presists, a new issue would be opened.

[goern]

I receive a 403 for the URL and cant review this.