Fix allocation bug instance connection error #5274
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hancement/5198-dtt1-allocation-bug-instance-connection-error-to4495-dtt1-release
teddytpc1
approved these changes
Apr 19, 2024
teddytpc1
deleted the
enhancement/5198-dtt1-allocation-bug-instance-connection-error-to4495-dtt1-release
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
close: #5198
A connectivity validation method is created after provisioning, this validation is carried out through
SSHorWINRMdepending on the system. When the module finishes executing it is because the machine is provisioned and has connectivity, therefore, it is ready to use.Several tests were carried out and they were used to correct some errors in the Windows userData and the general Windows configuration. As well as in the process of eliminating Windows instances.
The validation process has an automatic rollback, that is, if after 15 retries with a time between attempts of 60 seconds the instance does not connect, a rollback is automatically performed and the instance is deleted. This rollback can be disabled with the
--rollbackargument set toFalseRelated
Retry of: #5216
Testing
Test with rollback: #5198 (comment)
Test without rollback: #5198 (comment)
Test PowerPC: #5198 (comment)
Test macOS Intel: #5198 (comment)
Test macOS ARM: #5198 (comment)
Test Linux: #5198 (comment)
Test Windows Server 2012 R2: #5198 (comment)
Test Windows Server 2016: #5198 (comment)
Test Windows Server 2019: #5198 (comment)
Test Windows Server 2022: #5198 (comment)
Test Windows desktop 10: #5198 (comment)
Test Windows desktop 11: #5198 (comment)