-
Bug
-
Resolution: Done-Errata
-
Major
-
2.15.0 GA
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
-
RHOAM Sprint 63
-
Low
When 3scale with monitoring enable is upgraded from 2.14 to 2.15 Pod monitor for system is not updated. It looks like old definition will stay (/metrics and /yabeda-metrics) which will cause errors in system-app
[b9212d72-815e-4cb5-aa3f-cf6aed6c0e18] [192.168.144.115] [192.168.136.46] Started GET "/yabeda-metrics" for 192.168.136.46 at 2024-09-11 11:00:10 +0000 [b9212d72-815e-4cb5-aa3f-cf6aed6c0e18] [192.168.144.115] [192.168.136.46] [b9212d72-815e-4cb5-aa3f-cf6aed6c0e18] [192.168.144.115] [192.168.136.46] ActionController::RoutingError (No route matches [GET] "/yabeda-metrics"): [b9212d72-815e-4cb5-aa3f-cf6aed6c0e18] [192.168.144.115] [192.168.136.46] [b9212d72-815e-4cb5-aa3f-cf6aed6c0e18] [192.168.144.115] [192.168.136.46] lib/three_scale/middleware/cors.rb:21:in `call' 192.168.136.46 - - [11/Sep/2024:11:00:10 +0000] "GET /404 HTTP/1.1" 404 - 0.0052
Deleting PodMonitor/system-app will cause operator to recreate new one with correct content. I assume same would happen when monitoring would be disabled, and then re-enabled.
When new 3scale 2.15 deployments is created PodMonitor contains correctly only /metrics.
- links to
-
RHEA-2024:128529
Red Hat 3scale API Management 2.15.0 Release - Container Images
- mentioned on
