-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
4.16.0, 4.17.0
-
Important
-
No
-
3
-
OTA 249, OTA 250, OTA 251, OTA 252, OTA 253, OTA 254, OTA 255
-
7
-
Rejected
-
False
-
-
Release Note Not Required
-
In Progress
=Control Plane Upgrade=
...
Completion: 45% (Est Time Remaining: 35m)
^^^^^^^^^^^^^^^^^^^^^^^^^
Do not worry too much about the precision, we can make this more precise in the future. I am thinking of
1. Assigning a fixed amount of time per CO remaining for COs that do not have daemonsets
2. Assign an amount of time proportional to # of workers to each remaining CO that has daemonsets (network, dns)
3. Assign a special amount of time proportional to # of workers to MCO
We can probably take into account the "how long are we upgrading this operator right now" exposed by CVO in OTA-1160
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- relates to
-
OTA-1160 Expose "how long has this CO been updating"
-
- Closed
-
- links to
-
RHEA-2024:3718
OpenShift Container Platform 4.17.z bug fix update