Fix error during custom cluster creation with slow network speeds #15814
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #15538
Technical notes summary
This is the line throwing the error
My own local testing and console logs in the issue's screenshot confirm that the wait for management ended because management was found; it didn't time out. The issue appears to be that for a brief window after a provisioning cluster is created, the model's
thisdoesn't include updated status so we can't get the management cluster's id. There is already a workaround for this inwaitForMgmt. I added the same workaround to themgmtIdgetterAreas or cases that should be tested
The scenario as described in the issue should be tested. Note for my fellow firefox enjoyers: it seems specific to chrome
Areas which could experience regressions
none
Screenshot/Video
Checklist
Admin,Standard UserandUser Base