-
Bug
-
Resolution: Done
-
Undefined
-
None
-
4.12.0, 4.11.z, 4.10.z
-
None
-
CNF RAN Sprint 225, CNF RAN Sprint 226, CNF RAN Sprint 227, CNF RAN Sprint 228
-
4
-
False
-
-
Description of problem:
Current implementation uses 20 seconds * number of clusters as the job view update interval. This is to avoid overloading ACM with too many view updates. When the number of clusters is big enough, the update interval becomes impractical, i.e. way longer than the time required to complete the job or even longer than the whole CGU timeout
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Enable pre-caching in CGU with a large number of clusters 2. 3.
Actual results:
Pre-caching jobs are completed on spokes, but the status is not updated in the mcv on the hub for a long time
Expected results:
A reasonable update interval in this case so that CGU can move forward Additional info:
Workaround is to have less clusters in one CGU or increase the overall CGU timeout to accommodate the extra time waiting on precaching job status
- blocks
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
- mentioned on
