-
Bug
-
Resolution: Done
-
Normal
-
None
-
ACM 2.8.0, ACM 2.7.0
-
False
-
None
-
False
-
-
-
No
sometimes when 11170 failed, it would leave victoriametrics pod still running there, and it would cause some cases failed,
like
s: "failed to check node selector with kubernetes.io/os=linux for pod: victoriametrics-569564879b-b96lj",
s: "Failed to check affinity for pod: %!v(MISSING)victoriametrics-569564879b-b96lj",
- account is impacted by
-
ACM-5291 [ACM QE] Observability - ACM 2.8 Train 04 (Global Sprint 2023 - 05) QE Work Items
- Closed