-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configurable Timeout for WaitForIP #82
Comments
I'll take a poke at this, shouldn't take long. Just so I'm clear, are you referring to this timeout, which seems to be 5 seconds, not 5 minutes? I couldn't find any other references that might apply to this, but feel free to redirect if I've missed something. |
There is a loop running 60 times, with 5seconds wait each, which results in 5min fixed. |
I looked into how we might slot a configurable timeout into this, and I think the best approach would be to add an additional step to wait for the IP, rather than bundling it within the create step. Similar to this; I don't have enough experience with this code, or the cycles to implement right now, but I think this would be the best approach based on my limited research. Good luck! |
@DiscoRiver Thanks for research, this is indeed a good solution. However, lets raise the fixed timeout now to 15min as a workaround for slow Windows Deployments until we implement the WaitForIP Step. |
@DiscoRiver you can test with v0.4.0 |
/kind bug
Windows Machine with DHCP needs more than the fixed 5min Timeout to report IP to PrismCentral.
Create an configuration option for timeout
The text was updated successfully, but these errors were encountered: