Skip to content
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

Backport of NET-5187: Upgrade test timeout due to log producer errors into release/1.16.x #18472

Conversation

hc-github-team-consul-core
Copy link
Collaborator

Backport

This PR is auto-generated from #18461 to be assessed for backporting due to the inclusion of the label backport/1.16.

The below text is copied from the body of the original PR.


Description

If --follow-log=true several upgrade tests timeout after passing. This was as a result of container failing to stop due to log producer not being stopped before container restart

SOLUTION
To restart a container - sidecar:

  • Stop log producer
  • Stop Container
  • Start Container
  • Start Log Producer
    Then container can be stopped and terminated gracefully.

Testing & Reproduction steps

Links

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Overview of commits

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved Consul Bot automated PR

@vercel vercel bot temporarily deployed to Preview – consul-ui-staging August 15, 2023 16:37 Inactive
@vercel vercel bot temporarily deployed to Preview – consul August 15, 2023 16:40 Inactive
@hc-github-team-consul-core hc-github-team-consul-core merged commit dfb5b1f into release/1.16.x Aug 15, 2023
@hc-github-team-consul-core hc-github-team-consul-core deleted the backport/NET-5187/safely-vital-hookworm branch August 15, 2023 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants