-
Notifications
You must be signed in to change notification settings - Fork 75
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
Fix tests #3354
Fix tests #3354
Conversation
PR ChecklistHow to use this checklistHow to use this checklistPR AuthorFor each section, check a box when it is true. PR ReviewerCheck that the PR checklist action did not fail. Bug ReferencesNone. Confirm
How to properly reference fixed bugs
Test UpdatesUnit Tests
Integration Tests
Documentation
Does this PR require review from someone outside the core ubuntu-pro-client team?
|
@@ -117,19 +117,14 @@ Feature: auto-attach retries periodically on failures | |||
|
|||
Examples: ubuntu release | |||
| release | machine_type | | |||
| xenial | aws.generic | |
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.
auto-attach retries should work on aws, right? What changed?
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.
Sorry I should read commit messages before commenting 🤦
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.
But then, if the mechanism for triggering retries on aws is different now, we can't rely on the gcp/azure tests for it right?
I think we need an aws specific test for this feature now
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.
Done
On AWS, we no longer try to run auto-attach if we run the ua-auto-attach systemd job. Because of that, the setup we are using for the retry auto-attach test no longer works for AWS. We are now using a different setup for AWS
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.
Thank you!
Why is this needed?
Fix some integration tests for the release
Test Steps
Check that the affected integration tests are passing