-
Bug
-
Resolution: Unresolved
-
Major
-
4.21
-
None
Description of problem:
MicroShift's readiness detection mechanism has inefficient polling intervals and redundant client creation that delays startup confirmation and resource readiness detection
Version-Release number of selected component (if applicable):
4.21
How reproducible:
100%
Steps to Reproduce:
1. Start MicroShift.
2. Check journal logs for elapsed time per component from start to ready.
3.
Actual results:
Expected results:
Additional info:
- is depended on by
-
USHIFT-6234 MicroShift 4.20 sees significant increase in start time(s)
-
- Closed
-
- links to