-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14.0, 4.15.0, 4.16.0
-
No
-
Proposed
-
False
-
-
-
Bug Fix
-
Done
This is a clone of issue OCPBUGS-22399. The following is the description of the original issue:
—
Users are encountering an issue when attempting to "Create hostedcluster on BM+disconnected+ipv6 through MCE." This issue is related to the default settings of `--enable-uwm-telemetry-remote-write` being true. Which might mean that that in the default case with disconnected and whatever is configured in the configmap for UWM e.g ( minBackoff: 1s url: https://infogw.api.openshift.com/metrics/v1/receive Is not reachable with disconneced. So we should look into reporting the issue and remdiating vs. Fataling on it for disconnected scenarios.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
In MCE 2.4, we currently document to disable `--enable-uwm-telemetry-remote-write` if the hosted control plane feature is used in a disconnected environment. https://github.com/stolostron/rhacm-docs/blob/lahinson-acm-7739-disconnected-bare-[…]s/hosted_control_planes/monitor_user_workload_disconnected.adoc Once this Jira is fixed, the documentation needs to be removed, users do not need to disable `--enable-uwm-telemetry-remote-write`. The HO is expected to fail gracefully on `--enable-uwm-telemetry-remote-write` and continue to be operational.
- blocks
-
OCPBUGS-26526 Explore making that remote write failure less intrusive
- Closed
- clones
-
OCPBUGS-22399 Explore making that remote write failure less intrusive
- Closed
- is blocked by
-
OCPBUGS-22399 Explore making that remote write failure less intrusive
- Closed
- is cloned by
-
OCPBUGS-26526 Explore making that remote write failure less intrusive
- Closed
- links to
-
RHSA-2023:7198 OpenShift Container Platform 4.15 security update