-
Notifications
You must be signed in to change notification settings - Fork 23.8k
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
ansible-test - Improve container management. #78550
Conversation
2e93193
to
6e366ba
Compare
6e366ba
to
a1c59c6
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
a1c59c6
to
41348af
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
41348af
to
193c922
Compare
d431115
to
c59cc3f
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
ba6d3f3
to
d517b41
Compare
/azp run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docs portion LGTM
@mattclay and everyone else involved in this, thanks a lot for this huge improvement! :) |
big +1 :) |
if 'Permission denied' in ex.message: | ||
raise | ||
|
||
# No "Permission denied" check is performed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like timeouts still happen: #79508
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, at least we know it's not due to ansible-test trying to connect before the user is ready. It looks like we're back to needing to look over the logs on the guest when it's disconnecting the client.
See changelogs/fragments/ansible-test-container-management.yml for details. (cherry picked from commit cda16cc)
SUMMARY
ansible-test - Improve container management.
ISSUE TYPE
Feature Pull Request
COMPONENT NAME
ansible-test