-
Notifications
You must be signed in to change notification settings - Fork 204
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 broken Service Sets page #2799
Conversation
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Konstantin Kelemen.
|
7e5d7a3
to
339a16f
Compare
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Konstantin Kelemen.
|
339a16f
to
1bed65a
Compare
Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA). Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA. After that, please reply here with a comment and we'll verify. Contributors that have not signed yet: @konstantin-kelemen
|
CLA has been signed |
@cla-bot check |
Thanks for reporting this! The error can be reproduced, but the fix is not correct - it provides the set name as the service name. Service names are not shown in this table, but should be subject for search |
Fixed with 7c2a3f2 |
I was getting an SQL error on the Director Service Sets page since I got the module updated from v1.10.2 to the latest master code from the repo.
The query was:
and the error was:
After trying to run this command in psql shell I quickly figured out that there was a typo in one of the parameters:
o.object_name
instead ofos.object_name
.This PR fixes the typo in the module code.