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

Fix sanity check done on configured filesystem directories when running Alertmanager in microservices mode (#2947) #2948

Merged
merged 1 commit into from
Sep 14, 2022

Conversation

pracucci
Copy link
Collaborator

What this PR does

Cherry-picking the fix done in #2947.

Which issue(s) this PR fixes or relates to

N/A

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

…ng Alertmanager in microservices mode (#2947)

* Fix sanity check done on configured filesystem directories when running Alertmanager in microservices mode

Signed-off-by: Marco Pracucci <marco@pracucci.com>

* Added CHANGELOG entry

Signed-off-by: Marco Pracucci <marco@pracucci.com>

Signed-off-by: Marco Pracucci <marco@pracucci.com>
(cherry picked from commit bfad6ac)
@@ -4,6 +4,8 @@

### Grafana Mimir

* [BUGFIX] Fix sanity check done on configured filesystem directories when running Alertmanager in microservices mode. #2947
Copy link
Member

@pstibrany pstibrany Sep 14, 2022

Choose a reason for hiding this comment

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

Changelog on the release branch should not mention main.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

But it does. I guess we'll fix it before publishing the stable version.

Copy link
Member

Choose a reason for hiding this comment

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

But it does.

Yep. 😂 (It has nothing to do with this PR, I should have been more careful reviewing the other PR that introduced the change.)

Copy link
Contributor

@jhesketh jhesketh left a comment

Choose a reason for hiding this comment

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

Seems reasonable as far as a backport goes, but take with a grain of salt as I'm still learning the internals.

@pracucci pracucci merged commit df038d7 into release-2.3 Sep 14, 2022
@pracucci pracucci deleted the backport-2947-to-release-2.3 branch September 14, 2022 13:03
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