-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.11.z, 4.10.z
Description of problem:
When updating s390x cluster from 4.10.35 to 4.11.34, i got following message in the UI: Updating this cluster to 4.11.34 is supported, but not recommended as it might not be optimized for some components in this cluster. Exposure to KeepalivedMulticastSkew is unknown due to an evaluation failure: client-side throttling: only 9m20.476632575s has elapsed since the last match call completed for this cluster condition backend; this cached cluster condition request has been queued for later execution On OpenStack, oVirt, and vSphere infrastructure, updates to 4.11 can cause degraded cluster operators as a result of a multicast-to-unicast keepalived transition, until all nodes have updated to 4.11. https://access.redhat.com/solutions/7007826 As we discussed on Slack[1] message could be more user friendly, something like this[2]: "Throttling risk evaluation, 2 risks to evaluate, next evaluation in 9m59s." [1] https://redhat-internal.slack.com/archives/CEGKQ43CP/p1683621220358259 [2] https://redhat-internal.slack.com/archives/CEGKQ43CP/p1683643286581299?thread_ts=1683621220.358259&cid=CEGKQ43CP
Version-Release number of selected component (if applicable):
4.11.34
How reproducible:
Have a cluster on 4.10.35 or i guess any 4.10.z and update to 4.11.34
Steps to Reproduce:
1. Open webconsole 2. On the dashboard/Overview click on Update cluster 3. Change the channel to stable-4.11 4. Select new version and from the drop down menu click on Include supported but not recommended versions 5. Select 4.11.34 6. Message from the problem description appears
Actual results:
Unclear message
Expected results:
Clear message
- relates to
-
OCPBUGS-5469 Risk cache warming takes too long on channel changes
- Closed
-
OCPBUGS-19512 Faster risk cache warming
- Closed
- links to
-
RHEA-2023:5006 rpm