Bug 1858854 - Sometimes it takes long time for worker machines to become Running
Summary: Sometimes it takes long time for worker machines to become Running
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.7.0
Assignee: OCP on RHV Team
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-20 15:06 UTC by Jan Zmeskal
Modified: 2020-12-09 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-09 16:45:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
machine-controller log from cluster where workers took about 18 minutes to become Running (225.66 KB, text/plain)
2020-07-20 15:06 UTC, Jan Zmeskal
no flags Details

Description Jan Zmeskal 2020-07-20 15:06:59 UTC
Created attachment 1701771 [details]
machine-controller log from cluster where workers took about 18 minutes to become Running

Description of problem:
This is a follow-up to the BZ1817853. During its verification, I found out that in some cases newly created worker machines go into Running state (oc get machine -n openshift-machine-api) very quickly, let's say after about 5 minutes. In other cases, such as the one described here (https://bugzilla.redhat.com/show_bug.cgi?id=1817853#c23) it takes significantly longer, about 18 minutes in that specific case.


How reproducible:
Inconsistently

Steps to Reproduce:
https://bugzilla.redhat.com/show_bug.cgi?id=1817853#c23

Actual results:
Worker machines sometime spend so much time in Provisioned state that the user might think they got stuck there.

Expected results:
If we can speed that process up (as is the case in some of the instances of adding worker machines), that would be great. If not, it would be nice to inform user that the machine is still progressing and did not just end up in Provisioned state forever.

Comment 1 Gal Zaidman 2020-12-09 16:45:15 UTC
Closing this since I couldn't reproduce and QE env was very buggy at the time this bug was opened.
Please reopen if you hit this issue


Note You need to log in before you can comment on or make changes to this bug.